Hello,

I'm always interested by answers concerning this:

On 13/10/2015 23:38, Francois Lafont wrote:
> Hi,
> 
> On 12/10/2015 23:02, Rob Braden wrote:
> 
>> Puppet Agent 1.2.6 is out! This is a new minor release of the all-in-one
>> agent bundle which contains no updated component code, but fixes bugs in
>> packaging and service management.
> 
> Thanks, good news. ;)
> 
>> * Includes a fix for an issue that could, in some cases, leave the puppet
>> and mcollective services stopped and unregistered after a package upgrade
>> from an earlier Puppet Agent release.
> 
> When there is a new release, this page below is very useful (for me):
> 
>     
> https://docs.puppetlabs.com/puppet/latest/reference/about_agent.html#release-contents-puppet-agent-1x
> 
> Indeed if I click on the number version of a specific component (Puppet,
> MCollective etc.) I have the release note of this component with the
> reference to the fixed bugs reported in https://tickets.puppetlabs.com
> etc. I find this very useful, thanks for that.
> 
> But in the case of this current 1.2.6 release, the page above is not
> useful because there is no change for each component of the puppet-agent.
> Indeed, this 1.2.6 release just concerning the packaging.
> 
> Is there somewhere a release note concerning the packaging with the
> references to the fixed bugs reported in https://tickets.puppetlabs.com
> (exactly like the release notes of each component of the AIO puppet-agent)?
> 
> If not, is there a github repository or something like that to see the
> last commits which could be related to the fix pointed out in this
> announce?
> 
> Thanks in advance for your help.

Regards
François Lafont

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/56310078.9090702%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to