> > Despite the fact that virtually all of the bugs open against 4.2.0 are > > also open against 4.1 or 4.3 -- or both! -- there seems to be little > > interest in fixing them. > > > > Some have suggested that I try to solve this by closing GCC 4.3 > > development until 4.2.0 is done. > > So here's a second possibility: delete the 4.2 branch, and start again with > a fresh release branch. Call it 4.2 again, although it would be more-or-less > what we're expecting to be 4.3. Maybe it would be not just simplest but also > most effective to cut our losses and try again.
This is a really bad idea. 4.3 is months from being ready to release and there's only a handful of P1 PRs blocking 4.2 from release. From my perspective, 4.2 is better than 4.1 in many ways. As a port maintainer, I have spent a large amount of time trying to ensure that 4.2 is ready. I'd be quite upset if this effort was for naught. If 4.2 has deficiencies that need addressing prior to release, then the specific technical aspects need to be discussed. A general suggestion that the branch be deleted isn't acceptable as the same mistakes will be made all over again. Dave -- J. David Anglin [EMAIL PROTECTED] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
