On 2016-04-18 3:21 PM, Holger Levsen wrote: > Not neccessarily: > > At first, sway will be uploaded to "unstable" and unstable is actually quite > very uptodate. After some days and if it's free from bugs of severity > "serious" and higher, it will automatically migrate to "testing". > > So unstable and testing are actually usually quite uptodate and people run > unstable and testing and they are used to create a number of popular > derived distros, *buntu is one of them. So it's useful to have sway > there and updated regularily. > > And then, there will be a freeze of testing at the end of this year and > then sometime next year testing will be declared "stable". stable is > free of major changes (well, except for firefox and the kernel and > someā¦) and in general only receives security fixes.
This sounds fairly sane. > One easy way of preventing sway from being released as stable is to file > a RC bug to prevent it from entering "testing". Would be nice to prevent it from getting into stable prior to 1.0, but post 1.0 I'm fine with it. -- Drew DeVault