Sure, the original entry was mainly a placeholder until I got home, but that seems to have a nice ring to it. The idea is to help people who need the info, so any feedback is great.Lysander wrote: It was a very good post - I think a better link title [esp for new users like me] would be something like "[help on] deciding whether to upgrade after a full freeze".
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Moving to Stretch - too early?
- Ardouos
- Posts: 1077
- Joined: 2013-11-03 00:30
- Location: Elicoor II
- Has thanked: 1 time
- Been thanked: 4 times
Re: Understanding the Debian Release Cycle
There is only one Debian | Do not break Debian | Stability and Debian | Backports
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
Re: Understanding the Debian Release Cycle
Abusive ... and simply wrong.dasein wrote:One last tangential point: talk of "live testing" post-release is utter nonsense and betrays a complete ignorance of Debian's release cycle. The "live testing" phase of Testing's existence occurs between releases, not after a release. Once a new Stable is released, it does not get routine bug fixes
Once Stable has been released it in effect enters a phase of widespread live/operational testing by the general public and from that additional bugs will be identified by such broad real-world usage. Fixes for those bugs are either released asap when a security-issue/major bug, released as part of the next point release https://www.debian.org/News/2017/20170114 if a significant bug, or left as-is if a minor bug. Clearly my quoted 'live testing' description was in reference to that post release period.
Re: Moving to Stretch - too early?
Wow.
Don't you ever get tired of being wrong?
It's tragic when someone is incapable of recognizing that the "evidence" they cite actually supports the contrary position.
Take for example the point-release announcement for Debian 8.7, cited in the previous post (https://www.debian.org/News/2017/20170114)...
The vast majority of the 87 entries identified as "miscellaneous bugfixes" in that announcement were deployed in response to 94 distinct security issues, identifiable by the acronym CVE (Common Vulnerabilities and Exposures). Among the specific vulnerabilities addressed by these "miscellaneous" fixes: overflow conditions, memory leaks, and arbitrary code execution.
No one disputes that Stable gets security fixes. But Stable does not receive routine bugfixes, which helps to explain why the current Stable has over 200 RC bugs open against it.
As seen at a recent "Science March":
Don't you ever get tired of being wrong?
It's tragic when someone is incapable of recognizing that the "evidence" they cite actually supports the contrary position.
Take for example the point-release announcement for Debian 8.7, cited in the previous post (https://www.debian.org/News/2017/20170114)...
The vast majority of the 87 entries identified as "miscellaneous bugfixes" in that announcement were deployed in response to 94 distinct security issues, identifiable by the acronym CVE (Common Vulnerabilities and Exposures). Among the specific vulnerabilities addressed by these "miscellaneous" fixes: overflow conditions, memory leaks, and arbitrary code execution.
No one disputes that Stable gets security fixes. But Stable does not receive routine bugfixes, which helps to explain why the current Stable has over 200 RC bugs open against it.
As seen at a recent "Science March":
Last edited by dasein on 2017-05-03 03:11, edited 1 time in total.
Re: Understanding the Debian Release Cycle
Since I was in the neighborhood anyway...
My only suggestion regarding link text might be to frame it as the question it's meant to answer. Something like "Switch to Stretch now or wait until release?"
I'm deeply flattered that you thought my post was worthy of a siglink, even for just the next few months.Ardouos wrote:The idea is to help people who need the info, so any feedback is great.
My only suggestion regarding link text might be to frame it as the question it's meant to answer. Something like "Switch to Stretch now or wait until release?"
Re: Understanding the Debian Release Cycle
I've framed this in a different way as you can see from my sig, since it relates, and will relate, to releases other than just Stretch.dasein wrote:Since I was in the neighborhood anyway...
I'm deeply flattered that you thought my post was worthy of a siglink, even for just the next few months.Ardouos wrote:The idea is to help people who need the info, so any feedback is great.
My only suggestion regarding link text might be to frame it as the question it's meant to answer. Something like "Switch to Stretch now or wait until release?"
- Ardouos
- Posts: 1077
- Joined: 2013-11-03 00:30
- Location: Elicoor II
- Has thanked: 1 time
- Been thanked: 4 times
Re: Understanding the Debian Release Cycle
I feel for now it would be best to use Stretch as it is close to release, I will then change it to something a bit more generic after release if I feel the sig is still needed... Which it generally does every time testing is frozen.Daesin wrote: My only suggestion regarding link text might be to frame it as the question it's meant to answer. Something like "Switch to Stretch now or wait until release?"
Last edited by Ardouos on 2017-05-03 12:49, edited 1 time in total.
There is only one Debian | Do not break Debian | Stability and Debian | Backports
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
Re: Moving to Stretch - too early?
A bug is a failing to operate as intended. Some bugs can be exploited, others are purely cosmetic. Bugs with security or severe operational implications are looked at to be fixed/rolled out to the current stable, those that are cosmetic don't.
Nice pic BTW, looks like you were enjoying yourself.
Nice pic BTW, looks like you were enjoying yourself.
Re: Understanding the Debian Release Cycle
In fairness, two years of intervening cruft is a formidable obstacle. (Let's face it: I was willing to retype the answer rather than find my answer from two years ago.) During those two years, no one has occasion to ponder the question because it's just not relevant. And during those two years, new Debianites who've never experienced a freeze do turn up.Ardouos wrote:Which it generally does every time testing is frozen.
P.S. Purely pedantic and tangential point: the quote you attributed to lysander is actually me.
- Ardouos
- Posts: 1077
- Joined: 2013-11-03 00:30
- Location: Elicoor II
- Has thanked: 1 time
- Been thanked: 4 times
Re: Understanding the Debian Release Cycle
True, I tend to find that I do get more results by filtering through a search engine for this forum, rather than using the search builtin. It may will be a permanent sig if nothing I find more useful turns up.dasein wrote: In fairness, two years of intervening cruft is a formidable obstacle. (Let's face it: I was willing to retype the answer rather than find my answer from two years ago.) During those two years, no one has occasion to ponder the question because it's just not relevant. And during those two years, new Debianites who've never experienced a freeze do turn up.
It is such a shame that we cannot use more than 5 urls in a sig.
Sorry, not sure how that happened. Thank you for pointing it out, as credit is always where it is due.dasein wrote: P.S. Purely pedantic and tangential point: the quote you attributed to lysander is actually me.
There is only one Debian | Do not break Debian | Stability and Debian | Backports
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
Re: Understanding the Debian Release Cycle
That's actually one of the reasons I changed the topic line for that particular post--to make it easier to find two years from now. ;-PArdouos wrote:It may will be a permanent sig if nothing I find more useful turns up.
I was thinking more along the lines of blame, but hey, to-MAY-to/to-MAH-to.Ardouos wrote:Sorry, not sure how that happened. Thank you for pointing it out, as credit is always where it is due.dasein wrote:P.S. Purely pedantic and tangential point: the quote you attributed to lysander is actually me.
As for how it happens (and it's happened to me), I blame gremlins.
-
- Posts: 459
- Joined: 2013-06-16 00:10
Re: Moving to Stretch - too early?
I had this little-used Jessie partition on another system and decided to upgrade it to Stretch, just for fun. It wasn't. I don't know if the theme engines or applications are just in transition (which is my first guess), or if it's the way they're going to look for now on, but it was uh-glee. It threw me off because I had tried it in a VM back in August and Stretched looked just like Jessie. Guess that's why they call it unstable
the crunkbong project: scripts, operating system, the list goes on...bester69 wrote:There is nothing to install in linux, from time to time i go to google searching for something fresh to install in linux, but, there is nothing
Re: Moving to Stretch - too early?
I've been in Stretch for quite a while and i haven't experienced any breakage at all, just be prepared with your Super-Debian Engineer Toolkit and you will be ready to go.
I would exchange everything I know in exchange for half of what I don't.
Re: Moving to Stretch - too early?
I started using Stretch in January. Have had zero problems with it.
It don't think it's too early to move on from current stable, unless you're using Debian for production purposes.
It don't think it's too early to move on from current stable, unless you're using Debian for production purposes.
Debian 12 Stable with sway
Secure your stuff: Securing Debian Manual
Don't break your stuff: Source List Management DontBreakDebian
Secure your stuff: Securing Debian Manual
Don't break your stuff: Source List Management DontBreakDebian
Re: Moving to Stretch - too early?
Stretch is quite different from Jessie. That's normal with new releases. I have a /var/mail log with lots of changes in the way bits are configured and used. So, do a full backup before attempting an upgrade. I recommend cloning the entire Jessie, including Grub, to a spare drive and checking it for operation. Doing so provides a drop-in replacement when things go south.