Mailinglist Archive: opensuse-bugs (4067 mails)

< Previous Next >
[Bug 711791] New: Consolidating Terminology in YaST: Update and Upgrade
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 11 Aug 2011 14:29:07 +0000
  • Message-id: <>

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@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: thomas.schraitle@xxxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
CC: ke@xxxxxxxxxx
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

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.


Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >