Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 75238 invoked from network); 2 Sep 2003 03:05:43 -0000 Received: from unknown (HELO ms-smtp-01.southeast.rr.com) (24.93.67.82) by daedalus.apache.org with SMTP; 2 Sep 2003 03:05:43 -0000 Received: from noel770 (cae88-16-024.sc.rr.com [24.88.16.24]) by ms-smtp-01.southeast.rr.com (8.12.5/8.12.2) with SMTP id h822wj4P028733 for ; Mon, 1 Sep 2003 22:58:46 -0400 (EDT) From: "Noel J. Bergman" To: "Jakarta Commons Developers List" Subject: RE: [doc] how to release - feedback Date: Mon, 1 Sep 2003 23:05:34 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Henri Yandell wrote: > On Mon, 1 Sep 2003, Noel J. Bergman wrote: > > See: http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases > The Jakarta Commons release docs need to link to this doc. Or at least > include the 'how to create a key' section. Very useful at getting me > started on gpg quickly. Welcome. > One problem I have with all the release information is that it is all over > the place, and is not linked to a timeline. I need to wait for 24 hours at > some point for mirrors to catch up, but am unsure exactly where that fits. Now you seem to contradict yourself. You just suggested possibly "including" the section because it was helpful, but now you are complaining about the material being all over the place. I agree with the latter complaint. It is definitely one of my pet peeves. My view is "Linking good. Replication bad." Replicating this information all over the ASF sites, makes it harder to maintain, and results in disparate copies of things. For example, we have the general signing page, which dates back to sometime last year. But then just a week ago, another page with similar information http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonReleaseManagerHowto/Signi ngReleases) was created. Personally, I think that the Avalon Release Manager page is good, but it should have linked to the common page on signing, where he could always have contributed elaborated information rather than creating an ad hoc page. This sort of thing led me to start a Wiki page just for the purpose of tracking this sort of redundant content (http://nagoya.apache.org/wiki/apachewiki.cgi?PoliciesAndProcedures). If you find additional pages, please do update the preceeding so that we can locate all of that stuff. As for your question, as far as I know, you do a release as normal. Many mirrors don't take that long to synchronize, anyway. If you were to delay anything, it seems to me that you could delay announcing the release. I see from another message that you came to the same conclusion. --- Noel