seamonkey progress III

[Eric Dorland]

* Alexander Sack (asac at jwsdot.com) wrote:
> 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.
> > 
> 
> Sorry to double post on this ... just to remember: the security team
> will *not* be involved: They stated multiple times that we (the
> maintainers) have to take care for security on our own. Instead it
> would be possible for me (or anyone else of us who does major mozilla
> security work) to join security team at some point.

I think they will be much more likely to pitch in if we're on a branch
still receiving active security support, but yes, we're largely on our
own. 

-- 
Eric Dorland <eric at kuroneko.ca>
ICQ: #61138586, Jabber: hooty at jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/attachments/20061006/d0bf1cf3/attachment.pgp