Well, I definitely don't think that work should happen in a branch called 1.0.0. Rather, it would seem that we would want to create a branch called 1.0, and tag from it.
I think that we should make a 1.0 branch tonight, and then all future work in the 1.0 line will happen in it. So, if something goes wrong while building / voting on the release, we'll resolve those issues in the 1.0 branch, not in trunk. That way, people can keep on working on trunk, which will immediately become the 1.1 train. -Patrick On 8/20/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > Patrick- > > I expect that we'll keep the "1.0.0" branch around, and then make a > "1.0.0" tag once the release is cut and approved. > > What happens with the "1.0.0" branch (i.e., if 1.0.1 work takes place > in the 1.0.0 branch or in trunk) is, I believe, a topic that has yet > to be discussed. > > > On Aug 20, 2007, at 1:42 PM, Patrick Linskey wrote: > > > Hi, > > > > I think that we should be making a permanent 1.0 branch, and then tag > > off of it, so that we have somewhere to work on 1.0.1. Or do things > > work differently in svn? > > > > -Patrick > > > > On 8/20/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > >> OpenJPA Developers- > >> > >> Pursuant to the vote at http://www.nabble.com/-DISCUSS--set-a- > >> deadline-for-1.0.0-features-t4233167.html , a branch for OpenJPA > >> 1.0.0 will be created tonight at 11:59 PM EST, and a release > >> candidate will be immediately created for voting on the final 1.0.0 > >> release. > >> > >> If anyone needs more time for essential bugfixes, now is the time to > >> speak up. > >> > >> -- > >> Marc Prud'hommeaux > >> > >> > >> > > > > > > -- > > Patrick Linskey > > 202 669 5907 > > -- Patrick Linskey 202 669 5907
