seamonkey progress III

[Mike Hommey]

On Fri, Oct 06, 2006 at 08:04:02PM +0200, Alexander Sack <asac at jwsdot.com> wrote:
> On Fri, Oct 06, 2006 at 06:53:03PM +0200, Mike Hommey wrote:
> > On Fri, Oct 06, 2006 at 04:53:39PM +0200, Alexander Sack <asac at jwsdot.com> wrote:
> > > On Fri, Oct 06, 2006 at 04:41:20PM +0200, Mike Hommey wrote:
> > > > On Fri, Oct 06, 2006 at 03:32:31PM +0200, Alexander Sack <asac at debian.org> wrote:
> > > > > > That's about it!
> > > > > > One last thing: which version should go into Etch? 1.0.5 or 1.1 ? And
> > > > > > who to ask about this?
> > > > > >
> > > > > 
> > > > > I can't tell ... I don't think final 1.8.1 branch versions will be out
> > > > > in time for the freeze ... so probably we should go the safe way and
> > > > > use the 1.8.0 branch versions (aka 1.0.5 for your case).
> > > > 
> > > > See the thread starting at
> > > > http://lists.debian.org/debian-release/2006/09/msg00300.html
> > > > As far as the new branch packages are tested, we can expect exceptions to
> > > > push them into etch, which should be better for everyone.
> > > 
> > > Mike, unless you want to help supporting security on the long run and
> > > have time to do so and assuming thunderbird 2.0 won't make it, I
> > > cannot provide security for two branches ... really. Please lets use
> > > the same branch for everything.
> > 
> > Damn, when is thunderbird 2.0 due, again ?
> 
> Dunno ... I just red your post to debian-release. There you said "End
> of Nov".

The problem with the current branch is that it won't be supported by
upstream from roughly 6 months after etch release... on the long term,
it might be better to have upstream support for security...

The other problem is that now you're basically alone for security
support, I don't think it's a sane situation. It'd be much better if
several of us (and some from the security team as well) could be
involved in the process with upstream.

Another thing to consider is that the new branch is not 1.9, which means
the differences are not huge in the codebase, the patches that apply to
1.8.1 (that upstream will have provided directly, since it will be
supported) won't be very difficult to port, I think.

I just hope the recent trademark "fun" won't refrain them to help us...

Mike