New classes aren't suitable for a patch release, and I'm not going to
create a new minor release now.
In future open up pull requests against the stable branches if there's
no associated Redmine ticket on the release, and earlier (release was
prepared yesterday).
> > Can we please have the following two issues included into Foreman 1.13.1
> > via puppet-foreman_proxy release update?
> >
> > https://github.com/theforeman/puppet-foreman_proxy/commit/
> 9b75833407377bc08cc821dd9e51f41ef1234f11
>
> Released in 4.0.3.
>
>
Thanks!
I find this to be a grey area with our current architecture given that
plugins can release when and how they want. But since we manage plugins
through puppet-foreman and puppet-foreman_proxy they are partially bound by
these rules which could result in a plugin or smart proxy plugin being
released in a broken way (if the configuration of said plugin is paramount
to it running).
Also, I'd be happy to do a release, or help manage any release work for
Foreman or the puppet modules!
···
On Wed, Oct 26, 2016 at 3:36 AM, Dominic Cleal wrote:
> On 25/10/16 17:33, Eric D Helms wrote:
In future open up pull requests against the stable branches if there’s
no associated Redmine ticket on the release, and earlier (release was
prepared yesterday).
> > Can we please have the following two issues included into Foreman 1.13.1
> > via puppet-foreman_proxy release update?
> >
> > https://github.com/theforeman/puppet-foreman_proxy/commit/
> 9b75833407377bc08cc821dd9e51f41ef1234f11
>
> Released in 4.0.3.
>
> > https://github.com/theforeman/puppet-foreman_proxy/commit/
> 90a98bb918802e7dd155518b8298108c66ca88d0
>
> New classes aren't suitable for a patch release, and I'm not going to
> create a new minor release now.
>
Do you have an estimation for when ? or do you mean not in 1.13.x? its a
shame not to have it in the installer for existing / new users imho.
thanks,
Ohad
···
On Wed, Oct 26, 2016 at 10:36 AM, Dominic Cleal wrote:
> On 25/10/16 17:33, Eric D Helms wrote:
In future open up pull requests against the stable branches if there’s
no associated Redmine ticket on the release, and earlier (release was
prepared yesterday).
No, I don't plan to do it - somebody else may put it together!
The next release from master would be 5.0.0 in about a month, which
would go into 1.14.0 by default.
> or do you mean not in 1.13.x?
Quite possibly, I'd normally only release patch versions of the modules
to fix bugs for minor Foreman updates. I don't particularly wish to add
new features in those updates.
> its a
> shame not to have it in the installer for existing / new users imho.
It is in the installer, for 1.14.x.
···
On 26/10/16 09:47, Ohad Levy wrote:
> On Wed, Oct 26, 2016 at 10:36 AM, Dominic Cleal > wrote:
> On 25/10/16 17:33, Eric D Helms wrote: