"That's better, but it still doesn't
      really explain the branch names or how they correspond to platform
      releases. "
      Done, with branch name instructions:
       
https://github.com/ge0ffrey/jboss-integration-platform-bom/commit/a962788949fdabf32f560c925dd613c9a62c7e3d
      The correspondance was already documented at the bottom of the
      readme, see section "version mapping".
        With kind regards,
          Geoffrey De Smet
      
      On 29-10-13 16:15, Randall Hauch wrote:
    
      In README.adoc:
      > @@ -44,14 +65,22 @@ Dependency exclusions should be avoided, because they cannot be overwritten by c
>  All IP developers needs to unanimous (undisputed) to keep the exclusion.
>  So as soon as 1 IP developer calls for the removal of an exclusion, he/she can immediately remove it.
>  
> +=== Branching policy
> +
> +The +master+ branch is never released. Per product set there is 1 release branch,
> +so multiple IP products (as well a multiple IP projects) use the same release branch.
> +
> +Any change applied on a release branch, should be applied on all newer release branches and +master+ too.

      That's better, but it still doesn't really explain the branch
        names or how they correspond to platform releases. One or one?
        And if so, what's the benefit of this over simple tagging?
      —
        Reply to this email directly or view
          it on GitHub.