This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC version bikeshedding


> I think that if anybody has strong objections, now is the time to make
> them.  Otherwise I think we should go with this plan.

IMHO the cure is worse than the disease.

> Given that there is no clear reason to ever change the major version
> number, making that change will not convey any useful information to
> our users.  So let's just drop the major version number.  Once we've
> made that decision, then the next release (in 2015) naturally becomes
> 5.0, the release after that (in 2016) becomes 6.0, etc.

I don't really understand the "naturally": if you drop the major version 
number, the next release should be 10.0, not 5.0.  Here we seem to be leaning 
towards a weird scheme where we retain the major version number but change its 
meaning, which will be even more confusing than the current scheme.

-- 
Eric Botcazou


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]