From: John Baldwin <jhb@FreeBSD.org>
To: Simon Marchi <simark@simark.ca>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: GDB 13.2 and GDB 14 releases...
Date: Mon, 1 May 2023 09:16:39 -0700 [thread overview]
Message-ID: <1c15a0de-3b9e-7d34-47b1-5cb69fee2469@FreeBSD.org> (raw)
In-Reply-To: <945cb511-3bd0-7004-caa7-9f0deb76e766@simark.ca>
On 5/1/23 6:37 AM, Simon Marchi via Gdb-patches wrote:
> On 4/29/23 16:15, Joel Brobecker via Gdb-patches wrote:
>> GDB 14.1 Branching and Release
>> ==============================
>>
>> Normally, my default approach is to start talking about the next
>> major release as soon as the previous .2 release is out. The idea
>> is to give ourselve 3 months or so to prepare for it, branch and
>> then release, so as to try to follow a schedule of one major release
>> every 6 months.
>>
>> In this case, I think it's too early to tell. I've looked at the NEWS
>> file, and while there are a number of nice new features, maybe we might
>> want to wait a little longer to see if we can pack this release a little
>> more.
>
> IMO, it's better to make regular releases than waiting to have a certain
> amount of changes. The changes currently in master might not look
> important to me, but maybe someone else is eagerly waiting for a
> specific fix or feature to be officially released.
I'm also a fan of time-based release schedules.
--
John Baldwin
next prev parent reply other threads:[~2023-05-01 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 20:15 Joel Brobecker
2023-05-01 13:37 ` Simon Marchi
2023-05-01 14:58 ` Joel Brobecker
2023-05-01 15:15 ` Sam James
2023-05-02 6:55 ` Hector Martin
2023-05-01 16:39 ` Simon Marchi
2023-05-02 9:23 ` Luis Machado
2023-05-01 16:16 ` John Baldwin [this message]
2023-05-02 12:57 ` Luis Machado
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=1c15a0de-3b9e-7d34-47b1-5cb69fee2469@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).