brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From geomacy <...@git.apache.org>
Subject [GitHub] brooklyn-docs pull request #198: [WIP] Versioning
Date Tue, 27 Jun 2017 10:59:53 GMT
Github user geomacy commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/198#discussion_r124210641
  
    --- Diff: guide/blueprints/catalog/versioning.md ---
    @@ -3,18 +3,130 @@ title: Versioning
     layout: website-normal
     ---
     
    -### Versioning
    +Brooklyn supports multiple versions of a type to be installed and used at the same time.
    +Versions are a first-class concept and are often prominently displayed in the UI.
     
    -Version numbers follow the OSGi convention. This can have a major, minor, micro and qualifier
part.
    -For example, `1.0`. `1.0.1` or `1.0.1-20150101`.
    +In order to do this, Brooklyn requires that the `id:version` string be unique across
the catalog:
    +it is normally an error to add a type if a type with the same `id:version` is present.
    +The exceptions to this are if the definition is identical, or if the `version` is noted
as a `SNAPSHOT`.
    +In extraordinary circumstances it may be appropriate to delete a given `id:version` definition
    +and then add the new one, but this is discouraged and the usual practice is to:
     
    -The combination of `id:version` strings must be unique across the catalog.
    -It is an error to deploy the same version of an existing item:
    -to update a blueprint, it is recommended to increase its version number;
    -alternatively in some cases it is permitted to delete an `id:version` instance
    -and then re-deploy.
    -If no version is specified, re-deploying will automatically
    -increment an internal version number for the catalog item.
    +* Use a `-SNAPSHOT` qualifer suffix on your version when developing
    +* Increase the version number when making a change to a non-SNAPSHOT type  
    +
    +When adding to the catalog, if no version is supplied, Brooklyn may automatically 
    +increment the version number for the catalog item.
    +
    +When deploying a blueprint, if a version number is not specified Brooklyn will typically
use
    +the highest ordered version (see "Ordering" below) in the catalog for the referenced
type,
    +and will thereafter lock the use of that version in that blueprint.
    +(An exception is where types are co-bundled or an explicit search path is defined;
    +in the context of evaluating one type, Brooklyn may prefer versions in the same bundle
or on the search path.) 
    --- End diff --
    
    "may" again


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message