From: Andrew Cagney <ac131313@cygnus.com>
To: gdb@sources.redhat.com
Subject: 5.1 release schedule
Date: Wed, 11 Jul 2001 14:39:00 -0000 [thread overview]
Message-ID: <3B4CC790.8090807@cygnus.com> (raw)
So here is the theory.
2001-07-08 (ish) I sent out the 5.1 NEWS, README, ... requests.
2001-07-15
Send out ``I intend to branch in 7 days'' e-mail (2001-07-15 + 7 ==
2001-07-22).
2001-07-22
Cut branch. Create first release candidate.
Send out ``I intend to create final candidate in 7 days'' e-mail
(2001-07-22 + 7 == 2001-07-29).
2001-07-29
Create final release candidate.
Send out ``I intend to release final candidate in 7 days'' e-mail
(2001-07-29 + 7 == 2001-08-05).
2001-08-05
Release GDB 5.1
Is there anything else that should be done? The biggest I know of is to
get the official web page http://www.gnu.org/software/gdb/ updated.
That in turn means getting the unofficial http://sources.redhat.com/gdb/
pages cleaned up so that one can be a mirror (or as close to) of the other.
enjoy,
Andrew
next reply other threads:[~2001-07-11 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 14:39 Andrew Cagney [this message]
2001-07-11 15:08 ` Daniel Jacobowitz
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=3B4CC790.8090807@cygnus.com \
--to=ac131313@cygnus.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