Will the Puppet 4.0 release be available through a dist-upgrade on apt.puppetlabs.com or a through a normal upgrade?
On Fri, Feb 27, 2015, at 09:31 PM, Kylo Ginsberg wrote: > > Priorities > * Puppet Agent 1.0.0 > * Puppet Server 2.0.0 > * Puppet Server 1.1.0 > * Puppet 4.0.0 / 3.8.0 > * Hiera 2.0 > > > Our main emphasis continues to be on the work needed to release > puppet-agent 1.0.0 and puppet-server 2.0.0. Much of this is > Jenkins-related (feel free to follow along at > https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/, but it’s > WIP), but we’ve also been iterating on the file paths spec mentioned > last week at > https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md. > > We’ve also been talking a lot within the walls of Puppet Labs about > things we can do to make the move from puppet 3 to puppet 4 a bit > easier. You’ll see this in a couple places. > > > In the puppet/stable branch, we added two tickets of note: finishing > touches to the 4x function API (PUP-1806), and the ability to specify > parser = future per environment (PUP-4017). That latter is part of > making the puppet 3 -> puppet 4 move eaiser. It’s also actually a new > feature, so the next puppet 3.x release will be 3.8.0 (not 3.7.5), > and it will be released at the same time as puppet 4.0.0 / > puppet-agent 1.0.0. We’re currently shooting for getting this done in > two more weeks. > > > Meanwhile we are working on tickets that will not hold up the release > if we do not get them done in time - PUP-2315, better error messages > for type mismatch in function calls, and PUP-4047, possibly opt out of > errors for "non productive expression". We’ve also “unfrozen” merges > of community PRs, and have merged some nice-to-have low-risk PRs > (since we have a little more time, natch). > > > We are also working on finishing touches for Puppet Strings and > Hiera 2.0.0 > > > On the puppet-server side, work continues on the prep for the Puppet > Server 2.0 release. The main thrust of this release is to provide > compatibility with Puppet 4.0. In addition, as part of our > conversation about easing the puppet 3 -> puppet 4 migration, we’ve > been considering how to deal with compatibility issues across the > network between Puppet 3.x agents and the Puppet 4.0 / Puppet Server > 2.0 server-side components (because we’re changing the URL structure > that the agents use to communicate with the master). > > > As of right now, it seems like we’re fairly certain that Puppet Server > 2.0 will *not* be compatible with Puppet 3.x agents, and will attempt > to issue an informative 404 error if you try to hit a Puppet Server > 2.0 master with a Puppet 3.x agent. It seems likely that we’ll have > another near-term release (Puppet Server 2.1, most likely) where we > add in support for re-routing the URLs that are used by a Puppet 3.x > agent. Your 3.x agents will still need to be using manifests/modules > that are compatible with the future parser that will ship in 4.0 for > you to benefit from this, but hopefully it will provide a slightly > easier upgrade path that won’t force you to update all of your agents > to 4.x at precisely the same moment in time that you upgrade to Puppet > Server 2.x. > > > At the same time, we’re also actively working on a Puppet Server 1.1 > release. This release will land *after* Puppet Server 2.0, and will be > targeted at users who aren’t ready to make the jump to Puppet 4.0. The > main thrust of this release will be improvements in memory usage and > improvements in the default values we provide for settings related to > tuning Puppet Server. We’re hoping to set things up so that the > initial installation of Puppet Server will be better at recognizing > the hardware resources available on the system and providing good > initial guesses about the appropriate tuning settings to take > advantage of those resources. We’ll also be providing some new tuning > documentation that will help you tweak things to suit your particular > environment. All of the improvements that we make for Puppet Server > 1.1 will be rolled up into the next Puppet Server 2.x release as well, > so that users who are ready to move to Puppet 4.0 will be able to take > advantage of these improvements right away. > > > Btw, if you’ve read this far, then you deserve a little chuckle. The > most entertaining bug I’ve seen in a while was merged recently. The PR > has a nice description: > https://github.com/puppetlabs/puppet/pull/3605. > > Kylo > -- > Kylo Ginsberg | [email protected] | irc: kylo | twitter: @kylog > > > -- > 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CALsUZFH%2BXY57-ZYNwcLWtBaJ7KcMq0X0N1xu5_cTuLQGOViNQQ%40mail.gmail.com[1]. > For more options, visit https://groups.google.com/d/optout. Links: 1. https://groups.google.com/d/msgid/puppet-dev/CALsUZFH%2BXY57-ZYNwcLWtBaJ7KcMq0X0N1xu5_cTuLQGOViNQQ%40mail.gmail.com?utm_medium=email&utm_source=footer -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/1425118852.2513552.233579761.367C4262%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
