You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by zo...@apache.org on 2011/04/18 17:38:55 UTC
svn commit: r788478 - in /websites/production/aries: ./
content/development/versionpolicy.html
Author: zoe
Date: Mon Apr 18 15:38:54 2011
New Revision: 788478
Log:
Clarify version policy
Modified:
websites/production/aries/ (props changed)
websites/production/aries/content/development/versionpolicy.html
Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Mon Apr 18 15:38:54 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-788475
+/websites/staging/aries/trunk:782169-788477
Modified: websites/production/aries/content/development/versionpolicy.html
==============================================================================
--- websites/production/aries/content/development/versionpolicy.html (original)
+++ websites/production/aries/content/development/versionpolicy.html Mon Apr 18 15:38:54 2011
@@ -274,6 +274,7 @@ would be the provider policy (==,=+).
The policy can be set by using the Maven property <aries.osgi.version.policy>, see the default-parent
pom for an example.</p>
<h2 id="bundle_versions">Bundle versions</h2>
+<p><strong>Note: Bundle versions are changed at release time and only by the release manager. Bundle versions are not updated during development.</strong></p>
<p>OSGi semantic versioning applies to bundles as well as packages. When releasing a new version of a bundle
the change in the bundle version should give some indication of nature of the changes to the bundle.
In Aries the bundle version is the same as version of the Maven artifact version.