Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: gdb-7.12 timeframe?
Date: Thu, 21 Jul 2016 12:52:00 -0000	[thread overview]
Message-ID: <20160721125233.GA4846@adacore.com> (raw)
In-Reply-To: <CAH=s-POFXVkCDOSTZu+_0D4QBidALhYfLtRpa9LGTQiVV=gVxw@mail.gmail.com>

> > 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.

Thanks for taking a look at the buildbot results.

Regarding stabilization, there are two approaches. We can stabilize
master to the point of near-release-readiness, which means we start
holding patches that may be unsafe (a little bit like GCC does).
Or we branch, and then decide which fixes we want for the branch.
I was proposing the latter, which is a little more work for the
branch, but allows development to continue on master. However,
I am happy with either approach. We've used the former in the past,
but given that we're entering the summer holiday period, it might
take a while before we hear from some of us about issues that,
under the stabilize-before-branch policy, we might want to fix
before we branch.

-- 
Joel


      parent reply	other threads:[~2016-07-21 12:52 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
2016-07-21 11:05   ` Pedro Alves
2016-07-21 12:52   ` Joel Brobecker [this message]

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=20160721125233.GA4846@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    /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