From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [commit/www] GDB 6.7 schedule updated
Date: Tue, 11 Sep 2007 22:24:00 -0000 [thread overview]
Message-ID: <20070911222421.GJ3666@adacore.com> (raw)
Hello,
Now that we have started the GDB 6.7 release process, I have updated
the schedule. I took this opportunity to throw some tentative dates
for the next release, currently labeled 6.8 (there are some high hopes
that this release contains some major new features warranting an increase
of the major version number).
Here is the new proposed schedule:
CURRENT (6.7) NEXT (6.8)
Branch: September (2007-09-11) February (2008-02-05)
Pre-release: September (2007-09-25) February (2008-02-19)
Release: October (2007-12-09) March (2008-03-04)
reSpin: January (2008-01-08) June (2008-06-03)
2007-09-11 Joel Brobecker <brobecker@adacore.com>
* schedule/index.html: Update schedule for gdb-6.7. Introduce
a proposed schedule for gdb-6.8.
--
Joel
next reply other threads:[~2007-09-11 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 22:24 Joel Brobecker [this message]
2007-09-11 22:31 ` Daniel Jacobowitz
2007-09-11 22:46 ` 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=20070911222421.GJ3666@adacore.com \
--to=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