From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sources.redhat.com
Subject: Schedule proposal for the next release(s)
Date: Wed, 21 Jun 2006 08:11:00 -0000 [thread overview]
Message-ID: <20060621074033.GF976@adacore.com> (raw)
Hello,
Now that GDB 6.5 is out, here is what I propose in terms of the next
major release schedule (in all likeliness labled GDB 6.6).
I would like to schedule the next release around begining of Dec 2006.
Working backwards, and substracting a month from it, it would mean that
we need to branch early Nov 2006. Allowing for unexpected problems,
let's give us another 2 weeks, that would mean actual branching date
around Oct 15. So I propose:
* Branch : 16-OCT-2006
* Pre-release : 06-NOV-2006 (3 weeks later)
* Release : 20-NOV-2006 (2 weeks after)
I think that should give us enough time to do some testing before
the pre-release and then before the release.
Opinions?
Also, around the same topic, I mentioned to the GDB developers that
the question of making a minor release of the GDB 6.5 branch is still
open. Decision in a couple of month at the latest, depending on what
critical fixes we have.
--
Joel
next reply other threads:[~2006-06-21 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 8:11 Joel Brobecker [this message]
2006-06-24 2:26 ` Nick Roberts
2006-06-24 7:40 ` Joel Brobecker
2006-07-05 22:47 ` Joel Brobecker
2006-07-05 23:22 ` Nick Roberts
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=20060621074033.GF976@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sources.redhat.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