Open Stack

So is it implied that a version "8.0.0b1" of a puppet module works
with the "8.0.0b1" of it's parent project ?

This has some implications, it means there are expectations that
puppet-openstack is able to keep up with upstream changes throughout
the cycle.
We've gotten pretty good at following trunk with the myriad of CI but
some changes are more challenging than others.

Would there be times where the puppet module's tagged release would
lag behind upstream (say, a couple days because we need to merge new
things) and if so, does tagging lose some of it's value ?
The liberty puppet modules were released quite a while after liberty
went stable.


David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]


On Mon, Feb 15, 2016 at 11:13 AM, Emilien Macchi <emilien at 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).
> 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>