Hola, Should we consider calling this next release launcher 1.1? I ask because Tomcat has been shipping with launcher for a while now (definitely more than a year), so what has been 1.0-dev in CVS is the de-facto 1.0.
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, August 16, 2004 10:17 AM >To: [EMAIL PROTECTED] >Subject: cvs commit: jakarta-commons/launcher/xdocs release-notes-1.0.xml >release-plan.xml downloads.xml > >dirkv 2004/08/16 07:17:21 > > Modified: launcher/xdocs downloads.xml > Added: launcher/xdocs release-notes-1.0.xml release-plan.xml > Log: > prepare for release > > Revision Changes Path > 1.3 +12 -7 jakarta-commons/launcher/xdocs/downloads.xml > > Index: downloads.xml > =================================================================== > RCS file: /home/cvs/jakarta-commons/launcher/xdocs/downloads.xml,v > retrieving revision 1.2 > retrieving revision 1.3 > diff -u -r1.2 -r1.3 > --- downloads.xml 7 Mar 2004 11:05:22 -0000 1.2 > +++ downloads.xml 16 Aug 2004 14:17:21 -0000 1.3 > @@ -28,8 +28,7 @@ > <!-- > <p>The following releases are available:</p> > <ul> > - <li>Version 1.1 - 20 October 2003</li> > - <li>Version 1.0 - 12 August 2002</li> > + <li>Version 1.0 - 20 August 2004</li> > </ul> > <br/> > <p> > @@ -57,20 +56,26 @@ > </p> > </section> > > -<!-- > <section name="Release Candidate"> > <p> > - Release candidates for the upcoming 1.1 release can be >downloaded > + We are currently preparing the 1.0 release following this > + <a href="release-plan.html">release plan</a>. > + </p> > + <p> > + Release candidates for the upcoming 1.0 release can be >downloaded > <a href="http://cvs.apache.org/~dirkv/builds/";>here</a>. > </p> > <p> > + Preliminary <a href="release-notes-1.0.html">release >notes</a> are available. > + </p> > + <p> > Please review and report any problem on the > <a href="mail-lists.html">mailing list</a>. > </p> > <p> > - Final release target is 20 October 2003. > + Final release target is 20 August 2004. > </p> > </section> > ---> > + > </body> > </document> > > > > 1.1 jakarta-commons/launcher/xdocs/release-notes-1.0.xml > > Index: release-notes-1.0.xml > =================================================================== > <?xml version="1.0"?> > <!-- > Copyright 2003-2004 The Apache Software Foundation > > Licensed under the Apache License, Version 2.0 (the "License"); > you may not use this file except in compliance with the License. > You may obtain a copy of the License at > > http://www.apache.org/licenses/LICENSE-2.0 > > Unless required by applicable law or agreed to in writing, software > distributed under the License is distributed on an "AS IS" BASIS, > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or >implied. > See the License for the specific language governing permissions and > limitations under the License. > --> > <document> > <properties> > <title>Release notes for Commons-Launcher 1.0</title> > <author email="[EMAIL PROTECTED]">Commons >Documentation Team</author> > <revision>$Id: release-notes-1.0.xml,v 1.1 2004/08/16 14:17:21 >dirkv Exp $</revision> > </properties> > > <body> > <section name="Release notes for Commons-Launcher 1.0"> > <p> > Launcher was imported into jakarta commons almost 2 years ago (25 okt >2002) but never had a release. > </p> > > <p>The Launcher Component is designed to be a cross platform Java > application launcher.</p> > <p>The original Java classes come from the Jakarta Tomcat 4.0 >project.</p> > > <!-- BEGIN include homepage --> > <p> > Commons-launcher eliminates the need for a batch or shell script to >launch a > Java class. Some situations where elimination of a batch or shell script >may > be desirable are: > <ul> > <li>You want to avoid having to determining where certain application >paths > are e.g. your application's home directory, etc. Determining this > dynamically in a Windows batch scripts is very tricky on some versions >of > Windows or when softlinks are used on Unix platforms.</li> > <li>You want to avoid having to handle native file and path separators >or > native path quoting issues.</li> > <li>You need to enforce certain system properties e.g. > <code>java.endorsed.dirs</code> when running with JDK 1.4.</li> > <li>You want to allow users to pass in custom JVM arguments or system > properties without having to parse and reorder arguments in your >script. > This can be tricky and/or messy in batch and shell scripts.</li> > <li>You want to bootstrap system properties from a configuration file >instead > hard-coding them in your batch and shell scripts.</li> > <li>You want to provide localized error messages which is very tricky >to do > in batch and shell scripts.</li> > </ul> > </p> > <!-- END include --> > > <p> > For more information consult the > <a href="http://jakarta.apache.org/commons/launcher/";>Commons-Launcher >website</a>. > </p> > </section> > </body> > </document> > > > > > 1.1 jakarta-commons/launcher/xdocs/release-plan.xml > > Index: release-plan.xml > =================================================================== > <?xml version="1.0"?> > <!-- > Copyright 2003-2004 The Apache Software Foundation > > Licensed under the Apache License, Version 2.0 (the "License"); > you may not use this file except in compliance with the License. > You may obtain a copy of the License at > > http://www.apache.org/licenses/LICENSE-2.0 > > Unless required by applicable law or agreed to in writing, software > distributed under the License is distributed on an "AS IS" BASIS, > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or >implied. > See the License for the specific language governing permissions and > limitations under the License. > --> > <document> > <properties> > <title>Release Plan</title> > <author email="[EMAIL PROTECTED]">Commons >Documentation Team</author> > <revision>$Id: release-plan.xml,v 1.1 2004/08/16 14:17:21 dirkv >Exp $</revision> > </properties> > <body> > <section name="Release Plan for Launcher 1.0"> > <subsection name="Administrivia"> > <p> > This document describes a plan for a 1.0 release of the > Jakarta-Commons Launcher component (for the remainder > of this document, simply "Launcher"). Per the > <a href="http://jakarta.apache.org/site/decisions.html";> > Jakarta/ASF guidelines</a>, this > document doesn't mean anything until accepted by the > relevant committer community via a lazy majority vote > (hereafter, simply "lazy majority"). Once accepted, it may > be replaced by an alternative plan, again subject to lazy > majority approval. > </p> > <p> > Non-binding votes (votes cast by those outside the relevant > committer community) are welcome, but only binding votes > are significant for decision making purposes. > </p> > </subsection> > > <subsection name="Objective"> > <p>The objective of the 1.0 release of Launcher is to > provide a stable and robust release with the intention of > providing a stable foundation for the further evolution of > the Launcher component.</p> > </subsection> > > <subsection name="Release Manager"> > <p><ul><li>Dirk Verbeeck</li></ul></p> > </subsection> > > <subsection name="Release Process"> > <p>The <a href="http://jakarta.apache.org/commons/releases/index.html";> > Jakarta Commons release process</a> will be followed.</p> > </subsection> > > <subsection name="Timeline:"> > <p> > (All days ending at 23:59:59 GMT in case of dispute.) > <ul> > <li><b>Preparation Period</b>: > 11 March 2004 - 27 July 2004 > <br/> > During this period, all issues preventing building a > release candidate should be a addressed. All other > updates (documentation and website) are not blocking. > </li> > <br/> > <li><b>Review Period</b>: > 27 July 2004 - 16 August 2004 > <br/> > During the Review Period specific design, functional and > contract changes to Launcher will be considered on the > Jakarta-Commons mailing list, using the following > process: > <ol> > <li>Any developer or committer that would like to see > a specific change (or group of changes) enacted or > rolled back will suggest it on the Jakarta-Commons > mailing list ([EMAIL PROTECTED]). > </li> > <li>Any interested committer that opposes a given change > (or group of changes) is obligated to indicate this > disapproval on the list during the Review Period. > </li> > <li>We will seek, but not strictly require consensus on > each decision point. If consensus cannot be reached, > any committer may call for a vote to resolve the > issue via a lazy majority vote. > </li> > </ol> > The Review Period may be extended by one week (at a time) > given lazy majority approval, in case issues still need > to be resolved. > <br/><br/> > To facilitate the review process Release Candidates > (RC1, RC2, ...) will be provided at the start of the > review period and when mayor issues are resolved. > </li> > <br/> > <li><b>Implementation Period</b>: > 16 August 2004 - 20 August 2004 > <br/> > (assuming the Review Period is not extended) > <br/><br/> > During this period, any remaining implementation, testing > and documentation will be completed. No new features > or "public" interface changes will be considered > in-scope at this time (short of a lazy-majority > approved revised release plan or any "showstopper" > defects). > <br/><br/> > At the end of the Implementation Period, a formal > release vote will be called, subject to lazy > approval. > <br/><br/> > A formal release vote may be called before the end > of the implementation period, but after the end of > the Review Period, if appropriate. > (As soon as all remaining issues are resolved) > </li> > <br/> > <li><b>Release</b>: > 20 August 2004 > </li> > </ul> > </p> > </subsection> > </section> > </body> > </document> > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
