Re: 1.3 soon?

[ moving this to dev list ]

On Mon, 13 Dec 2004, Jonathan Swartz wrote:

> 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".
>
> But once that is done, do you see any reason not to release the initial 1.3?

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.

- http://www.masonhq.com/resources/todo/view.html?id=573

   Should be documented in Changes, I think.

- http://www.masonhq.com/resources/todo/view.html?id=526

   Document purpose of keys needed when using multiple comp roots.

   Where was this done?


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.

> I'd like to make the initial announcement to mason-users for just this
> release, if that's ok with you.

Sounds good.  You did most of the work for this release, so you should get 
the glory ;)



-dave

/*===========================
VegGuide.Org
Your guide to all that's veg.
===========================*/


-------------------------------------------------------
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/