[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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.


> The current "stable" version I think does not deserve its name. In the
> beginning I submitted a number of bugs since "stable" packages had bugs
> until someone told me that bugs are not fixed in stable. At that point I
> switched to unstable since that was the release containing the fixes.

My understanding is that there has never been a restriction on submitting
packages into a stable release.  The general policy has been not to
submit new code (i.e. _only_ bug fixes) into stable.  I think the problem
arises from the fact that usually most new release both add functionality
_and_ fix past bugs.  Introducing this version into stable will fix old
bugs, but could also add new ones and incompatibilities with other packages.

                                             
                                          Brian
                                 ( bcwhite@verisim.com )
                                             
-------------------------------------------------------------------------------
     Searching for something?  Look to us!  http://www.verisim.com/ferret/


--
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: