Jaunty still in Beta?

[Dotan Cohen]

> Conf changes are dealt with during updates. The update manager *should*
> be telling the user about the changes and asking for suggestion what to
> do with them (install new version, see diffs, leave them alone, etc.).
> For a taste, try aptitude (command line) for an update which involves
> conf changes. This happens all the time in Debain Testing and more
> frequently in Debain Unstable. Aptitude is designed to deal with these
> things gracefully. In your case, if the GUI update manager does not deal
> with these gracefully, then the GUI manager is broken in some way.
> Please file a bug.
>

I update via apt-get, not some GUI. And the alphas and betas are not
designed to be updated into a release. It's nice that it happens to
work out, but that is not what they are designed for.

> Again, other than bugs and stability (including conf changes), nothing
> is different. If the release notes tell otherwise, that is just an
> aspect of stability and bug fixes. But aptitude tracks the same release
> as it evolves. By the time you reach a stable release, it is no
> different than a newly installed release except your own conf changes.
>

That is wrong, many removed features still leave config files lying
around, that will bite you when they are added in future versions if
not purged.

I'm not going to fight with you or convince you. If you want to update
alpha-beta-RC-release then go for it, I do not administer your system.
But do not think that you are following a safe upgrade path.

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il