From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Release numbering (was Merge Window Closed.)
Date: Wed, 29 Aug 2007 22:16:22 +0200 [thread overview]
Message-ID: <20070829201622.537532474A@gemini.denx.de> (raw)
In-Reply-To: Your message of "Wed, 29 Aug 2007 10:55:34 EDT." <46D588E6.3020209@smiths-aerospace.com>
Hello,
in message <46D588E6.3020209@smiths-aerospace.com> you wrote:
>
> What about adopting Ubuntu's philosophy and numbering by year and month Y.M?
> <http://www.ubuntu.com/aboutus/faq>
To be honest: I don't like it. No rational reason, just gut feeling.
> This has the disadvantage of not clearly marking major changes
> (discontinuities) e.g. 1.x -> 2.0 or 1.2.y -> 1.3.0. Assuming there
> are no earth-shattering discontinuities in the future, that isn't a
There will be such things, I guess... 2.0 is already in a repo...
> 1) It acknowledges that u-boot (as with most open source projects) is
> subject to continuous rolling improvement.
Oops? I don't see any difference for this between onve versioning
scheme and any other, as long as the versions change frequently ;-)
> 2) It eliminates the debate of whether the major or just the minor
> number needs to be rolled.
ACK. But actually this is more a disadvantage - see above.
> 3) When someone says "my build based on version 7.8 is broken" we can
> scale our scorn based on how old the release is without having to look
> it up. ;-)
I never look this up. Anything that is not TOT is "too old" :-)
> 4) This is also in line with Linus's current philosophy that the kernel
> will be 2.6.xxxxxx forever. (I suspect this won't hold literally true
> forever, I predict the "2.6" prefix will eventually be dropped.)
Ummm... but Linux does NOT use da date based version number.
> Going to date-based numbering makes a lot of sense to me.
I feel this is mostly a matter of taste.
I have been using date based labels all the time when U-Boot was
still in CVS (see all the LABEL_200y_mm_dd_HHMM tags we have). And I
must say that I really got sick of this. It served a specific need in
CVS, but I never needed this again in git. If it was not for a public
release process I wouln't need any version number at all. But
whatever we may use, please not date based stamps. I think they are
*stupid*. JUst my 0.02 EUR.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The White Rabbit put on his spectacles. "Where shall I begin, please
your Majesty ?" he asked.
"Begin at the beginning,", the King said, very gravely, "and go on
till you come to the end: then stop." -- Lewis Carroll
next prev parent reply other threads:[~2007-08-29 20:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 12:13 [U-Boot-Users] Merge Window Closed Wolfgang Denk
2007-08-19 16:10 ` Dirk Behme
2007-08-19 16:34 ` ksi at koi8.net
2007-08-27 16:41 ` Dirk Behme
2007-08-27 18:54 ` Wolfgang Denk
2007-08-29 14:55 ` [U-Boot-Users] Release numbering (was Merge Window Closed.) Jerry Van Baren
2007-08-29 15:28 ` Ben Warren
2007-08-29 20:16 ` Wolfgang Denk [this message]
2007-08-29 18:21 ` [U-Boot-Users] Merge Window Closed Michal Simek
2007-08-29 18:42 ` Jon Loeliger
2007-08-29 20:23 ` Wolfgang Denk
2007-08-30 7:29 ` Michal Simek
2007-09-11 20:47 ` Wolfgang Denk
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=20070829201622.537532474A@gemini.denx.de \
--to=wd@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.