Looks good but I would use terminology Micro instead of Point as that is the
terminology used in JDK Package/Extension versioning.
I would also specify that "in development" == alpha and you could have
releases such as 1.0a1
On Fri, 31 Aug 2001 04:42, Rodney Waldhoff wrote:
> Since the number of commons components and users is steadily growing, and
> since several components are approaching their second (or more) release, it
> seems appropriate to consider the way in which we release new versions of
> components and how we label those releases.
>
> I have put together a draft document (adapted from the HOWTO-RELEASE
> document in Jakarta-Taglibs, which has been brought up on this list a
> couple of times) which provides a language for describing the kinds of
> incompatibilities a new release might introduce, and a protocol (that is, a
> version numbering system) that helps to communicate those incompatibilities
> to clients and developers.
>
> The document can be found at:
>
> http://cvs.apache.org/viewcvs/~checkout~/jakarta-commons/VERSIONING-GUIDELI
>NES.txt?content-type=text/plain
>
> If you are interested, please take a look. Your feedback is more than
> welcome. (As mentioned in the document itself, I am specifically not
> calling for this to become commons "standard" at this time.)
>
> - Rod
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
--
Cheers,
Pete
*----------------------------------------------*
| The best defense against logic is ignorance. |
*----------------------------------------------*
