Repository: brooklyn-docs Updated Branches: refs/heads/0.12.0 6184fe07e -> 50ba8232d
update release notes for 0.12, adding a few things i'm aware of Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/a4fa1d7b Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/a4fa1d7b Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/a4fa1d7b Branch: refs/heads/0.12.0 Commit: a4fa1d7b059e8e37d1bf4acd865b92eff11f746c Parents: 9bf9b26 Author: Alex Heneveld <[email protected]> Authored: Thu Sep 7 12:52:38 2017 +0100 Committer: Alex Heneveld <[email protected]> Committed: Thu Sep 7 12:59:43 2017 +0100 ---------------------------------------------------------------------- guide/misc/release-notes.md | 38 ++++++++++++++++++++++++++++++-------- 1 file changed, 30 insertions(+), 8 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/a4fa1d7b/guide/misc/release-notes.md ---------------------------------------------------------------------- diff --git a/guide/misc/release-notes.md b/guide/misc/release-notes.md index 6f2327c..a933dfb 100644 --- a/guide/misc/release-notes.md +++ b/guide/misc/release-notes.md @@ -14,19 +14,41 @@ to Brooklyn's commercial users for funding much of this development. ### New Features +1. Auto-bundling of BOMs and the ability to manage and persist bundles: related entities are now grouped in bundles +and all management activity (deletion, upgrades, persistence) done at the level of the bundle. +You can now start a new Brooklyn instance pointed at a persistence store, +and it will automatically load all bundles installed into the previous Brooklyn +through the REST API. + +1. Application deployment "create-or-reuse" semantics by specifying an application ID. +This supports workflows that require something deployed in a singleton pattern, +such as in a continuous integration pipeline. + +1. jclouds latest version: improved Azure support and more. + +1. Optimization: much better memory usage and better CPU usage. + ### Backwards Compatibility -Changes since 0.10.0: +Changes since 0.11.0: + +1. The `cluster.first` sensor set by a group on its children has been removed due to ambiguity and deadlock. +Equivalent information can be retrieved by looking at the `cluster.first.entity` and this now updates correctly. + +1. Version names now have a recommended syntax, and warnings will occur if it is not followed. +In obscure cases where version strings differ only in symbols, +different version names can map to the same OSGi version string and may now +block install or cause replacement where previously they could exist simultaneously. +For example if you have a bundle `1.0.0$SNAPSHOT` and you install `1.0.0&SNAPSHOT`, this will now be treated as a replacement. -1. The usage of `ManagementContext.getConfig()` is deprecated for storing non-config data like -singletons and cached objects. Use `ManagementContext.getScratchpad()` instead. Affected objects: +1. Types (catalog items) are validated sooner and so errors may occur earlier if there are invalid blueprints. +In addition if a bundle cannot be installed, it now reverts to the state before the bundle installation. +(Previously it would leave the bundle in the half-installed error state for the user to remedy.) - * BrooklynCampConstants.CAMP_PLATFORM - * CampYamlParser.YAML_PARSER_KEY - * BrooklynServiceAttributes.BROOKLYN_REST_OBJECT_MAPPER - * BrooklynWebConfig.SECURITY_PROVIDER_INSTANCE +1. Deletion and deprecation of individual catalog items is no longer persisted or kept after a restart. +These changes should be done by updating or deleting the BOM/bundle containing the item. For changes in prior versions, please refer to the release notes for -[0.10.0]({{ site.path.v }}/0.10.0/misc/release-notes.html). +[0.11.0]({{ site.path.v }}/0.11.0/misc/release-notes.html).
