[openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)
emilien at redhat.com
Tue Apr 12 12:12:09 UTC 2016
On Tue, Apr 12, 2016 at 7:45 AM, Marcus Furlong <furlongm at gmail.com> wrote:
> On 11 April 2016 at 22:15, Emilien Macchi <emilien at redhat.com> wrote:
>> On Mon, Apr 11, 2016 at 1:57 AM, Marcus Furlong <furlongm at gmail.com> wrote:
>>> On 29 March 2016 at 09:53, Emilien Macchi <emilien at redhat.com> 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
>> 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:t
> 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?
Like other projects we work by iterations where each release contains
new features, bugfixes, etc. When we fix bugs after a release, we do
our best to backport it to stable branches, and provide a new release
when possible. Most of our operators do not run master branch
directly, and I think we're doing a good job at backports, thanks to
CI and reviewers.
During Liberty & Mitaka, release management was handled by a very few
human resources. It will change during Newton cycle, we are working
hard to transfer the release management to OpenStack release team and
hopefully it will help to provide more releases than before.
More information about the OpenStack-dev