On Tue, 2005-09-06 at 22:25 +0900, Horms wrote: > On Tue, Sep 06, 2005 at 08:51:06AM -0400, Andres Salomon wrote: > > Ok, so now that we have dists/sid and dists/trunk (which is for development > > and experimental stuff); how is this actually supposed to work? I > > understand > > the scenario when we have 2.6.12 in sid and 2.6.13rc in trunk; stick > > any new development stuff in trunk, backport to sid if desired, do sid > > releases from dists/sid, and experimental releases from dists/trunk. What > > about the case where we have 2.6.13 in both? Are we supposed to do all > > releases from trunk, and branch/cp to sid? Are we supposed to do releases > > from sid, and keep trunk ready for 2.6.14 development; regularly > > forward-porting changelogs and stuff? > > I think this is pretty confusing myself, though I believe that the idea > is that if sid and trunk are the same, then you nuke the sid branch. > So basically things only exist in sid/ if we are working on something > newer than what is in sid (and being maintained). >
Pretty much what I was thinking; why keep a branch around when we're not using it? Why not just create trunk only when it's different from sid (or vice versa, whatever the svn users like to call HEAD). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
