In message <[EMAIL PROTECTED]> you wrote:
>
> A minor :) issue I can see is that there might be *some* confusion 
> because of an apparent, numerical rollback from 1.3.4 back to 1.08.xx. 
> You're bound to encounter some folks who will ask, again and again, why 
> you're  working on 1.02.yy when 1.3.4 is out there.

Good point. I have to admit that I was reading "1.08.xx" same as
1.8.xx; the leading 8 is just there to make sure that 1.08.xx sorts
before 1.10.xx.

> Now an obvious solution would be to use 2 as the major number. If you're 
> serious about not knowing when a major number bump-up is required, then 
> you should be fairly ok with starting at 2.08.01 rather than 1.08.01. :)

Well, the "version 2" prefix is kind of already taken by Sascha Hauers
alternative implementation.

Should we go for 2.x.x anyway?

> Another, maybe trickier, issue is: you won't be able to cleanly number 
> interim releases if you encounter a really serious bug right after 
> you've produced this month's release, will you?

Well, we can always use EXTRAVERSION to add some additional name,  as
we do all the time for our -rc? prereleases.

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: [EMAIL PROTECTED]
I think it's a new feature. Don't tell anyone it was an accident. :-)
  -- Larry Wall on s/foo/bar/eieio in <[EMAIL PROTECTED]>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

Reply via email to