Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On Sun, Apr 18, 2010 at 2:52 AM, buginator buginato...@gmail.com wrote: Ok, I am fine with either a tag or a branch, as soon as Per OKs it, I'm ok with that. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. If the Dydo changes can't be rectified, then we will do what we did the the 2.3_rc1a tag. The 2.3.0 release should be done on 4/24/10. Are we all in agreement? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On Saturday, 17 April 2010 at 15:45, buginator wrote: Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. Actually, I'd branch 2.3.0 from the rc tag as soon as possible, since the whole point of branching is that the 2.3 branch then is not frozen, only the 2.3.0 branch (which then can get selected backports from 2.3). Zarel proposed a tag instead of a branch for 2.3.0, to which we commit until the final release. Doesn't matter much to me, it's all the same anyway in svn. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On Sat, Apr 17, 2010 at 2:45 PM, buginator buginato...@gmail.com wrote: Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. Yeah, that was my idea. If it's frozen, we might as well tag 2.3.0. Leaves 2.3-branch open for 2.3.1 commits. The 2.3.0 release should be done on 4/24/10. Man, I'm gonna have to rush the new layout. :( -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On 4/17/10, Christian Ohm wrote: On Saturday, 17 April 2010 at 15:45, buginator wrote: Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. Actually, I'd branch 2.3.0 from the rc tag as soon as possible, since the whole point of branching is that the 2.3 branch then is not frozen, only the 2.3.0 branch (which then can get selected backports from 2.3). Zarel proposed a tag instead of a branch for 2.3.0, to which we commit until the final release. Doesn't matter much to me, it's all the same anyway in svn. Ok, I am fine with either a tag or a branch, as soon as Per OKs it, then whoever can tag it. He might want to get his .02 on this issue, and if we don't hear from Per by Sunday evening, then we can just make the branch or tag then. I only know of 2 patches that need to be applied so far... ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
