Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 95685 invoked by uid 500); 17 Apr 2001 14:25:08 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 95474 invoked from network); 17 Apr 2001 14:25:04 -0000 Date: Tue, 17 Apr 2001 07:26:42 -0700 (PDT) From: X-Sender: To: Subject: Re: Tagging 2.0.17 in a few... In-Reply-To: <20010416230006.V31832@lyra.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > 2) You can't roll the tarball and sign it with a key that isn't in the > > KEYS file before you tag. You can also move the tag on that file after > > you commit the changes. I also believe you should have somebody sign your > > key before you use it. > > The KEYS file does not need to go into the distribution. Heck, I'd suggest > that it specifically *NOT* go into the distro. > > Assuming no KEYS file in the distro, then step (2) can be ignored. > > A KEYS file on the public site (whichever of the bazillion redundant copies) > needs a key, tho. I seriously disagree. I thought a lot about this before I posted, because I was trying to figure out why the site said you needed the KEYS file to be up-to-date before the tag. The reason is simple. If I just downloaded the 2.0.17 tarball, and I want to get the KEYS file, I am going to go to CVS, and grab the one with the 2.0.17 tag. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------