<br><br><div class="gmail_quote">On Mon, Jul 14, 2008 at 6:41 PM, C. Scott Ananian <<a href="mailto:cscott@laptop.org">cscott@laptop.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">On Mon, Jul 14, 2008 at 6:24 PM, Eben Eliason <<a href="mailto:eben.eliason@gmail.com">eben.eliason@gmail.com</a>> wrote:<br>
> I think this is still a whole bunch clearer than trying to convince someone<br>
> that version 5 is newer than version 10! (where 10 is a "bugfix" release to<br>
> what used to be version 4.)<br>
<br>
</div>You're undercutting your own points: what does "newer" mean? If you<br>
want chronological "newness", then use ISO8601 dates. Otherwise, just<br>
release a version 11 at the same time as 10, so that versions 10 and<br>
11 are the chronologically newest releases, 11 for 8.2 users and 10<br>
for 8.1 users, and those people using '9' don't get confused. This</blockquote><div><br></div><div>This isn't always possible. If I release version 10 (because it takes advantage of some new feature in a new OS) and then later find out I have a critical bug in an older version of the OS that still has a wide support window, I'm forced to release 11 after 10, even though its an older code base. I'm not concerned at all with temporal newness, or this would be a non-issue.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
really seems like a non-issue to me. If your development style really<br>
wants to use minor versions, make up your own mapping to integers: 5.0<br>
= 500, 5.1=501, etc. But regardless, adding dotted integers for<br>
version numbers isn't a real concern for me: it touches a number of<br>
pieces of code and documentation at this point, but we can go ahead<br>
and make that change early in 9.1 if you like. But it still doesn't<br>
actually do anything towards solving the problem you initially posed:<br>
the only difference between 500 and 5.0 is perceptual.</blockquote><div><br></div><div>I read on our wiki that the version number was supposed to be monotonically increasing. If that were the case, doing as you suggest isn't valid, as I would never be able to release anything with a version below 500 once I had, defeating the purpose. Also, the current page on activity bundles explicitly states that "<span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px; ">Larger versions are considered 'newer'", which is simply not the case, even if we do allow your scheme proposed above, which, I agree, is technically equivalent.</span></div>
<div><span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px;"><br></span></div><div><span class="Apple-style-span" style="font-family: -webkit-sans-serif; line-height: 19px;">- Eben</span></div>
<div><br></div></div>