On Wed, Oct 26, 2016 at 3:36 AM, Dominic Cleal <domi...@cleal.org> wrote:
> On 25/10/16 17:33, Eric D Helms wrote: > > 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! > > 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. > OK - thanks for the info. 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! > > 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). > -- > Dominic Cleal > domi...@cleal.org > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
