This page (revision-11) was last changed on 29-Mar-2020 17:09 by Juan Pablo 

This page was created on 24-Jan-2015 17:47 by Juan Pablo

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Version Date Modified Size Author Changes ... Change note
11 29-Mar-2020 17:09 3 KB Juan Pablo to previous Clarify versioning proposal as discussed on ML
10 29-Mar-2020 14:38 3 KB Juan Pablo to previous | to last Clarify versioning proposal as discussed on ML
9 22-Mar-2019 23:10 2 KB Juan Pablo to previous | to last add ACLs
8 23-Feb-2019 14:04 2 KB Juan Pablo to previous | to last add release train section
7 23-Feb-2019 14:03 2 KB Juan Pablo to previous | to last add release train section
6 30-Jan-2019 19:49 2 KB Juan Pablo to previous | to last
5 28-Jan-2019 21:41 2 KB Juan Pablo to previous | to last
4 28-Jan-2019 21:41 2 KB Juan Pablo to previous | to last
3 25-Dec-2018 20:53 2 KB Juan Pablo to previous | to last add "Milestone releases" section from NewIn2.11
2 25-Dec-2018 11:07 1 KB Juan Pablo to previous | to last svn -> git
1 24-Jan-2015 17:47 1 KB Juan Pablo to last content adapted from http://www.ecyrd.com/JSPWiki/wiki/VersioningProposal
Incoming links Outgoing links
VersioningProposal
VersioningProposal

Difference between version and

At line 21 added 8 lines
!! Milestone releases
As noted above, a minor release upgrade from (say) {{2.10.0}} to {{2.10.3}} ought to be be transparent. However, a major release upgrade from (say) {{2.10.3}} to {{2.11.0}} is very likely to break compatibility with the earlier release. This might be something like requiring a higher release of java to compile or execute the code. You should always refer to the appropriate "NewIn" page in this wiki to familiarise yourself with the change as part of planning for an upgrade to a new major release.
That said, while a new major release is under development, it might prove appropriate to break compatibility in some way, without releasing a new major version. In such a case, this new milestone (intermediate) release will be given an {{M#}} identification such as {{2.10.0.M1}}.
{{M#}} releases are as production-ready as any other JSPWiki release, so the label does not mean the release is incomplete, or only for the brave, or in beta, or something along those lines. Often an {{M#}} release will change an internal API, which will affect associated code such as plugins, or it might alter some configuration parameters. You should check the "NewIn" page before upgrading to an {{M#}} release, but not be concerned about its stability.
This page (revision-11) was last changed on 29-Mar-2020 17:09 by Juan Pablo  Top