Re: How to coordinate web team for security releases?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



- --On Tuesday, February 06, 2007 14:24:00 +0000 Dave Page
<dpage@postgresql.org> 
wrote:

> Marc G. Fournier wrote:
>>
>>
>> --On Tuesday, February 06, 2007 14:02:23 +0000 Dave Page
>> <dpage@postgresql.org>
>> wrote:
>>
>>> Marc G. Fournier wrote:
>>>> 'k, set ... you will want to test it though ...
>>>>
>>>> current 'taboo' strings are:
>>>>
>>>> /^Security: /
>>> Please lose that one - the pgAdmin list is used for general discussion
>>> and that string doesn't seem unreasonable to be included in an email.
>>
>> Discuss it with Tom ... he's the one that requested that one ...
>>
>> Wait, you missed something in the thread here (or, I didn't emphasize it
>> enough) .. this is *only* on the committers list, none of the other ones ...
>> its only meant to trap commit messages pertaining to a security release, not
>> security related discussions ... is that why you did that 'long string'
>> below?  Cause you thought it was on all lists? :)
>>
>> Sorry, I should have been more clear ...
>
> No *you* missed something :-) The pgAdmin SVN commit messages go to
> pgadmin-hackers@postgresql.org - my request was that you add the long
> string to /that/ list.

Yup, I missed that, sorry ... okay, changed ... try that now, s hould work a 
wee bit better :)

>
> Regards, Dave.



- ----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org                              MSN . scrappy@hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFyJ0U4QvfyHIvDvMRAhQ/AJ4tL/En/EPKE3mpYXXgE5VHeHAx1gCfcqv8
VYj7OLobteyqMpa6tj8XQ/k=
=Do7Y
-----END PGP SIGNATURE-----