This is the mail archive of the
mailing list for the GCC project.
Re: [RFC][wwwdocs] Mention PR21173 in the news
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Gabriel Dos Reis <gdr at cs dot tamu dot edu>
- Cc: Steven Bosscher <stevenb at suse dot de>, gcc-patches at gcc dot gnu dot org, Gerald Pfeifer <gerald at pfeifer dot com>, Joe dot Buck at synopsys dot COM
- Date: Thu, 26 May 2005 09:20:56 -0700
- Subject: Re: [RFC][wwwdocs] Mention PR21173 in the news
- References: <firstname.lastname@example.org> <email@example.com>
Gabriel Dos Reis wrote:
Steven Bosscher <firstname.lastname@example.org> writes:
| So this patch adds a friendly note on the home page, with a link to the
| bug. Comments?
I'm very supportive of the idea. However, can we put a more
descriptive information about the symptoms of that bug?
I'm not very supportive of putting this on our front page. I think
putting it on the 4.0 page itself would make sense to me. It's
definitely worth warning people about frequently reported bugs, but I
don't think that even a serious, oft-reported bug, rises to the level of
I'd appreciate it people would not get too excited about these issues,
as just replying to lots of email takes up lots of my time. Every .0
release (3.3.0, 3.4.0, etc.) has had serious bugs, and this is 4.0.0.
Maybe this is more serious, maybe it's not. But, the world's not coming
to an end. There's real overhead in doing a release, not just for me,
but for everyone. Rushing out releases without adequate forethought is
not what I want to do.
However, I'm working actively on 4.0.1 planning, now that 3.4.4 is done,
and expect to have something to say soon; within a few days at most.
I've been reviewing the outstanding PRs, and thinking about what to do.
I think it's clear that we want to get a release done soon, but we
also want to make sure that we don't have a release that has some new
bad problem, resulting in churn. Please stay tuned.