| 1 |
Date: Sun, 14 Jul 2002 21:06:30 -0700 |
|---|
| 2 |
From: Mark Mitchell <mark@codesourcery.com> |
|---|
| 3 |
To: gcc@gcc.gnu.org |
|---|
| 4 |
Subject: Release Plan Updates |
|---|
| 5 |
Message-ID: <41980000.1026705990@warlock.codesourcery.com> |
|---|
| 6 |
|
|---|
| 7 |
This email describes decisons by the Steering Commitee's to adjust the |
|---|
| 8 |
release schedule. The primary goal of these changes is to accomodate |
|---|
| 9 |
the schedules of the various GNU/Linux and other free system distributors. |
|---|
| 10 |
These distributors would like to upgrade to a stable compiler whose C++ |
|---|
| 11 |
ABI is less likely to change henceforth. |
|---|
| 12 |
|
|---|
| 13 |
Therefore, as independently suggested on this list, the SC has decided |
|---|
| 14 |
that: |
|---|
| 15 |
|
|---|
| 16 |
1. The 3.1.1 release will proceed as planned. (More on that in my next |
|---|
| 17 |
email.) |
|---|
| 18 |
|
|---|
| 19 |
2. There will be no 3.1.2 release. Instead, there will be a GCC 3.2 |
|---|
| 20 |
release which is GCC 3.1.1 with those C++ ABI fixes present on the |
|---|
| 21 |
mainline. This release will take place shortly after GCC 3.1.1. |
|---|
| 22 |
(It will happen approximately as quickly as I can create branches |
|---|
| 23 |
and Jason can commit the relevant fixes.) |
|---|
| 24 |
|
|---|
| 25 |
3. GCC 3.2.1 (and perhaps GCC 3.2.2) will be released when GCC 3.1.2 |
|---|
| 26 |
(and perhaps GCC 3.1.3) would otherwise have been released. Despite |
|---|
| 27 |
their release numbers, these will be compilers off what we now think |
|---|
| 28 |
of as the GCC 3.1 sourcebase. |
|---|
| 29 |
|
|---|
| 30 |
4. GCC 3.3 will be released when GCC 3.2 was originally scheduled, and |
|---|
| 31 |
will be made from the current mainline. |
|---|
| 32 |
|
|---|
| 33 |
If you're a GCC developer, none of this makes too much difference to |
|---|
| 34 |
you; all the same check-in rules and guidlines are in place. |
|---|
| 35 |
|
|---|
| 36 |
However, if you're a GCC user you should be aware that fixes that GCC |
|---|
| 37 |
3.1.1 be the last release C++ ABI-compatible with GCC 3.1. |
|---|
| 38 |
|
|---|
| 39 |
Finally, if you're a distributor you should be aware that there's no |
|---|
| 40 |
way to be 100% sure that GCC 3.3 will be ABI compatible with GCC 3.2; |
|---|
| 41 |
this special re-jigerring of things only ups the odds that things will |
|---|
| 42 |
remain copmatible. While maintaining the ABI is amongst our most |
|---|
| 43 |
important goals, there are events that could make it necessary to make |
|---|
| 44 |
changes. |
|---|
| 45 |
|
|---|
| 46 |
Your Release Manager, |
|---|
| 47 |
|
|---|
| 48 |
-- |
|---|
| 49 |
Mark Mitchell mark@codesourcery.com |
|---|
| 50 |
CodeSourcery, LLC http://www.codesourcery.com |
|---|
| 51 |
|
|---|
