Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44A50B61.5030600@rowe-clan.net>
Date: Fri, 30 Jun 2006 12:30:41 +0100
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
User-Agent: Thunderbird 1.5.0.4 (X11/20060614)
MIME-Version: 1.0
To: david reid <david@jetnet.co.uk>
CC: Justin Erenkrantz <justin@erenkrantz.com>,  colm@stdlib.net,
 dev@apr.apache.org, Cliff Schmidt <cliffschmidt@gmail.com>
Subject: Re: Proposed Crypto Notification process
References: <44A4C4EC.7080101@rowe-clan.net>
	 <20060630081212.GA7308@dochas.stdlib.net>
 <5c902b9e0606300409p1457b3e3w124bfa89aaa39c2e@mail.gmail.com>
 <44A50774.4020909@jetnet.co.uk>
In-Reply-To: <44A50774.4020909@jetnet.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

david reid wrote:
> Actually, I think we should look at going a step further and have the 
> email sent automatically as well. When a project creates/updates a file 
> it can trigger a script to handle the email creation/submission - which 
> would be a win/win for everyone and hopefully make the projects lives a 
> bit easier as well. I really don't see the point of doing it other ways...

Overkill - they would go balistic from the flood.

The only time we might renotify would be new crypto ALGORITHM e.g. double
the bits somewhere.  It's only a change to the product, not a change to the
version number or your source code or whatever.

When we move from svn.apache.org to svn2.apache.org, that won't even need
a renotification because it's all by-reference.  Only moving from the
apr.apache.org/crypto.html absolute authority document would trigger one.

Bill