[Bug 711791] New: Consolidating Terminology in YaST: Update and Upgrade
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c0 Summary: Consolidating Terminology in YaST: Update and Upgrade Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: thomas.schraitle@novell.com QAContact: jsrain@novell.com CC: ke@novell.com Found By: Documentation Blocker: --- According to FATE#308189: ------------ »In the past, we just used the term "update" for all update related things, because we were told "upgrade" is suitable for hardware related upgrades only. With the advent of zypper, the term "upgrade" (dup, dist-upgrade) is back for upgrading the system complete from one version "n" to the next version "n+1" (yes, you can "upgrade" within one version, but that's a special case...). The term is fine and I'd like us to use "upgrade" in YaST and everywhere else where suitable.« ------------ Ján Kupec gave in the mentioned FATE entry also a very helpful interpretation: ------------ * upgrade = installation of newer (major) version of a package or distribution, which brings NEW FEATURES * update = installation of ANY NEWER VERSION of a package or distro In short, upgrade is 'feature-wise', update is 'time-wise'. If we'd agree on this definition, then: * upgrades are a subset of updates * bug fixes (e.g. openSUSE updates/patches), are mere 'updates' - they should not bring new features * distribution update is always an upgrade - it always brings new features ------------ To give you a little background information: We use almost always the original terms in the software. However, sometimes it conflicts with our own terminology or with other software (compare YaST update vs. zypper upgrade). This makes it almost impossible to maintain a consistent wording throughout all documentation. It is not only about "us" (the doc team), we think about our readers and customers. Our primary goal is to make our documentation easy to read and understand. Different terms confuses our customers. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c1 Thomas Fehr <fehr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@novell.com --- Comment #1 from Thomas Fehr <fehr@novell.com> 2011-08-11 16:37:12 UTC --- Not completely sure why this is assigned to yast2-maintainers. I assume it is to check texts in dialogs regarding the above wording. I assume texts regarding update will most be in package yast2-update and yast2-installation which happen to have the same maintainer so I reassign this to Jiří. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c2 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |thomas.schraitle@novell.com --- Comment #2 from Jiří Suchomel <jsuchome@novell.com> 2011-08-12 06:31:44 UTC --- Well, the discussion says that both terms are valid for their cases, right? So were exactly you mean YaST is not consistent with the meaning of any of the term? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c3 Thomas Schraitle <thomas.schraitle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|thomas.schraitle@novell.com | --- Comment #3 from Thomas Schraitle <thomas.schraitle@novell.com> 2011-08-12 12:38:10 UTC ---
Well, the discussion says that both terms are valid for their cases, right?
Well, depends. :) I guess, they are interrelated and it is sometimes hard which one to choose. However, it would be good to have a clear definition which seems not to be the case (aside from the above FATE entry.) For example, here are two cases in YaST: * When you install openSUSE (or SLE) you can select between "New Installation" and "Update". * YaST Wagon tells about "This tool will help to update the running system to a service pack." Shouldn't both be replaced with "upgrade"? :) Compare it to zypper dist-upgrade (dup). For me, this seems inconsistent. Maybe Karl has a better explanation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c4 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |coolo@novell.com, | |locilka@novell.com InfoProvider| |jsrain@novell.com --- Comment #4 from Jiří Suchomel <jsuchome@novell.com> 2011-08-12 12:54:15 UTC --- I'm not sure. Jiri? Stephan? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c5 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |jsrain@novell.com InfoProvider|jsrain@novell.com | --- Comment #5 from Jiri Srain <jsrain@novell.com> 2011-08-15 08:29:57 UTC --- If we agree with this difference between Update and Upgrade, then yes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c6 --- Comment #6 from Lukas Ocilka <locilka@novell.com> 2011-08-15 09:14:59 UTC --- The difference between Update and Upgrade in YaST used to be this: Update - Takes your system to either the highest possible versions of packages installed (undefined state) or applies online updates (kid-of defined state) - Doesn't change the installed product, just it's parts. - zypper up / zypper patch Upgrade - Switches your system from one (usually defined state) product version to another product version including switching to Service Packs. - Changes the installed product to a different one - zypper dup Sadly, this wording is not well used within our products ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=711791 https://bugzilla.novell.com/show_bug.cgi?id=711791#c8 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FEATURE --- Comment #8 from Jiří Suchomel <jsuchome@novell.com> 2011-08-15 09:19:36 UTC --- Well, I think this should be discussed and resolved in the mentioned feature before any implementation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com