This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC version bikeshedding
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Ian Lance Taylor <iant at google dot com>, Jason Merrill <jason at redhat dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 24 Jul 2014 10:39:56 +0200
- Subject: Re: GCC version bikeshedding
- Authentication-results: sourceware.org; auth=none
- References: <20140720165506 dot GT3003 at laptop dot redhat dot com> <7564e4f5-8030-4a23-8b0b-b1262265a349 at email dot android dot com> <20140720170146 dot GU3003 at laptop dot redhat dot com> <53CF8E48 dot 8090003 at redhat dot com> <CAKOQZ8yvTaos4Qo=cBEF070_rZkF9V-2L-76R6i7KLisBMEn-g at mail dot gmail dot com> <20140723200049 dot GA2397 at laptop dot redhat dot com>
On Wed, Jul 23, 2014 at 10:00 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Wed, Jul 23, 2014 at 09:20:23AM -0700, Ian Lance Taylor wrote:
>> I think that if anybody has strong objections, now is the time to make
>> them. Otherwise I think we should go with this plan.
>
> My preference was to keep the current versioning scheme, after all, even
> right now it is IMHO worthwhile to tell users about to significant user
> visible change with libstdc++ ABI.
> But not a strong objection from me.
The point is we have significant user visible changes for each release.
Where the "significance" is of course a subjective matter.
The other thing I could have lived with is doing 4.10.0 (and keeping
the major at 4 forever). But "randomly" bumping the major version
looks crap to me, esp. as 5.0.0 will be seen as very very experimental.
Richard.
> Jakub