seamonkey progress III

[Alexander Sack]

On Fri, Oct 06, 2006 at 08:14:25PM +0200, Mike Hommey wrote:
> 
> 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 would be more than happy if anyone seriously wants to help
... anyway eric opted-out (as he does not want to look at undisclosed
bugs) and iirc you pointed out that you don't have time.

I can always add you CC on sensitive bugs if you want to help. I
worked that way quite some time ... then if you did a good bunch of
backporting we can ask to add you to security list too. 

... and you are right  support for 1.5.0.x will be lot of easier
to backport from the 1.8.1 branch. Thats why I am pretty confident
(and they indicated in chat that they would) that other vendors will
join us too.


 - Alexander

-- 
 GPG messages preferred.   |  .''`.  ** Debian GNU/Linux **
 Alexander Sack            | : :' :      The  universal
 asac at jwsdot.com           | `. `'      Operating System
 http://www.asoftsite.org  |   `-    http://www.debian.org