[
https://issues.apache.org/jira/browse/CB-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171054#comment-14171054
]
ASF GitHub Bot commented on CB-7774:
------------------------------------
Github user mmocny commented on a diff in the pull request:
https://github.com/apache/cordova-coho/pull/53#discussion_r18835133
--- Diff: docs/versioning-and-release-strategy.md ---
@@ -19,17 +19,100 @@
#
-->
-# Versioning and Release Strategy
+# Versioning Strategy
-## Versioning Strategies
- 1. `SemVer` ([Semantic Version](http://www.semver.org))
- * Used by platforms, plugman, CLI, core plugins
- * Is important when describing dependencies in a sane way (e.g. within
plugin.xml files)
+## Version Format
-CLI exists in both lists because its version has the format:
`CadVer-SemVer`
- * E.g.: `3.0.0-0.5.1`
+`SemVer` ([Semantic Version](http://www.semver.org)) will be used as the
+version format for all components, including platforms, plugman, CLI, core
+plugins. Doing so is important when describing dependencies in a sane way
+(e.g. within plugin.xml files). Although the CLI previously used a
+`CadVer-SemVer` format, it now uses a simple SemVer format. The `CadVer`
format
+is no longer used in any Cordova components. The plugins no longer have an
`r`
+prefix.
-## Release Strategies
+The semantics of `SemVer` should be followed, bumping the appropriate digit
+based on the impact of the new content.
+
+## Branching and Tagging
+
+All components also follow the same branching and tagging strategy,
including
+plugins and tools. A `major.minor.X` release branch (i.e., "3.7.x") should
be
+created, and any fixes should be appended to that release branch. New
content
+should be on the master branch, and a new release branch created at release
+time. When a release is performed, a release tag is added to the
appropriate
+branch (i.e., "3.8.0" tag is put on the "3.8.x" branch).
+
+## Version Behavior
+
+Plugin versions will all be separate and independent. So there may be a
"1.2.0"
+of the Device plugin, and a "3.4.5" of the Camera plugin at the same time.
+The bumping of the version numbers of each plugin should be appropriate to
the
+new content added to that plugin. The `cordova plugin add` command will add
+the most recent version of that plugin by default, though alternately the
user
--- End diff --
This is correct as of today, but we would prefer to amend to say "most
recent *compatible* version". I know you are capturing today's behaviour here,
but just calling this out.
> update strategy for versioning
> ------------------------------
>
> Key: CB-7774
> URL: https://issues.apache.org/jira/browse/CB-7774
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Coho
> Reporter: Marcel Kinard
>
> With the advent of independent platform releases, we need a strategy for how
> to version all the Cordova components.
> See http://markmail.org/message/zijjq4xe7wbbcwtg
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
