[PATCH] D21821: Bump trunk version to 4.0 and switch to new versioning scheme
Tom Stellard via llvm-commits
llvm-commits at lists.llvm.org
Mon Jul 4 12:06:57 PDT 2016
tstellarAMD added a subscriber: tstellarAMD.
tstellarAMD added a comment.
In http://reviews.llvm.org/D21821#470061, @hfinkel wrote:
> > I'm just worried that even if we intend the y in x.y to be interpreted as the patch version, tools and readers of the version string will still interpret it as major.minor.
> > But I've started to like the idea of just using x.y.z with y=0. We'd release 4.0.0, Tom would ship 4.0.1, and then we'd go to 5.0.0. I think the risk of people and tools being confused by that would be very small, and communicating that we're treating each six-month release as major shouldn't be too hard.
> I think this is a good option. It also leaves us free to generate a true minor release at some point in the future should we decide to do so.
I agree with this. If our stable releases are 4.0.1, it gives us the option to create minor releases (e.g. 4.1.0) if we want. One possible use for minor releases would be to backport new features, but not change the API (I'm not saying we should or shouldn't do this, it is just an example).
More information about the llvm-commits