From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: gdb-7.12 timeframe?
Date: Thu, 21 Jul 2016 10:32:00 -0000 [thread overview]
Message-ID: <CAH=s-POFXVkCDOSTZu+_0D4QBidALhYfLtRpa9LGTQiVV=gVxw@mail.gmail.com> (raw)
In-Reply-To: <20160720172417.GA3601@adacore.com>
On Wed, Jul 20, 2016 at 6:24 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Hello,
>
> It's been almost 6 months since we started our previous release
> cycle, so now is a good time to consider whether or not we feel
> we have enough goodies to start a new process.
>
> We have two questions to answer:
>
> 1. When to start the process (ie stabilize master and create
> the release branch);
>
> 2. What timeframe to shoot for in terms of the 7.12 release.
>
> The part that worries me is that we're about to enter the month
> of Aug, which is traditionally a very slow month due to summer
> holidays.
>
> What I would like to propose is we try to create the branch soon.
> This means we make a call for blocking issues before the branch
> is created, and create the branch, say, one week from now.
> Issue a first pre-release then.
We need collect issues first, and decide whether one week is enough to
stabilize the master and create branch then. I didn't follow the regression
tests in buildbot, but I'll take a look.
Do we have a wiki page to track all these issues for release?
>
> Meanwhile, we can try fixing all reported issues that were found
> and deemed blocking for the release. To avoid having some issues
> being reported too late, I propose we wait for September to make
> our the 7.12 release. If necessary, we can make a second pre-release
> early september.
I have a travel at the end of the Sep, but I think 7.12 is already
released then.
The time is good to me.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-07-21 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 17:24 Joel Brobecker
2016-07-21 10:32 ` Yao Qi [this message]
2016-07-21 11:05 ` Pedro Alves
2016-07-21 12:52 ` Joel Brobecker
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='CAH=s-POFXVkCDOSTZu+_0D4QBidALhYfLtRpa9LGTQiVV=gVxw@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--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