Re: Two more concrete ideas for what a once-yearly+update schedule would look like

["Gerald B. Cox" <gbcox@xxxxxx>]

On Tue, Dec 20, 2016 at 5:45 PM, Rahul Sundaram <metherid@xxxxxxxxx> wrote:

Well, it isn't some theoretical construct... it's being done now with KDE and has

been working just fine.  It stays in updates-testing until you decide to push it to stable.  KDE

folks by and large want the updates as fast as possible.  If the GNOME folks would like

their updates to age for six months, they can just keep them in updates-testing.   Seems

like we're just making this more complicated than it is.

You can't keep things simmering in updates-stable for a long time.  What if you need to push a bug fix or security fix that is not tied to a new major upstream release?

Rahul 

I was just repeating what I thought was a good suggestion - which is based upon what has 

already been implemented using the current infrastructure.  Reserve "new" releases only for things

that absolutely require it and let everything else be updated piecemeal.  

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx