Richard Guenther writes: > On 9/9/06, Mark Mitchell <[EMAIL PROTECTED]> wrote: > > Kenny Simpson wrote: > > > What is the status of the 4.1 branch? Any word on 4.1.2? > > > > My current plan is to do a 4.1.2 along with 4.2.0. My concern has been > > that with 4.2.0 moving slowly, trying to organize another release might > > just distract the developer community. > > > > However, I realize that's a pretty wide gap between 4.1.1 and 4.1.2. We > > could also do 4.1.2 sooner, and then do 4.1.3 along with 4.2.0. (I want > > to do a 4.1.x release along with 4.2.0 so as to avoid the problems we > > have in past with quality "going backwards" between releases from > > different branches.) > > > > I'm sure that, a priori, people would prefer a 4.1.2 release, but it > > does take effort. On the other hand, many 4.1 bugs are also in 4.2. > > > > Any thoughts? > > With my vendor hat on I'd prefer a 4.1.2 release sooner than I expect > 4.2.0 - which would make the time we branch for 4.2.0 a good candidate. > >From a pure GCC development side I do not care very much about > 4.1.2 (or even 4.0.4 which I don't expect at all). > > I guess a release of 4.1.2 together with branching for 4.2.0 might encourage > to backport regression fixes from 4.2 to 4.1, as with stage1 starting, 4.1.2 > will get even less attention than 4.2.0.
+1 for a 4.1.2 release when/after the 4.2.0 branch is created. I'll propose this release to the Debian release managers to be included into the upcoming Debian 4.0 release. Matthias
