Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 41918 invoked by uid 500); 25 Feb 2003 15:12:52 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 41837 invoked from network); 25 Feb 2003 15:12:51 -0000 Message-ID: <3E5B87C0.4010808@isu-gmbh.de> Date: Tue, 25 Feb 2003 16:12:00 +0100 From: Christian Geisert Organization: ISU GmbH User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826 X-Accept-Language: de-de, en-us MIME-Version: 1.0 To: general@xml.apache.org Subject: Re: Guidelines for releases References: <3E5B3CE2.30403@ozemail.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Berin Lautenbach wrote: > Peoples, > > The xml-security project has recently grown somewhat in terms of > committers, and the question has come up around putting a process in > place around releases. When, how, pre-requisites, shakedown testing etc. > > Is there anything we can "lift" from the other projects in terms of such > a process, rather than re-inventing the wheel? http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/ReleaseInstructions http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-batik/MAINTAIN And FOP should have something soon too .. Christian --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org