From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: Schedule proposal for the next release(s)
Date: Sat, 24 Jun 2006 02:26:00 -0000 [thread overview]
Message-ID: <17564.41525.309789.830784@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060621074033.GF976@adacore.com>
> 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)
If this is agreed I think it should be added to:
http://sourceware.org/gdb/schedule/
which is already out of date.
On a releated note, I think that http://sourceware.org/gdb/current/ need
not mention dejagnu.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-06-24 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 8:11 Joel Brobecker
2006-06-24 2:26 ` Nick Roberts [this message]
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=17564.41525.309789.830784@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=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