On Fri, Aug 05, 2016 at 07:31:33PM +0200, Kristian Fiskerstrand wrote: > On 08/04/2016 06:24 PM, William Hubbs wrote: > > I feel that our stable tree is so far behind on all > > architectures that we are doing our stable users a disservice, so I > > would like to open up a discussion here, and maybe some policy changes > > at the next meeting. > > Far behind isn't necessarily a problem as long as it doesn't have bugs, > in particular security related ones. Updating too often (without a good > reason) can also be annoying enough. > > > > > Ultimately, I think we need some form of automated stabilization, e.g. > > if a package version sits in ~ for 30 days and there are no blockers at > > that point, the new version should go automatically to stable on all > > architectures where there is a previous stable version. > > I LOUDLY disagree. The stable tree should not be compromised by such > automation, it is already bad enough without proper use-testing in some > cases. Stable isn't only about building properly. and that's why we don't commit straight to stable. people are supposed to be testing those ~arch versions for a while before they go stable. That testing should cover the use cases you are talking about and work out the bugs. Once that's done, we should be able to move the package to stable. William