Thanks Felix. Agree. With the Aries versioning policy, it reduces the chance to bump versions too much.
One question on the Aries version policy: In the versioning policy, http://aries.apache.org/development/versionpolicy.html , it states "*The version should relate to the most recent release of the package and not to the version found in trunk.*" It will be good to have the release version as an comment in the package.info (or an automatically generated package version map per release) so that the developers can immediately decide whether the package version needs to be updated. At the moment, developers have to look at the change histories and this process requires the knowledge of the last release date, which does not show in the change history. Thoughts? -- Thanks Emily ================= Emily Jiang [email protected]
