Re: Re: 1.3 soon?
"Jonathan Swartz" <[email protected]>
| Newsgroups | gmane.comp.web.mason.devel |
|---|---|
| Message-ID | <[email protected]> |
> > Ok. I also realized that before we can release 1.3 I have to clean up the > > logic on the site that handles different version branches, e.g. "stable" > > versus "development". Ok, I've cleaned this up a little. Once we release 1.3 we have to * add 1.3 to the "beta releases" list in the db * modify docs/manual/index.html and code/download/index.html to reflect the fact that we have three branches (1.0x, 1.2x, and 1.3x) > I see a bunch of tasks marked as 1.3x and checked in, but not listed in > Changes. We should review those. > > They are: > > - http://www.masonhq.com/resources/todo/view.html?id=556 > > Allow </& foo> > > This change is checked into HEAD, but not documented. It is documented on line 369 of Devel.pod. But if you meant not listed in Changes, you are correct. I'll add it. > > - http://www.masonhq.com/resources/todo/view.html?id=573 > > Should be documented in Changes, I think. Done. Also, I just realized we need to add attribution to all the changes that came from users. > > - http://www.masonhq.com/resources/todo/view.html?id=526 > > Document purpose of keys needed when using multiple comp roots. > > Where was this done? In Interp.pm, where comp_root now lives. But I added it to Admin.pod as well. > > > Before we consider this branch stable, I'd like us to consider the changes > needed to support a resolver that pre-computes resolution of each > component. I started working on this, but realized that it required some > API changes to the resolver. I need to revisit this and see what changes > need to be made, if any. It might be that your change to move the comp > root to the interp object makes this possible now. Ok, take a look. But why would this be a prerequisite for a release of 1.3? I'm certainly not considering the branch stable at this point anyway - it is most definitely beta until more people use it and we go through a number of bug fix releases. Jon ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/