On May 8, 2006, at 12:42 PM, Dain Sundstrom wrote:
+1 to the re-cut trunk plan
I do not want to re-cut trunk, until we have the time to setup
gbuild to tck test it, and capacity on gbuild to run it. We should
never be out of compliance again. It is just to painful to fix later.
+ a bunch... Not only is it painful, but it's also risky -- you don't
know what issues are going to be found late in the game... It will be
hard to do this 100% of the time, but we need to find a way to do
this in reasonable size chunks...
--kevan
-dain
On May 6, 2006, at 2:30 PM, Matt Hogstrom wrote:
I think we're at the point where 1.1 needs to bake for a bit and
we'll release it in a few weeks. Since I expect that folks will
want to get to putting in new feature and functions for 1.2 I
wanted to kick off a thread to get that discussion going.
I'm consolidating here my recollections of discussion on the list
about what to do. The idea that made the most sense to me was to
move the current trunk to another branch and copy the 1.1 branch
to trunk. We'd then have people merge their changes from the the
old trunk to the new and start on 1.2.
I'm not sure about timing but it might be nice to have this work
done before Java One and the hackathons.
Thoughts?
Matt
