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 "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.
I have not been around the last time a "stable" release was made so
forgive my ignorance but the way it was done last time seems strange
to me.
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
{} Consulting available for Networking / Unix / Crossplatform integration {}
{} Snail Mail: FTS Box 466, 135 N.Oakland Ave, Pasadena, CA 91182 {}
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5
--
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: