On Tue, Sep 06, 2005 at 10:06:45AM -0400, Andres Salomon wrote: > On Tue, 2005-09-06 at 15:20 +0200, Sven Luther 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 > > > > Indeed. > > > > > 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? > > > > The plan, as i see it, is that as soon as 2.6.12 is in etch, we are going to > > upload 2.6.13 kernels anyway to sid, and continue to make 2.6.12 bug-fix > > uploads to etch by t-p-u (if this is not still broken). > > > > I wouldn't really consider 2.6.12 to be etch release-material until the > packaging changes settle down; more of something for d-i and etch users > to use while we finalize the packaging. I wouldn't want to see etch > actually release w/ -6.
Agreed, though currently Etch is testing, and the likelyhood that Etch is magically released as stable before we have a chance to make another release, and indeed settle down the packaging, seems remote. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
