You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/09/09 01:01:44 UTC

[jira] Updated: (TAPESTRY-2189) Document the Tapestry release numbering system

     [ https://issues.apache.org/jira/browse/TAPESTRY-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2189:
-------------------------------------------

    Fix Version/s: 5.1

For, for 5.1, we should start numbering as 5.1.0.0.  The follow on to 5.1 may be 5.1.1, not 5.2.

> Document the Tapestry release numbering system
> ----------------------------------------------
>
>                 Key: TAPESTRY-2189
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2189
>             Project: Tapestry
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 5.0.10
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.1
>
>
> This was discussed in the list.
> The consensus was a numbering scheme of 5.MAJOR.MINOR.PATCH.
> PATCH changes are non-API changes (just internals and implementations).
> MINOR changes are represent additions of new APIs.
> MAJOR changes represent changing or removing existing APIs.
> "5" is for Tapestry 5, we don't want this to change.
> Also, even/odd numbering.  Even releases (5.0, 5.2, 5.4) are stable.  Odd release (5.1, 5.3, 5.5) are unstable.  When an odd release becomes stable the number is rolled forward one to an even number.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org