On 11 April 2016 at 22:15, Emilien Macchi <[email protected]> wrote: > On Mon, Apr 11, 2016 at 1:57 AM, Marcus Furlong <[email protected]> wrote: >> On 29 March 2016 at 09:53, Emilien Macchi <[email protected]> wrote: >>> Puppet OpenStack team has the immense pleasure to announce the release >>> of 24 Puppet modules. > >> Also (related to the above), are there any plans to do point releases >> including the bugfixes from the stable/mitaka branches? I ask because >> currently, if modules are installed from puppet forge, you still need >> to apply patches locally for things that have been fixed in the git >> stable branch. I've just noticed that I have patches for nearly every >> module for liberty. This is because after the initial puppet forge >> release, there were no further updates to any of the modules. > > What we do currently is backporting bugfix in stable branches (ex: > stable/liberty) but we don't produce tags quite often. It might change > in the future but until now we don't have much sub-releases between > cycles. > I would suggest you to deploy modules from git/branch (using your > stable version) and if any backport is required, feel free to submit > it and our team will review it according to our backport policy: > https://wiki.openstack.org/wiki/Puppet/Backport_policy
Is there any point releasing the modules on puppet forge if they are mostly going to be in a broken state (i.e. the initial release)? That is likely to reflect badly on the project? Cheers, Marcus. -- Marcus Furlong __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
