[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUe-dev] Proposal for more structured version numbering scheme
From: |
Reinhard Mueller |
Subject: |
[GNUe-dev] Proposal for more structured version numbering scheme |
Date: |
Tue, 22 Aug 2006 17:09:40 +0200 |
Hi, all,
I was thinking about introducing a structured version numbering scheme,
along with a stricter handling of stable vs. unstable versions.
This is how I thought it could work:
gnue-forms-0.6-alpha0
gnue-forms-0.6-alpha0+svn.20060822
:
gnue-forms-0.6-alpha0+svn.20060909
gnue-forms-0.6-alpha1
gnue-forms-0.6-alpha1+svn.20060910
:
gnue-forms-0.6-alpha1+svn.20061020
gnue-forms-0.6-beta1
gnue-forms-0.6-beta2
gnue-forms-0.6-beta3
gnue-forms-0.6-pre1
gnue-forms-0.6-pre2
gnue-forms-0.6-rc1
gnue-forms-0.6-rc2
gnue-forms-0.6-rc2+svn.20061214
:
gnue-forms-0.6-rc2+svn.20061218
gnue-forms-0.6.0
gnue-forms-0.6.1 (only bug fixes and translation updates)
gnue-forms 0.6.2 (only bug fixes and translation updates)
gnue-forms-0.6.3 (only bug fixes and translation updates)
gnue-forms 0.6.4 (only bug fixes and translation updates)
gnue-forms-0.7-alpha0
etc.
AFAICT, this version numbering scheme would sort correctly both when
sorting strictly by ASCII code, and by debian's version number sorting
scheme.
HEXVERSION could work as follows:
0.6-alpha0 -> 0006a000
0.6-alpha0+svn.... -> 0006a010
0.6-alpha1 -> 0006a100
0.6-beta1 -> 0006b100
0.6-pre1 -> 0006d100
0.6-rc1 -> 0006e100
0.6.0 -> 0006f000
0.6.1 -> 0006f100
Any feedback on this idea is welcome.
Thanks,
Reinhard
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUe-dev] Proposal for more structured version numbering scheme,
Reinhard Mueller <=