Date:	Wed, 18 Jul 2001 22:18:30 -0400
Message-Id:	<200107190218.WAA30409@greed.delorie.com>
From:	DJ Delorie <dj AT redhat DOT com>
To:	djgpp-workers AT delorie DOT com
Subject:	[mark AT codesourcery DOT com: GCC 3.0.1 Status Report]
Reply-To:	djgpp-workers AT delorie DOT com

Time to get those last-minute patches in ;-)

------- Start of forwarded message -------
From: Mark Mitchell <mark AT codesourcery DOT com>
Newsgroups: cygnus.egcs
Subject: GCC 3.0.1 Status Report
Date: Wed, 18 Jul 2001 18:21:17 -0700
Organization: None provided
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Trace: cronkite.cygnus.com 995506915 26682 205.180.83.71 (19 Jul 2001 01:41:55 GMT)
X-Complaints-To: postmaster AT cygnus DOT com
NNTP-Posting-Date: 19 Jul 2001 01:41:55 GMT
To: gcc AT gcc DOT gnu DOT org
Mailing-List: contact gcc-help AT gcc DOT gnu DOT org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:gcc-unsubscribe-##L=##H AT gcc DOT gnu DOT org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc AT gcc DOT gnu DOT org>
List-Help: <http://gcc.gnu.org/ml/>
Content-Disposition: inline
DJ-Gateway: from mailing list gcc AT gcc DOT gnu DOT org
Xref: cygnus.com cygnus.egcs:51939

We are nearing the pre-3.0.1 freeze.

In particular, after midnight GMT - 0800 on July 21st, non-documentation 
check-ins on the branch will require my approval.  I will make a release
candidate at that time, for the planned August 1st release.

If things don't make it into this bug-fix release, they can always go
into GCC 3.0.2, due in October.

However, if there are regressions on the 3.0 branch, relative to GCC
3.0, then we should know about them.  If you are aware of such
issues, make sure they are in GNATS, and make me aware by emailing
me directly, including the PR numbers.

I know we have already made some pretty significant bug-fixes, so I'm 
confident that the 3.0.1 release will be useful to current 3.0 users.
It would be nice to address some of the lingering issues relative to
GCC 2.95 that are preventing people from upgrading.

If you are working on fixes that you would like to see in GCC 3.0.1,
now is the time to finish them up.  This is partly a reminder to myself; 
I've been working on the new C++ parser, and that's meant I haven't fixed 
some bugs in GNATS that I should get going on right away.

- -- 
Mark Mitchell                mark AT codesourcery DOT com
CodeSourcery, LLC            http://www.codesourcery.com
------- End of forwarded message -------

- Raw text -