Thanks a lot for getting a start on this. I made some updates [1], that can be summarized as:
1. Better use of semver The previous version referred to the minor version as A.B.X or A.B.Y. X and Y in this case are really patch versions. According to semver [2] the minor version would be B with those examples. I tried to clear that up. Also, with the move to a major release cadence, we’ll be using major and minor version much more frequently when discussing versions and using patch version rarely (I suspect). 2. Deprecation of code and removal of deprecated code will only happen on major releases (e.g. MAJOR.0) This is the major change to what was originally stated. If we go with the above rule, that makes it super simple for our users and ourselves to remember when deprecations can be acted upon. It also gives our users the advantage of knowing they will always have at least a full major release cycle to react to a deprecation. What does everyone think about that? A concern about the jclouds-labs section [3]. By having that in there, I guarantee you users will extrapolate and apply that to *all* labs repos whether we like it or not. We’re often battling confusion on whether or not people should be using labs code and that won’t help. In some cases we want labs code to be used (e.g. jclouds-chef) but having that wording there will scare many people off. My preference would be to not have that section there. Actually my preference would be to promote apis/providers to jclouds core once they're out of Beta but that’s another discussion. Everett [1] https://wiki.apache.org/jclouds/DeprecationAndBetaPolicy?action=diff&rev2=3 [2] http://semver.org/ [3] https://wiki.apache.org/jclouds/DeprecationAndBetaPolicy#jclouds-labs On Jun 24, 2014, at 5:16 PM, Andrew Phillips <aphill...@qrmedia.com> wrote: >> How can we mitigate this risk? >> >> 1. A clearly communicated deprecation policy. > > [...] > >> 2. A clearly communicated Beta policy. > > Here's something to shoot at: > > https://wiki.apache.org/jclouds/DeprecationAndBetaPolicy > >> 3. A better roadmap and better release notes > > Here another something to shoot at: > > https://wiki.apache.org/jclouds/Roadmap > > For this one especially, please note: for the themes, I've just grabbed > snippets from whatever I've heard and seen go by. I'm not putting those > topics forward as "my choice" in any way! > > Hope that helps... > > ap
