I’m courious about your opinion: Did you observe advantages of Leap over Tumbleweed?
Well, the main “advantage”/difference IMHO is the same as 13.2 (or any other release) has over Tumbleweed:
It’s “stable”, i.e. you don’t get a completely new system every few days, just selected bugfix/security updates.
Some people see this as disadvantage though… 
Yes for stability, although Leap is very new and unproven over time.
No, Tumbleweed doesn’t get “a completely new system” every few days, on average I would say 10 to 15 percent of the installed packages get updated regularly. So far it has been incredibly reliable for that amount of regular change, including those larger updates when KDE or Gnome gets a new version.
The point is that Leap 42.1 is frozen (like any other release) and only gets security and bugfix updates during its lifetime.
With Tumbleweed any package can be upgraded to a completely new version any time.
Which might bring in problems, and be it just that you have to adapt some config files…
And if a low-level package is upgraded, it might also result in a lot of other updates (because all packages that depend on it might have to be rebuilt). Not only a new GNOME or KDE version can cause that.
Again, just to be clear here: with “stable” I meant, there are no changes (except for bugfix and security updates). Not that it works stable.
I thought that was clear from my post.
Yes, and in theory Leap should be the stable one over time.
With Tumbleweed any package can be upgraded to a completely new version any time.
Which might bring in problems, and be it just that you have to adapt some config files…
And if a low-level package is upgraded, it might also result in a lot of other updates. Not only a new GNOME or KDE version can cause that.
Yes, in theory it could increase instability. I have said elsewhere it’s inherently unstable due to frequent change, but so far from my point of view that potential for instability hasn’t materialized as an unreliable system. However I wouldn’t use it for daily business transactions involving revenue.
Again, just to be clear here: with “stable” I meant, there are no changes (except for bugfix and security updates). Not that it works stable.
I thought that was clear from my post.
I prefer to use “stable” in the same way, but not everyone reads it that way. 
This is indeed at least partly about the semantics of “stable”.
For me stable means also that I do not get changes in my day-to-day end-user experience. That is: no other view of an application. Even if they say, but it has still the same features (and more). When a button is not on the same place as yesterday, I will be very upset.
Thus Tumbleweed is not “stable” for me, how much bugfree it may be.
I’m not really talking about “instability” here, as in crashes, problems, or things like that.
Again, I’m talking about “changes” or the amount of updates.
I prefer to use “stable” in the same way, but not everyone reads it that way.
I know, but I did even try to clarify what I mean with “stable” here in the very same sentence where I used that word.
Echoing what many others have said here, basically this comes down to you and what you’re using this build for, in my opinion. If this system is being used for daily production business tasks, I would advise you against using Tumbleweed and say stick to 13.2 or leap 42.1. If you are just getting a test/play/tinkering Linux box up and running, and do not mind troubleshooting perhaps more frequently, then Tumbleweed might be a good option for you.
Hope this helps, thanks and good luck!
I wonder if with Leap’s availability to be more “traditional” (meaning, with speicifc releases) and focus on the “stability”, in part with use of the enterprise-based underpinnings will open up Tumbleweed to be more aggressive with updates and willing to reduce it’s bug-free quality?
So far I have only found minor niggles with Tumbleweed but it also means just about anything can work its way into a full-blown issue. If I am willing to take that risk then Tumbleweed is a good means to go and so far it has proven to work well overall (for a rolling-release distribution).
I think Leap will be great for servers (where things don’t change as quickly, or without a lot of bug-testing) as well as desktops where one does not want things to change or absolutely, positively needs to work when one sits down in front of it.
But this brings up a question: what about application updates such as newer version of Firefox or PDF readers or the like? Sometimes the updated versions include security improvements that are not necessarily a security “fix”, or could include new features. Will they be back-ported to Leap, or wait until the next SP update?
I believe the answer to your question lies in the amount of testing the two versions have undergone, in terms of time and people hours.
Comparing openSUSE with Debian for instance, Debian has three editions: Stable, Testing and Unstable. Obviously, Stable has had more Testing than Unstable. (However, some distros are built on Debian Unstable and are never-the-less stable -Semplice, for example- because Semplice uses it’s own repositories, the contents of which are tested and found to be compatible).
And Debian “Testing” becomes integrated into Debian Stable, eventually. For those that prefer to be on the cutting edge, distros like Sparky are created from Debian Testing and maintained - supported so that any problems that do arise are discovered and a solution is found very quickly.
Rolling versions like the Arch derivative Manjaro function in a similar way. The crux of the matter is Teamwork (and putting a Team together), so that when no one was available to maintain Manjaro’s Openbox version, it became less stable and was eliminated from Manjaro’s two default varieties (Xfce & KDE) and placed within the community versions.
None of this is static - that is, written in stone.
It’s a matter of looking for a better way.
I am posting this with Leap 42.1 Xfce and frankly, I was surprised to find that it was submitted before multimedia codecs were available. (On the other hand, I was able to install it on my birthday and the date was already set - and have everything else working as it should).
The point being, the words are relative and depend on the use people give them.
The above are examples of how I understand it. People from the Leap and Tumbleweed Teams would be better prepared to answer your question (but may not agree with each other).
You could install them both and post the results here.
No.
There wouldn’t have been a reason to “create” Tumbleweed (and the new testing process) in the first place then.
But this brings up a question: what about application updates such as newer version of Firefox or PDF readers or the like? Sometimes the updated versions include security improvements that are not necessarily a security “fix”, or could include new features. Will they be back-ported to Leap, or wait until the next SP update?
It won’t be much different to previous openSUSE releases.
In general only bugfix/security updates will be released.
New versions of selected applications (Firefox e.g.) will be released as standard updates too though, because backporting the security fixes would be too much effort or impossible.
With 42.2 (aligned to SLE12 SP2), all packages will be rebased to the latest versions, either from Tumbleweed/Factory or SLE12 SP2.
Why would you imagine that my original “Yes, in theory it could increase instability.” would not be talking about “changes or the amount of updates”???
The word “instability” is defined in English primarily as a lack of stability (firmly fixed, established).
You started talking about the reliability, and suggested “stable” could also be interpreted as something else, although I think I made it clear what I mean…
The word “instability” is defined in English primarily as a lack of stability (firmly fixed, established).
It’s you that started a senseless discussion again.
Please gentleman.
I thought that a bit of explanation bout stability of software (not the globe) may be needed, mostly to the OP. Because imho many interprete it as “bugfree” and others as “no changes whatsoever”. Both may be valid, but in a discussion it is nice when everybody uses a word in the same meaning.
Well, my question wasn’t clear enough, I guess. I mean, can anybody who used Tumbleweed and now installed Leap tell something about the difference, from his or her own experience? I have been using TW for many monthes on a “productiv system” (my laptop) without serious obstacles. So will I have any benefit from upgrading to Leap?
You apperently went from a “stable” release (13.1 or 13.2) to a rolling release (TW) for reason(s) you do not mention. And now you want us to tell you for what reason(s) you should revert to using a “stable” one (13.1, 13.2 or 42.1)?
You are the only one that can decide if you need a stable or a rolling release for every system you manage. Both types of releases have there pros and cons depending on what you use a system for. But I guess hopping to and fro is another approach (mostly called: testing) 
If you are happy with Tumbleweed, then stay with it.
I was thinking about to upgrade from 13.2 to Tumbleweed, instead of Leap 42.1. Some of the additional repositories I am using are not all on Tumbleweed.
djviking@linuxbox:~> zypper repos --uri
# | Alias | Name | Enabled | GPG Check | Refresh | URI
---+------------------------------+------------------------------------+---------+-----------+---------+----------------------------------------------------------------------------------------------------
1 | Development_SCM_Git | Development SCM Git | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/devel:/tools:/scm/openSUSE_13.2/
2 | Games | Games | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/games:/tools/openSUSE_13.2/
3 | KDE_Applications | KDE Applications | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_13.2/
4 | KDE_Extra | KDE Extra | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_13.2/
5 | KDE_Frameworks | KDE Frameworks | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_13.2/
6 | KDE_Frameworks_5_Additionals | KDE Frameworks 5 Additionals | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Frameworks5/openSUSE_13.2/
7 | KDE_Qt5 | KDE Qt5 | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.2/
8 | LibreOffice | LibreOffice | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/LibreOffice:/Factory/openSUSE_13.2/
9 | Nvidia | Nvidia | Yes | (r ) Yes | Yes | ftp://download.nvidia.com/opensuse/13.2/
10 | Packman | Packman | Yes | (r ) Yes | Yes | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_13.2/
11 | VideoLan_Client | VideoLan Client | Yes | ( p) Yes | Yes | http://download.videolan.org/pub/vlc/SuSE/13.2/
12 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | http://dl.google.com/linux/chrome/rpm/stable/x86_64
13 | repo-debug | openSUSE-13.2-Debug | No | ---- | Yes | http://download.opensuse.org/debug/distribution/13.2/repo/oss/
14 | repo-debug-update | openSUSE-13.2-Update-Debug | No | ---- | Yes | http://download.opensuse.org/debug/update/13.2/
15 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | ---- | Yes | http://download.opensuse.org/debug/update/13.2-non-oss/
16 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | ( p) Yes | Yes | http://download.opensuse.org/distribution/13.2/repo/non-oss/
17 | repo-oss | openSUSE-13.2-Oss | Yes | ( p) Yes | Yes | http://download.opensuse.org/distribution/13.2/repo/oss/
18 | repo-source | openSUSE-13.2-Source | No | ---- | Yes | http://download.opensuse.org/source/distribution/13.2/repo/oss/
19 | repo-update | openSUSE-13.2-Update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/13.2/
20 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/13.2-non-oss/
Of these the following repositories does not include Tumbleweed:
ftp://download.nvidia.com/opensuse/
http://download.opensuse.org/repositories/devel:/tools:/scm/
http://download.opensuse.org/repositories/LibreOffice:/
http://download.opensuse.org/repositories/KDE:/Qt5/
http://download.opensuse.org/repositories/KDE:/Frameworks5/
http://download.opensuse.org/repositories/KDE:/Applications/
Could that be because Tumbleweed already contains packages with the same version as coming from these? Possibly except for Nvidia.
It is recommended NOT to use the VideoLan repo but get VLC from packman. In the past there has been things put on VideoLan that can break your system.
You don’t need anything from Frameworks since that is what 42.1 uses normally for KDE. I’d at least disable the the non standard repos’s with the exception of packman and remove the NVIDIA driver before upgrade.
To be honest in this case I would do a fresh install transiting from a rolling release to a static one. But that’s me I prefer fresh installs
I keep two partition to use as root so I can test drive a new release until I see if it works well for me. Once I am happy I with the new I mount my home in it and then the old root waits for next release. Thus I always have a stable OS to back into if needed.