> On 6/9/06, Josh Bressers <bressers@xxxxxxxxxx> wrote:
> > > >
> > > >
> > > > This is true. We're going with seamonkey in RHEL. I think this current
> > > > round of issues is proof as to why this has to happen. Backporting to the
> > > > firefox 1.0 branch is nearly impossible given the drastic changes between
> > > > versions.
> > > >
> > > > Right now we're furiously working on backporting patches for the most
> > > > critical issues. If you want to help mail Chris Aillon (caillon@redhat)
> > > > with your request. He's currently heading up a small group of various
> > > > distributors trying to get all this work done.
> > > >
> > >
> > > You are backporting patches then for the most critical issues for Mozilla
> > > suite 1.7.13 only, Josh? Or also for Firefox-1.0.8?
> >
> > We're working on just the critical issues. The codebase for suite 1.7.13
> > and Firefox 1.0.8 are nearly the same. Patches for one should apply to the
> > other.
> >
>
> Ok this seems more confusing. The RHEL-3 U8 beta is supposed to move
> to seamonkey which is 1.8.x based. It would seem that if were the
> case.. it would be better to move everyone to the 1.8.x base
> (RHEL-4/FC-x).. or maybe I am just not understanding everything that
> is happening.
The plan is to move everything to seamonkey, but there is much testing that
needs to be done. We're not ready yet, which is why we are backporting the
critical patches first.
--
JB
