morgand 01/05/09 13:52:02
Modified: . HOWTO-RELEASE
Log:
added info on the sandbox repository, as well as details on how to update
the news section
Revision Changes Path
1.6 +52 -3 jakarta-taglibs/HOWTO-RELEASE
Index: HOWTO-RELEASE
===================================================================
RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- HOWTO-RELEASE 2001/05/03 15:33:58 1.5
+++ HOWTO-RELEASE 2001/05/09 20:51:58 1.6
@@ -1,6 +1,39 @@
HOWTO-RELEASE
-------------
+TABLE OF CONTENTS
+-----------------
+
+1 RELEASE TYPES
+1.1 "MAJOR" RELEASE
+1.2 "MINOR" RELEASE
+1.3 "BUG FIX" RELEASE
+1.4 "BETA" RELEASES
+
+2 RELEASE NUMBERS
+2.1 INITIAL RELEASE NUMBER
+2.2 DISCECTING THE RELEASE NUMBER
+2.3 "BETA" RELEASE NUMBERS
+
+3 STARTING/COMPLETING MAJOR RELEASES
+
+4 DEVELOPMENT STATES
+4.1 "IN DEVELOPMENT" STATE
+4.2 "BETA" STATE
+4.3 "RELEASED" STATE
+4.4 "UNSUPPORTED" STATE
+
+5 NEWS
+5.1 UPDATING THE NEWS
+
+6 CVS REPOSITORIES
+6.1 MAIN REPOSITORY
+6.2 SANDBOX REPOSITORY
+
+
+CONTENTS
+--------
+
1 RELEASE TYPES
There are four types of releases: "Major", "Minor", "Bug Fix", and "Beta". See
also Section 2, which describes how releases are numbered.
@@ -49,7 +82,7 @@
The next release of this tag library would increment the appropriate part of the
release number, depending on the type of release (major, minor, or bug fix). For
example, a subsequent minor release would be version 2.1, or a subsequent major
release would be 3.0.
-2.5 "BETA" RELEASE NUMBERS
+2.3 "BETA" RELEASE NUMBERS
Beta releases are denoted by adding the phrase "beta<beta version number>" after
the release number in the released archive. For example, if the current release
version is 2.0.4, and the developer wished to preview the next major release, the jar
would be named foo-3.0-beta1.jar.
@@ -69,7 +102,7 @@
The version 3 release is the main trunk of the CVS tree. However, versions 2 and 1
will still be available on other branches (rel2 and rel1), if other releases of that
version prove necessary.
-4 DEVELOPMENT STATE
+4 DEVELOPMENT STATES
Each tag library also has its development state listed on the main website. There
are four possible states: "in development", "beta", "released", and "unsupported".
@@ -92,5 +125,21 @@
Under rare circumstances, the Taglibs committers may vote to make a tag library
"unsupported", if there are no resources to maintain the library or if it has been
completely supplanted by a superior tag library. Only "released" tags may become
"unsupported"; tags in other states will simply be terminated after a brief warning
period.
5 NEWS
+
+There is a "news" section of the Jakarta taglibs site. This portion of the site
provides a notification of each major, minor or bug fix release of each tag library.
Each release notification will link to the "news" section for that tag library, which
will contain the details of what new features were introduced, which bugs were fixed,
etc.
+
+5.1 UPDATING THE NEWS
+
+The news sections for each tag library are automatically updated by the nightly
builds. The home page, however, must be updated manually. Build the HTML from the
XML files in the src directory and scp them to the /www/jakarta.apache.org/taglibs/
directory on the Jakarta server.
+
+6 CVS REPOSITORIES
+
+6.1 MAIN REPOSITORY
+
+The main repository for Jakarta taglibs is located in the jakarta-taglibs module.
Refer to the Jakarta site documentation for how to access a Jakarta CVS repository.
The main repository contains approved tag libraries that are being developed by the
Taglibs project committers.
+
+6.2 SANDBOX REPOSITORY
+
+Jakarta taglibs also has a "sandbox" repository located int the
jakarta-taglibs-sandbox module. The sandbox is intended to be a place for
experimenting with new tags or submitting tentative tag library proposals. Jakarta
committers from any project may request access to the sandbox in order to submit their
ideas. If a tag library in the sandbox recieves a majority vote from the Taglibs
committers, it is moved into the main repository, and the committers for that tag
library will often be granted committer status to the main repository as well.
-There will be a "news" section of the Jakarta taglibs site. This portion of the
site will provide a notification of each major, minor or bug fix release of each tag
library. Each release notification will link to the "news" section for that tag
library, which will contain the details of what new features were introduced, which
bugs were fixed, etc.
\ No newline at end of file
+Users may download and use tag libraries in the sandbox, but those libraries are
presented AS IS with no guarantees for stability or longevity.
\ No newline at end of file
