From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: U-Boot version numbering
Date: Fri, 01 Aug 2008 19:44:52 +0200 [thread overview]
Message-ID: <48934B94.7090803@free.fr> (raw)
In-Reply-To: <489336AA.5080701@gmail.com>
Ben Warren a ?crit :
> Kumar Gala wrote:
>> On Aug 1, 2008, at 10:32 AM, Wolfgang Denk wrote:
>>
>>
>>> Hello,
>>>
>>> I would like to get your general opinion about changing the U-Boot
>>> version numbering scheme.
>>>
>>> To be honest, I never really understood myself how this is supposed
>>> to work and if the next version should be 1.3.4 or 1.4.0 or 2.0.0, i.
>>> e. which changes / additions are important enough to increment the
>>> PATCHLEVEL or even VERSION number.
>>>
>>> I therefor suggest to drop this style of version numbering and change
>>> to a timestamp based version number system which has been quite
>>> successfully used by other projects (like Ubuntu) or is under
>>> discussion (for Linux).
>>>
>>> My suggestion for the new version numbers is as follows:
>>>
>>> VERSION = 1 (at least for the time being)
>>>
>>> PATCHLEVEL = current year - 2000
>>>
>>> SUBLEVEL = current month
>>>
>>> Both PATCHLEVEL and SUBLEVEL shall always be 2 digits (at least for
>>> the next 91+ years to come) so listings for example on an FTP server
>>> shall be in a sane sorting order.
>>>
>>> If we accept this system, the next release which probably comes out
>>> in October 2008 would be v1.08.10, and assuming the one after that
>>> comes out in January 2009 would be named v1.09.01
>>>
>> If we go to date based versions. I'd prefer we keep year as 4 digits:
>>
>> v1.2008.10
>> v1.2009.01
>>
>> It just seems easier to me at a visual level when I look at try and
>> compare versions.
>>
>> - k
>>
> I vote for this one, but starting at v2.
Just one thing: Verson numbering can be anything you want, but I think
it should be self-consistent. And on that account, I realize that the
"v1" part has no real meaning wrt to the rest of the version string,
which date-related -- unless there is a plan to have simultaneous v1 and
v2 releases, in which case it makes sense to have "v1".
Amicalement,
--
Albert.
next prev parent reply other threads:[~2008-08-01 17:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 15:32 [U-Boot-Users] RFC: U-Boot version numbering Wolfgang Denk
2008-08-01 15:35 ` Kumar Gala
[not found] ` <c166aa9f0808010839s7cbd81b9j2680ea4a6197bcd8@mail.gmail.com>
2008-08-01 15:40 ` [U-Boot-Users] Fwd: " Andrew Dyer
2008-08-01 18:41 ` Wolfgang Denk
2008-08-01 16:15 ` [U-Boot-Users] " Ben Warren
2008-08-01 17:44 ` Albert ARIBAUD [this message]
2008-08-01 17:51 ` Ben Warren
2008-08-04 7:11 ` Martin Krause
2008-08-01 15:36 ` ksi at koi8.net
2008-08-01 15:44 ` Albert ARIBAUD
2008-08-01 18:45 ` Wolfgang Denk
2008-08-06 16:47 ` Ken.Fuchs at bench.com
2008-08-06 17:42 ` Scott Wood
2008-08-06 18:44 ` Ken.Fuchs at bench.com
2008-08-01 21:47 ` Feng Kan
2008-08-01 22:02 ` Albert ARIBAUD
2008-08-04 7:33 ` Jens Gehrlein
2008-08-01 15:51 ` Hugo Villeneuve
2008-08-01 18:50 ` Wolfgang Denk
2008-08-01 18:32 ` [U-Boot-Users] 1.3.4-rc2 autoboot timeout - MPC8548 Zach Sadecki
2008-08-01 19:01 ` Wolfgang Denk
2008-08-01 18:46 ` [U-Boot-Users] RFC: U-Boot version numbering Adrian Filipi
2008-08-04 16:05 ` Matthias Fuchs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48934B94.7090803@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox