From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Changing GDB's version numbering scheme
Date: Mon, 10 Sep 2018 12:24:00 -0000 [thread overview]
Message-ID: <83a7oppmkd.fsf@gnu.org> (raw)
In-Reply-To: <20180910084934.GB3234@adacore.com> (message from Joel Brobecker on Mon, 10 Sep 2018 09:49:34 +0100)
> Date: Mon, 10 Sep 2018 09:49:34 +0100
> From: Joel Brobecker <brobecker@adacore.com>
>
> The proposal, to avoid this issue, is to change the version numbering
> scheme to increment the major version for each release branch.
With the current release schedule, you will have the major version
increase very rapidly, for no good reason, because, for example, the
difference between GDB 8.1 and 8.2, feature-wise, is very small, so is
not really appropriate (IMO) for a new major version.
Do we care about this downside?
next prev parent reply other threads:[~2018-09-10 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 8:49 Joel Brobecker
2018-09-10 12:24 ` Eli Zaretskii [this message]
2018-09-10 16:57 ` Simon Marchi
2018-09-10 17:08 ` André Pönitz
2018-09-10 17:32 ` Joel Brobecker
2018-10-31 17:25 ` Joel Brobecker
2018-11-01 9:31 ` Alan Hayward
2018-11-06 22:27 ` Tom Tromey
2018-11-07 16:46 ` John Baldwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a7oppmkd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox