After the Puppet 3.5.0 release problems, we had a retrospective and tried to figure out some process improvements which would have surfaced the problems earlier. Despite a lengthy 4-week release candidate cycle, that release still had a fatal flaw that nobody had caught until it went into final release. As we talked it over, our thoughts turned to continuous delivery. Puppet (along with most of the other open-source projects) already produces packaged artifacts as moves through our Jenkins pipeline, so it seemed like a natural step to make those packages publicly available.
In lieu of release candidates, we are moving toward a more automated system which will have the latest green builds (passed spec and Beaker acceptance tests) cut off the 'master' branch for most of our projects. What this means is that as we near feature complete on a release, like the coming Puppet 3.7.0 release, users like yourself can begin trying out the packages to ensure that the new features haven't broken anything you depend on, and that the new features work the way you expect/want them to. The repos are live now and you can try them out by following these directions: https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#using-the-nightly-repos Hopefully this will help get faster turnaround AND better coverage. Please let us know if you find it useful! Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 puppet platform // coffee // techno // bicycles -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/9283F1EA-22D6-491C-BD08-F6DBAA863861%40puppetlabs.com. For more options, visit https://groups.google.com/d/optout.
