From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: gcc@gcc.gnu.org Subject: gcc-2.95.2 rough plan Date: Tue, 07 Sep 1999 01:10:00 -0000 Message-id: <23106.936691715@upchuck.cygnus.com> X-SW-Source: 1999-09/msg00213.html Just to let folks know what the rough plan is for gcc-2.95.2. I would like to have gcc-2.95.2 hit the streets somewhere between Oct 1 and Oct 15. The plan (like all our minor releases) is to just fix serious bugs that have simple and safe bugfixes. It is very important that the proposed fixes be kept simple. Testing before a minor release is limited; therefore, we only want to install fixes that we know to be very safe. Maintainers are free to check in changes to the gcc-2.95 branch in areas of the compiler they maintain within the guidelines noted above. I do ask that anyone checking in changes to the gcc-2.95 branch send me a very short (1-2 line) description of the problem that is solved by the change (for the release notes). Comments and suggestions are always encouraged! Thanks, jeff From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: gcc@gcc.gnu.org Subject: gcc-2.95.2 rough plan Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <23106.936691715@upchuck.cygnus.com> X-SW-Source: 1999-09n/msg00213.html Message-ID: <19990930180200.tdScFMl3euLLzDRBklIlnc5FKLrgMUd-kJDsP2JQ1lU@z> Just to let folks know what the rough plan is for gcc-2.95.2. I would like to have gcc-2.95.2 hit the streets somewhere between Oct 1 and Oct 15. The plan (like all our minor releases) is to just fix serious bugs that have simple and safe bugfixes. It is very important that the proposed fixes be kept simple. Testing before a minor release is limited; therefore, we only want to install fixes that we know to be very safe. Maintainers are free to check in changes to the gcc-2.95 branch in areas of the compiler they maintain within the guidelines noted above. I do ask that anyone checking in changes to the gcc-2.95 branch send me a very short (1-2 line) description of the problem that is solved by the change (for the release notes). Comments and suggestions are always encouraged! Thanks, jeff