On Mon, Feb 15, 2016 at 8:13 AM, Emilien Macchi <emil...@redhat.com> wrote:
> Hi, > > While Puppet modules releases are independently managed, we have some > requests from both RDO & Debian folks to push a first tag in our Puppet > modules, for Mitaka release, so they can start provide Mitaka packaging > based on tag, and not on commits. > > This is something we never did before, usually we wait until the end of > the cycle and try to push a tag soon after the official release. > But we want to experiment beta tags and see if it helps. > > The Mitaka tag would be 8.0.0b1 and pushed by the end of February (I'll > work on it). > The forge does verify that versions match semver 1.0.0, which states "a pre-release version number MAY be denoted by appending an arbitrary string immediately following the patch version and a dash. The string MUST be comprised of only alphanumerics plus dash [0-9A-Za-z-]" thus this tag would more appropriately be 8.0.0-beta1 (as per the given example on http://semver.org/spec/v1.0.0.html). The forge doesn't care about tags, but if you have 8.0.0b1 in the metadata it will probably deny the publish. Though stable/mitaka branch won't be created until official Mitaka > release. Same thing for release notes, that will be provided at the end > of the cycle as usual. > > Any thoughts are welcome, > -- > Emilien Macchi > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
