From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to create the GDB 8.1.x branch?
Date: Wed, 29 Nov 2017 20:58:00 -0000 [thread overview]
Message-ID: <20171129205838.cgn3pttf5rzgjijt@adacore.com> (raw)
In-Reply-To: <861skir32h.fsf@gmail.com>
> Looks I overestimated the period after branch cut and release. I
> thought it is about 4 ~ 5 weeks, so I thought 4 weeks from now on,
> kernel patches *may* be merged, and GDB is not released yet, so I can
> squeeze these gdb patches in to 8.1 release. If the period is only
> 2~3 weeks, I don't want to delay the release. On the other hand, it
> takes some time for distro to pick up the Linux kernel or backport these
> kernel patches, the gdb feature can't be enabled without kernel support,
> so it doesn't matter too much that this feature is in gdb 8.1 or 8.2.
>
> > I don't have a problem with delaying the release after the branch
> > get created, but 5 weeks takes us roughly to start of 2018. I would
> > add an extra week or two after your backport before we actually
> > release, just in case there are unexpected complications with
> > the patch. So, we're talking mid-January.
> >
> > Any objections to a release around that time?
>
> Understood. I withdraw this proposal, and let us target your original
> plan.
Thanks for the update, Yao. I moved your item to the excluded list
for now. But we can still consider it again if conditions become better:
Who knows, if the branch drags longer than anticipated, and the changes
in the kernel get in quickly, it might still make it...
--
Joel
next prev parent reply other threads:[~2017-11-29 20:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 19:15 Joel Brobecker
2017-11-21 10:50 ` Ulrich Weigand
2017-11-27 21:55 ` Joel Brobecker
2017-11-28 19:44 ` Ulrich Weigand
2017-11-28 20:32 ` Pedro Alves
2017-11-29 13:20 ` Pedro Alves
2017-11-29 21:00 ` Joel Brobecker
2017-11-29 21:49 ` Pedro Alves
2017-11-29 22:20 ` Joel Brobecker
2017-11-21 11:10 ` Yao Qi
2017-11-21 12:39 ` Pedro Alves
2017-11-27 22:20 ` Joel Brobecker
2017-11-27 22:41 ` Pedro Alves
2017-11-29 20:56 ` Joel Brobecker
2017-11-29 22:20 ` Pedro Alves
2017-11-29 22:46 ` Joel Brobecker
2017-11-22 13:07 ` Yao Qi
2017-11-27 22:06 ` Joel Brobecker
2017-11-27 22:14 ` Joel Brobecker
2017-11-28 12:38 ` Yao Qi
2017-11-29 20:58 ` Joel Brobecker [this message]
2017-11-22 18:03 ` Sergio Durigan Junior
2017-11-27 22:23 ` Joel Brobecker
2017-11-28 17:08 ` Sergio Durigan Junior
2017-11-23 15:16 ` Pedro Alves
2017-11-23 16:50 ` Joel Brobecker
2017-11-23 17:32 ` Pedro Alves
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=20171129205838.cgn3pttf5rzgjijt@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