On Sat, Nov 24, 2012 at 7:50 PM, Reto Bachmann-Gmür <[email protected]> wrote: > Ok, thanks. Good to have such a policy. > > Just the last point: > >> - A change in the behaviour (documented behaviour/undocumented side >> effect) >> >> 3.4.1 -> 3.4.2 >> > > The version in trunk is a snapshot version (3.4.1-SNAPSHOT) so the latest > released version is probably 3.4 so this change would only change what > changed already.
3.4.2-SNAPSHOT is automatically created as soon as 3.4.1 is released. However as long there are no changes in the trunk there will not be a 3.4.2 release. Practically that means that a minor change in the trunk does not increase the version. But out of a release perspective the first change in the trunk does increase the version (as it triggers a new release) and all further changes do not unless one decides (for some other reason) to increase the version number. BTW: With the introduction of ManagedSites in the Entityhub I had to made some incompatible version changes. Back than I decided to increase the version number of the trunk trom 0.10.1 to 0.11. I also created an entityhub-0.10 branch [1] so that we could do 0.10.* releases if we wanted to fix bugs in the version with the old API. This was mainly because the entityhub 0.11.* is no longer compatible with the release stanbol version 0.9.0. But as Fabian already noted. We need really to do some more releases to see how this all works out in practice. The current discussions are all very theoretically and need to be validated by forging real releases. best Rupert [1] http://svn.apache.org/repos/asf/stanbol/branches/entityhub-0.10/ > > Reto -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
