David Abrahams wrote:
That means establishing a 1.36.0 milestone
There's no need to create such a milestone. I created the "To Be Determined" milestone. Which means that in addition to looking at the tickets currently in the 1.35.0 milestone we need to look through the ones in "To Be Determined" to see if any apply for this release. But ideally I would rather see the bug handling to occur entirely outside the 1.35.0 milestone since all the bugs should be getting fixed in the trunk, not the release. Hence as a gross approximation we would move all the 1.35.0 tickets to the "to be determined" milestone. And when a library is placed in the branch we can move the resolved tickets only to 1.35.0. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo