An LTS branch isn't needed if you do version controlled releases and sponsor support for versioned releases for at least 3-4 versions back.
To be fair, I've used Slackware long enough to see how maintaining a versioned release can go right, and seen enough of Ubuntu to see how it can go horribly wrong.
Devuan should have at least 3 branches.
Versioned releases released on annual cycles as packages mature.
Unstable but tested branch similar to Slackware-Current in which Versioned releases are established.
Experimental branch for new packages that aren't tested or just slightly tested for buildability in a working environment that will determine what goes into Unstable. This branch should also NOT be part of the mainline availability but accessible through a git/svn/cvs client only for safety reasons, namely preventing someone from blowing their system to Hell.
As releases mature, 1.0 would be maintained until the fourth or fifth release year following, then pastured, regardless of version number. The only time the main number should be changed is IF and ONLY IF glibc is updated, otherwise 1.0 would transmigrate to 1.1.
How does that sound?
Sent from my Windows Phone
________________________________
From: Adam Borowski<
mailto:kilobyte@angband.pl>
Sent: 7/16/2015 9:44 PM
To: dng@???<
mailto:dng@lists.dyne.org>
Subject: Re: [DNG] devuan LTS
On Thu, Jul 16, 2015 at 09:39:41PM -0700, Gregory Nowak wrote:
> the recent discussions here have made me think about what features I
> would like devuan to have which debian doesn't currently have. One
> feature that comes to mind is a long term support branch like what
> ubuntu has.
Since squeeze, every release has amd64+i386-only long term support.
--
⢎⣉⠂⠠⠤⡀⣄⠤⡀⠠⡅⠀⠤⡧⠄⡄⠀⡄⠀⠀⠀⠠⡅⠀⡠⠤⠄⠀⠀⠀⢴⠍⠀⡠⠤⡀⣄⠤⡀⠀⠀⠀⠤⡧⠄⣇⠤⡀⡠⠤⡀⠀⠀⠀⡄⠀⡄⡠⠤⡀⠠⠤⡀⡇⡠⠄⠀⠀⠀
⠢⠤⠃⠪⠭⠇⠇⠀⠇⠀⠣⠀⠀⠣⠄⠨⠭⠃⠀⠀⠀⠀⠣⠀⠬⠭⠂⠀⠀⠀⠸⠀⠀⠣⠤⠃⠇⠀⠀⠀⠀⠀⠀⠣⠄⠇⠀⠇⠫⠭⠁⠀⠀⠀⠣⠣⠃⠫⠭⠁⠪⠭⠇⠏⠢⠄⠀⠄⠀
(
https://github.com/kilobyte/braillefont for this hack)
_______________________________________________
Dng mailing list
Dng@???
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng