Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 64518 invoked from network); 22 Feb 2005 05:16:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Feb 2005 05:16:06 -0000 Received: (qmail 17571 invoked by uid 500); 22 Feb 2005 05:16:04 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 17535 invoked by uid 500); 22 Feb 2005 05:16:04 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 17520 invoked by uid 99); 22 Feb 2005 05:16:04 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.tsd.biz (HELO Lavoie.tsdinc.steitz.com) (209.249.229.5) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 21 Feb 2005 21:16:03 -0800 Received: from [192.168.1.186] ([130.13.32.219]) by Lavoie.tsdinc.steitz.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 22 Feb 2005 00:15:50 -0500 Message-ID: <421AA3E8.3090506@steitz.com> Date: Mon, 21 Feb 2005 22:15:52 -0500 From: Phil Steitz User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [feedparser] Release HOWTO? References: <421A9378.7000907@newsmonster.org> In-Reply-To: <421A9378.7000907@newsmonster.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Feb 2005 05:15:51.0101 (UTC) FILETIME=[935A06D0:01C5189D] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Kevin A. Burton wrote: > I'm pending on doing a first beta release of FeedParser here shortly. > > Is there a document anywhere describing current release procedures This is a little out of date, but a good place to start: http://jakarta.apache.org/commons/releases/index.html > including: > > - Release Candidate scheduling Different commons components have done different things here. The most common approach is to follow the RC -> VOTE -> Release path described in http://jakarta.apache.org/commons/releases/prepare.html, but the only thing absolutely required is that nothing is publicly released without a VOTE and notification of the Jakarta PMC. > - Nighly build setup If you have a working ant build.xml, all you need to do is post a request here (commons-dev list) to get added to the nightly build runs. > - Gump integration Not part of the release process per se and not a required prerequisite for a release. I don't know of any commons gump how-to. IIRC all apache committers have karma for the gump repo and you can get added by just adding a descriptor. > - Archive setup Don't know exactly what you mean here. If you mean what needs to go in the source and binary release tars, the minimum requirements are described in http://jakarta.apache.org/commons/releases/index.html hth, Phil --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org