Hi 
I agree except there are at least 4 approaches that i know of. My post
avoided going down the LTS approach on the grounds that it had been
rejected out of hand already, even though it works well for some.
The Redhat approach is to have 2 distinctly different distros with separate
names and branding. One tests ultra-new technologies often before any
other distros. The other, their flagship one called "Redhat", stays set
for years before getting upgraded. There is a big fuss and much publicity
in the run-up to the upgrade.
Then there's the Debian style, which is roughly what we use. The new
branch has all the exciting experimental stuff in it. Once it's been out
in the wild on real-world machines and on enough bare-metal to shake a
stick at and received plenty of patches and updates the community
eventually decides that in a year or so it can be considered what they call
"Stable branch". Of course when their branch is very fresh and new it is
also stable in the developers way of thinking because it's been tested in
all the ways they reasonably can and is not crashing or anything like that
- so perhaps "Stable" is a bit misleading but it makes intuitive sense to
users so Debian goes with it. Then they have a new "Development branch"
which gets used by pretty much everyone anyway with pretty much all of them
appreciating the opportunity to work with something more advanced than the
standard. It's special and a bit edgy so they feel privileged to use it
and it makes them feel like they are possibly more geeky than they really
are. The 'older' branch, now called "Stable" branch continues to get
security updates and such.
SliTaZ does much the same except they call their newer branch their
"cooking branch" but they are French so it suits them well. Beats mucking
around with horses, right?
These are all not-quite the same as LTS. Everything for the LTS release
has to conform to a MUCH stricter set of rules. So that is all versions of
all packages and modules have to be up to a certain standard otherwise they
risk being left out entirely, perhaps in favour of a competitor. Evolution
couldn't consistently make the standard nor meet any deadlines so for a
long while it consistently got in as an older version but eventually got
ditched in favour of Thunderbird and, i think, Lightning. Even though
Evolution would be more ideal as it's more like a drop-in replacement for
Outlook (hence why it was given so many chances) but it just became
untenable to continue having it as the default.
The LTS does tend to have new features and some extra "wow" factor(s) above
and beyond what could be expected for a normal release. This draws
attention from the press and others who eagerly speculate and anticipate
what may or may not be in it. Discussions rage. But those new features
have often been well and truly tested well in advance but in something
approaching secrecy so that only a few people really know what is going to
be in it.
So with the LTS release it's not just about it getting longer term support
after it's been released. That is, of course, crucial but it's not the
main thing. The main thing is that it's substantially better quality on
it's release date than any other release is on their release date - even
the subsequent next couple of releases. So people often choose the LTS
even after there have been a few more recent releases = because they know
they get better quality.
To me that is substantially better than just using it because it's old!!
It's a huge 'seasonal' boost to their marketing - much the same speculation
and anticipation as before the release of a new iPhone!!
We don't get anything like that level of excitement before the release of a
new branch. We get a bit of fresh interest at each new branch's release
but less and less each time. Maybe it might be possible to learn something
from people who make it to the next plateau up - or perhaps we are more
like Microsoft in being unable to admit that others may have a point. But
perhaps i am wrong and Microsoft, Apple, Google and Ubuntu are really
clueless morons that we have nothing to learn from.
Thanks for the run-down on rolling releases. I knew there had to be
something but i had no idea what. I'd also guessed that people wouldn't
really run into those problems for a couple of years. Right now people are
having the usual teething problems of adapting to a new layout and
presumably the typical problems of using an MS product before "Service Pack
1" - and without the confidence of knowing roughly when the equivalent
might be.
Thanks and regards from
Tom 