From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Guillermo Ballester Valor <gbv@oxixares.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Mark Mitchell <mark@codesourcery.com>
Subject: PATCH for Re: GCC development plan Web Page is not updated
Date: Tue, 27 May 2003 19:41:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305272136450.37635@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200305241950.09941.gbv@oxixares.com>
On Sat, 24 May 2003, Guillermo Ballester Valor wrote:
> http://gcc.gnu.org/develop.html#future
>
> perhaps should be updated, at least in GCC 3.3 release and future 3.3.1
> and 3.4
Done thusly. I also fixed the release date of GCC 3.2.3 on the way
(to be the date listed in ChangeLogs and CVS).
Mark, it's probably time to publish a schedule for the 3.3-branch
(3.3.1, 3.3.2) and mainline (end of stages 1, 2, and 3)?
Gerald
Index: develop.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/develop.html,v
retrieving revision 1.31
diff -u -3 -p -r1.31 develop.html
--- develop.html 26 Mar 2003 21:05:39 -0000 1.31
+++ develop.html 27 May 2003 19:36:01 -0000
@@ -265,7 +265,7 @@ stages of development, branch points, an
| GCC 3.2.2 release (Feb 05 2003)
| \
| v
- | GCC 3.2.3 release (April 15 2003)
+ | GCC 3.2.3 release (April 22 2003)
v
GCC 3.3 Stage 2 (ends Aug 15 2002)
|
@@ -275,12 +275,17 @@ stages of development, branch points, an
v
+-- GCC 3.3 branch created ------+
| (Dec 14 2002) \
- : v
- : GCC 3.3 release (...)
- : \
- v
- GCC 3.3.1 release (...)
-
+ | v
+ | GCC 3.3 release (May 13 2003)
+ | \
+ v v
+ GCC 3.4 Stage 1 (ends ... ) GCC 3.3.1 release (...)
+ | \
+ v v
+ GCC 3.4 Stage 2 (ends ... ) GCC 3.3.2 release (...)
+ | \
+ : :
+ v v
</pre>
<hr />
prev parent reply other threads:[~2003-05-27 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 18:06 Guillermo Ballester Valor
2003-05-27 19:41 ` Gerald Pfeifer [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=Pine.BSF.4.55.0305272136450.37635@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gbv@oxixares.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).