[cfe-dev] Clang version numbers

[Nikola Smiljanic]

3.6.1 is a dot release and will only contain commits that community decides
to merge from trunk, most likely bug fixes. Not sure how the odd/even
schema you suggest makes anything more intuitive (apart that it matches
what linux kernel does), users would still have to know about the meaning
of our numbers.

I think the only confusing point is that trunk has a version, not sure if
we really need this? I'd expect -version to just say 'trunk' + revision
number.



On Sun, Mar 8, 2015 at 3:51 AM, Robert Ankeney <rrankene at gmail.com> wrote:

> Trunk is always "the next version", 3.6 is whatever is built from 3.6
> branch.
>
> On Wed, Mar 4, 2015 at 3:07 PM, Robert Ankeney <rrankene at gmail.com> wrote:
>
> > Why is the current build calling itself 3.7.0? Since 3.6 was just
> > released, it seems it should be called 3.6.0 or something less confusing.
> >
> > Thanks!
> > Robert
> >
>
> As a user, I find this confusing. The next version could easily be 3.6.1.
> If someone gave me the current release today and I wanted to see what
> features this 3.7 contained, I would quickly discover that 3.6 was the
> current version, and would find this version suspect (unless it came from a
> Time Lord). If I searched after the formal release of 3.7, I would expect
> the 3.7 features listed and bugs corrected shown in the release notes to
> exist in this version. What would be less confusing to me would something
> like calling the current version 3.6.1, where an odd last digit implied an
> interim version, and an even last digit an actual release.
>
> Just my two cents worth.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150308/302b2103/attachment.html>