From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Creating the gdb-6.7 branch soon (3 weeks to go?)
Date: Wed, 09 May 2007 21:55:00 -0000 [thread overview]
Message-ID: <20070509215555.GC3662@adacore.com> (raw)
In-Reply-To: <200705071917.l47JHibW027159@brahms.sibelius.xs4all.nl>
> > We're getting close to the planned branching date for the next GDB
> > release. Branching is planned May 27, a first pre-release 2 weeks
> > after, followed by an official release again 2 weeks after.
>
> It doesn't really work for me; I'll be travelling during most of that
> period.
Given the number of platforms that Mark would be able to test, and
given that there is no imperative that we release by a certain date,
I propose we revise the dates to be:
- Branch date: June 10th
- Pre-release: June 24th
- Release : July 8th (probably 9th, which is a Monday, actually)
That should give Mark enough time to test his configurations before
the pre-release.
Any objection?
--
Joel
prev parent reply other threads:[~2007-05-09 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 18:29 Joel Brobecker
2007-05-07 19:12 ` Daniel Jacobowitz
2007-05-07 19:17 ` Mark Kettenis
2007-05-09 21:55 ` 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=20070509215555.GC3662@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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