This prepares initial releases for all TripleO components except tripleo-quickstart (there is some discussion re moving this to an independent release model as we don't have stable branches for that because it's a bootstrapping tool, not an end user deliverable) Note also that I've aligned the puppet-tripleo release naming with the puppet openstack convention of a number of releases during the cycle despite being cycle-trailing, but other tripleo components adopt the 6.0.0.0b1 naming where we're tracking features/bugs associated with each milestone e.g ref https://launchpad.net/tripleo/+milestone/ocata-1 Change-Id: I890de6587efcc1ce3d93edcf8dc24e77f67b0d03
294 B
294 B