geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy" <>
Subject Re: Branching trunk and creating 1.2
Date Fri, 17 Nov 2006 16:04:11 GMT
Matt, as I understand, the commits should go into both places (trunk and
branches\1.2) right?  And dooes the goat herder need to take care of the
missing commits or just push the goat to commit in both places?

Good to see that the JIRAs for 1.2 count is coming down :o).  It would have
been even better if many were addressed rather than moved to 2.0 and
WishList :o(.  But, once again every thing can not be addressed right away.


On 11/17/06, Matt Hogstrom <> wrote:
> All,
> We've been talking about moving 1.2 from trunk to a branch while the
> final touches are put on it as well as promoting trunk to 2.0-
> SNAPSHOT and starting the push to Java EE 5.0.
> At this point it looks like most of the activity that is underway in
> trunk is complete.  Here is the outstanding issues I'm aware of.
> 1. Upgrade all the license headers and copyright notices to conform
> to the new ASF guidelines.
> 2. Need to get some issues with the connectors straightened out.
> Also, we're down from 200 JIRAs to 88 and still decreasing :)
> When we get these items straightened out I'd like to go ahead and
> make the branch tonight if we're good.
> Dain expressed his concerns about drift in the code base and having
> lived through the dead-1.2 branch muck he's spot on.  We need to make
> sure that code doesn't get committed in one place and not another.
> Anyone want to volunteer to be the goat herder?
> Any other issues people can think of?
> Matt Hogstrom
> When the clouds are full they pour the rain out on the earth;
> and whether a tree falls to the north, or it falls to the south,
> wherever the tree falls, there it lies.

View raw message