Re: Stable and unstable
>
> > A suggestion regarding stable and unstable: Please do not set a cut off
> > date but
> >
> > 1. copy rex to stable on some day
> >
> > 2. Let each maintainer have the ability to release a package into stable
> > or unstable for a week or so until rex is officially released as stable
> > and let us be able to submit bugfixes to stable.
>
> The current plan is something similar. Rex will be marked "frozen" and
> a new "unstable" distribution will be created. After a few weeks, the
> frozen release will replace the stable release.
>
I think that there is a different thing to worry about. What if a maintainer
thinks his (or her) package in unstable (rex) isn't yet good enough for the
next stable release? I think there should be a possibility to make sure
a package that is in rex at this time doesn't replace the corresponding
package from buzz, (the cause for this is that I do not want to put the new
procps (>=1.09) into any stable tree before it's officially released by
Charles Blake).
I'm proposing that there must be a way for a maintainer to say which version
of a package should go into the next stable release, most important if
there is a fine stable and BugFree(TM) package sitting in the current
stable tree.
Helmut
------------------------------------------------------------------------------
Helmut Geyer Helmut.Geyer@iwr.uni-heidelberg.de
public PGP key available : finger geyer@kalliope.iwr.uni-heidelberg.de
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: