From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [commit/www] Update schedule
Date: Mon, 08 Jan 2007 05:42:00 -0000 [thread overview]
Message-ID: <20070108054250.GB23012@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
Hello,
I updated the schedule page to include all the details about
the current release (6.6). I also added some tentative dates
for the next release (number 6.7 for now).
I am not sure whether we'll have a 6.6.1 yet or not. We will make one
if and when it makes sense.
As usual, the schedule is not cast in stone. We can always rediscuss it.
2007-01-08 Joel Brobecker <brobecker@adacore.com>
* schedule/index.html: Add 6.6 actual schedule, Add tentative
schedule for 6.7.
Checked in.
--
Joel
[-- Attachment #2: sched.diff --]
[-- Type: text/plain, Size: 1801 bytes --]
Index: schedule/index.html
===================================================================
RCS file: /cvs/gdb/htdocs/schedule/index.html,v
retrieving revision 1.33
diff -u -p -r1.33 index.html
--- schedule/index.html 6 Jul 2006 03:18:07 -0000 1.33
+++ schedule/index.html 8 Jan 2007 05:33:18 -0000
@@ -50,19 +50,19 @@ Fish]" /></a>
<center>
<table>
-<tr><td></td><th>CURRENT (6.5)</th><th>NEXT (6.6)</th>
+<tr><td></td><th>CURRENT (6.6)</th><th>NEXT (6.7)</th>
</tr>
<tr>
-<th>Branch:</th><td>May (2006-05-16)</td><td>October (2006-10-16)</td>
+<th>Branch:</th><td>November (2006-11-15)</td><td>May (2007-05-27)</td>
</tr>
<tr>
-<th>Pre-release:</th><td>June (2006-06-02)</td><td>November (2006-11-06)</td>
+<th>Pre-release:</th><td>December (2006-12-02)</td><td>June (2007-06-10)</td>
</tr>
<tr>
-<th>Release:</th><td>June (2006-06-21)</td><td>November (2006-11-20)</td>
+<th>Release:</th><td>December (2006-12-18)</td><td>June (2007-06-24)</td>
</tr>
<tr>
-<th>reSpin:</th><td>N/A</td><td>January (2007-01-20)</td>
+<th>reSpin:</th><td>N/A</td><td>August (2007-08-24)</td>
</tr>
</table>
</center>
@@ -83,6 +83,8 @@ equivalent amount.
<tr> <th>Release</th><th>Estimate</th><th>Schedule</th><th>Actual</th><th>Slip (months)</th><th align=left>Comment</th></tr>
<tr>
+<td>6.6</td><td>2006-11</td><td>2006-12</td><td>2006-12-18</td>
+ <td align=center></td><th align=left></td> </tr>
<td>6.5</td><td>(none)</td><td>(none)</td><td>2006-06-21</td><td
align=center></td><th align=left></td> </tr>
@@ -185,7 +187,7 @@ Floor, Boston, MA 02110-1301 USA.</p>
<p>Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.</p>
-<p>Last modified 2006-07-05.</p>
+<p>Last modified 2007-01-08.</p>
</address>
</body>
next reply other threads:[~2007-01-08 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 5:42 Joel Brobecker [this message]
2007-01-08 14:24 ` 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=20070108054250.GB23012@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