Hi Ronnie, good questions that make me critically examine what I did.
First of all, we can still tag the code in trunk to follow your suggestion, if we deem it as a good course of action. I would consider the possibility and, in case, tag it before new commits happen. Second reason: since a 1_0 branch has existed now for quite a long time I assumed this was a policy D-D had decided sometime in the past. Admittedly I had to ask explicitly. The third reason is that we still can copy further developments from trunk into 2_0 at will, as long as we think they won't break anything. I expect trunk to diverge from 2_0 though, at least we have to keep the possibility open. Sooner or later the support for apache 1.x will be dropped in trunk making room for support of new apache versions, whereas I think of the 2_0 branch as something that will maintain the apache 1 code even though we will make fixes, adjustments and improvements on it. Unlike in the typical example for a branch I don't see 2_0 as a branch that will join in the future the development in trunk. I hope I passed the exam. :-) regards -- Massimo On Thu, 29 Apr 2010 18:40:24 +0200, Ronnie Brunner wrote > > prevent a user from building the module though. It's been corrected in > > the 2_0 branch and will be commited soon. > > Actually, just wondering: why did you create a 2_0 branch (especially > since it's copied from head. Don't you expect to continue development > on the trunk? I'd have thought that it might have made more sense to > just create a 2.0.0 tag on the trunk and then continue in the trunk. > > Or do you expect independent development happening on trunk and the 2_0 > branch? Or are there other reasons to create a branch instead of just > a tag (Even if it's technically the same in SVN anyway...)? > > Regards > Ronnie > -- > Ronnie Brunner | ronnie.brun...@netcetera.ch > phone +41-44-247 79 79 | fax +41-44-247 70 75 > Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch > > --------------------------------------------------------------------- > To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org > For additional commands, e-mail: rivet-dev-h...@tcl.apache.org -- --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
