What is woody's release process? [was: woody: Remaining RC bugs in base system]
Matt Zimmerman writes:
> On Fri, Jan 25, 2002 at 03:12:13AM +0000, Mark Brown wrote:
>
> > On Thu, Jan 24, 2002 at 09:41:01PM -0500, Matt Zimmerman wrote:
> >
> > > Such is the way of the freeze, I think. This will have to happen at
> > > some point when new versions of base packages stop flowing into testing.
> > > Either unstable will have to be frozen as well (in which case, we have
> > > missed part of the point of testing) or packages will have to be
> > > compiled against woody.
you "think"
> > If packages that are frozen just stay frozen and don't get people starting
> > to upload incompatible new versions this wouldn't be a problem. If
> > packages are going to start getting new incompatible versions then aren't
> > we going to start getting back to an old-style freeze but without the
> > ability to upload to frozen (making bug fixing a bit hard)?
>
> As I understand it, the new release mechanism doesn't necessarily preclude
> uploads to frozen under certain specific circumstances if we decide that it
> is necessary.
still thinking?
I believe, I think as well ... So what is our release process? A
global experiment to educate developers, that a release won't happen
until they stop uploading new, probably incompatible packages? ;-)
I get the impression that the release process is not know to many of
us. The last email from our release manager is dated from October
(debian-release) and November (debian-devel-announce). Anthony, please
could you clarify / re-post the release process (not necessarily
dates). One big question among others seems to be the state of
unstable during the release process and the existence of a "frozen"
distribution.
Thanks, Matthias
Reply to: