Bug 7667 - Non-standard and confusing release numbers
Summary: Non-standard and confusing release numbers
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client platforms (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on: 3338 4885
Blocks: 7668
  Show dependency treegraph
Reported: 2021-03-25 10:43 CET by Pierre Ossman
Modified: 2021-06-08 13:10 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2021-03-25 10:43:41 CET
Right now we use the build number as the release number for our packaging. This is not how release numbers are normally set and so can be confusing for users.

Normally release numbers are increased whenever something changes with the packaging itself, rather than the stuff inside the package. The release number is also reset to "1" every time a new version comes out.

Looking at Google Chrome (another commercial and proprietary packager), they follow this: google-chrome-stable-89.0.4389.90-1.x86_64

There are two practical problems to solve:

 a) We set the release number to the build number, but we also do the opposite as rpmbuild is currently an integral part of how we build things. We'd likely need to fix bug 3338 and bug 4885 first in order to break this dependency and make release number and build number independent.

 b) New release numbers makes it easy to upgrade development builds. This won't affect users as they should only upgrade between versions, but our developers will be constantly upgrading to newer builds. For them it would be useful if the version or release number somehow constantly increases during development.
Comment 1 Pierre Ossman cendio 2021-03-25 10:56:44 CET
On the same note, packaging formats that don't naturally have release numbers should probably have those removed. E.g. the macOS .iso.

Note You need to log in before you can comment on or make changes to this bug.