![](https://seccdn.libravatar.org/avatar/25bbc96d9c53647354cb724e744b2222.jpg?s=120&d=mm&r=g)
On October 28, 2014 10:58:53 PM EDT, John M Andersen
On 10/28/2014 7:17 PM, Greg Freemyer wrote:
On October 28, 2014 8:25:07 PM EDT, Neil Rickert
On Tue, 28 Oct 2014 15:51:40 -0700 John Andersen
wrote: So now the big question: When it all goes live next month.....
Regular 13.2 -or- Tumbleweed(new)? Go with 13.2.
Which gives me the best chance of not fighting broken stuff and being reasonably current for the longest time? In that case, go with 13.1, and follow it onto Evergreen support.
Also If you have an opinion: Why would anyone install 13.2 and face an upgrade every X months, when they could just as well run the new Tumbleweed? With a an officially supported rolling release (finally) what is the point of the numbered releases going forward? I'll be installing 13.2. Tumbleweed will probably be fine, and I'll also use that on one computer. But I expect Tumbleweed to break every now and then. It won't be a totally hopeless break (I hope) because of the OpenQA testing. But they don't test everything. They rely on ordinary users to find what is broken in most everyday software.
So I want to have a solid 13.2 around. If traveling with laptop, I don't want to take the risk of Tumbleweed. Something might break at an inconvenient time. And for my main desktop, I also like some stability. Maybe I'll switch that to Tumbleweed as we approach the 13.3 release, but I'll stay with stable for a while. For the lurkers, next week's Tumbleweed is very different from today's so read the news if you don't know what that's about.
==== Basically agreeing with everything Neil said.
Also expect routine Tumbleweed "zypper dup" updates to be large, so don't jump on tumbleweed if you don't have a big pipe and/or can't handle a little adventure in your life.
The new Tumbleweed will likely have 10,000 or more users, so it should be pretty stable, but not as stable as a numbered release.
I'm planning to stick with 13.2 on laptop. My server may not
wrote: transition out of 13.1 until the end of Evergreen support. Greg
Thanks for weighing in...
I was aware that Tumbleweed(new) was going to be very new, and all the write-ups seemed to suggest it was promised to be much more stable and bug free than prior editions, since it is no longer just a spare time project of Greg K-H's. https://news.opensuse.org/2014/10/24/tumbleweed-factory-rolling-releases-to-... That page, and a number of discussions suggested this would much cleaner. I Guess if you don't trust that, its word to the wise, which is exactly
Both of the systems I talked about are "production". I do billable work on both, so I'm somewhat risk averse on them. The old tumbleweed process was: Development / testing of packages in isolation Integration into factory Human testing Selected packages integrated into tumbleweed Tumbleweed released with minimal testing The new process: Development / testing of packages in isolation Integration into factory via rings of testing Automated testing Tumbleweed released with minimal human testing The good news is that the automated testing is pretty complete for core areas and there is no doubt in my mind the new Tumbleweed is more stable than the old factory. Take a little time and review: https://openqa.opensuse.org/ Look at the test results and all the test suites they are running. They have lots of screenshots gathered during the automated testing as well as videos of each test run. I'm no expert on the other distros, but I wonder if any of them have as much automated testing as opensuse factory is now getting? The issue for me is that by definition the packages going into factory are bleeding edge and there is no "human selection" of packages that get moved to the new Tumbleweed. As soon as the automated testing passes for an entire factory snapshot everything in factory gets rolled out to tumbleweed. Part of me thinks that is great, but the risk adverse part of me says "no way."
what I was looking for.
I was hoping a rolling release would keep me from having to do this every 18 months.
"zypper dup" has become pretty stable over the last couple years. Why not just do it every major release (every 8 months)? I had a few issues with systemd after zypper dup to 13.1 from 12.3 but I think that is behind us so moving to 13.2 and future I expect to be smooth.
(Win7 machine: 5 years since installed).
I was planning a totally fresh install, (coming from 12.3 to 13.2 on an in-place update seems a bit hopeful to me), as I need to re-partition my disk anyway).
If you go in-place, I'd download the full DVD and do it off-line. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org