Well, that was the whole collections idea in a nutshell, but every one of those new repos would inevitably leave some people stranded on an old one. Terrifyingly, there are still something like 100,000 hosts[1] hitting the EOL'ed 3.x repos, which will never get any updates... there's no clearly great answer here but optimizing to protect people who have 'ensure => latest' against upstream repos doesn't seem like the right thing.
--eric0 [1] Big error bars on this number, but we do get ~5M hits per day for the old repository metadata across the deb and yum repos, so about 100K hits per 30 minute interval... > On Mar 3, 2017, at 1:55 PM, Rob Nelson <[email protected]> wrote: > > I second this. While PC1 didn't quite work out the way many expected, it made > it impossible to accidentally the whole (puppet 4) bottle when it came to > updating your machines still running puppet 3. > > > Rob Nelson > [email protected] <mailto:[email protected]> > On Fri, Mar 3, 2017 at 4:13 PM, Eli Young <[email protected] > <mailto:[email protected]>> wrote: > Rather than calling the new package repository "puppet", it might make more > sense to call it "puppet5". That way, when Puppet 6 rolls around, it can go > into its own repository ("puppet6") and people can change the repository over > once they've tested that their code works with the new version. > > On Mon, Feb 27, 2017 at 3:59 PM, Eric Sorenson <[email protected] > <mailto:[email protected]>> wrote: > Hi all - we're nearing the end of the Puppet 4.x series feature development. > It's been almost two years since Puppet 4.0 dropped and it seems like an > opportune time to start thinking about the next semver major. > > There was some discussion last year[0], but the development work is truly > rolling forward now, so I wanted to restart the conversation about Puppet 5 > to elicit feedback and make sure to incorporate the community's needs into > the plan. > > The headline here is that the core open-source "Puppet Platform" > (puppet-agent, puppet-server, puppetdb) are moving to a more coordinated > release model, with compatibility guarantees and consistent versioning among > the components. The first release of this "Puppet Platform 5", currently > targeted at May, will bring these components' major versions together and > provide some nice features without a huge backwards-incompatible break. > > A couple of FAQs, or rather questions I imagine will be frequently asked: > > Q: Puppet 5, what the hell eric0?! I just spent a month updating my code to > run under Puppet 4. > A: No Puppet code that works under Puppet 4 needs changing[1] to work under > 5. This is a semver major to release some backwards-incompatible changes that > have stacked up, plus some additional feature work, but does not affect the > language. Puppet 4 won't be EOL any time soon (and we're guaranteeing > commercial customer support until 2018) but we've got to keep the platform > moving forward. Plus, it seems like a good opportunity to eliminate the > confusion caused by "Puppet 4" being delivered in packages, split between > puppet-agent-1.x and puppet-server-2.x .... > > Q: So what *is* in it? Why should I upgrade? > A: Lots of good stuff. Hiera 5 with eyaml is built-in; it's UTF-8 clean; > network comms are pure, sweet, fast JSON. Our current Ruby versions are > EOL'ed, so we're moving to MRI Ruby 2.4 on the agent and jruby9k on the > server. The PE-only puppet-server metrics service is getting some > enhancements and will be open-sourced. > > Q: How's it going to be delivered? Are Puppet Collections still a thing? > A: Funny you should ask. As we kicked around a couple of months ago[3], it's > been two years and the collections idea just hasn't worked out in practice, > so it seems wise to iterate and keep evolving. The current plan is to create > a new repo, parallel with the existing PC1 repos, simply named 'puppet'. The > platform components will roll into it and future semver-majors will be > coordinated across the components, hopefully leading to smaller, easily > digestible chunks of change. > > You can see the complete list of changes (which will evolve as we gather > feedback and adjust scope) at this JIRA query[2]. If there's anything on the > roster that looks like it'll break your world — or, conversely, if you want > to nominate a change that's important to you but isn't currently on the list > — this thread is the place to do that. > > --eric0 > > [0] https://groups.google.com/d/msg/puppet-dev/RHa2tMPRTx4/sA8RX_gS1ogJ > <https://groups.google.com/d/msg/puppet-dev/RHa2tMPRTx4/sA8RX_gS1ogJ> > [1] I'm reserving a tiny, tiny asterisk for some Ruby extensions that use > internal APIs that may change, like pre-Puppet 4.9 lookup extensions. > [2] https://tickets.puppetlabs.com/issues/?filter=12940 > <https://tickets.puppetlabs.com/issues/?filter=12940> > [3] https://groups.google.com/d/topic/puppet-dev/3-HSUz5OnHg/discussion > <https://groups.google.com/d/topic/puppet-dev/3-HSUz5OnHg/discussion> > Eric Sorenson - [email protected] <mailto:[email protected]> > director of product, ecosystem and platform > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/6FF107F6-088A-43E2-BECF-772D8C153C49%40puppet.com > > <https://groups.google.com/d/msgid/puppet-dev/6FF107F6-088A-43E2-BECF-772D8C153C49%40puppet.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAE%2BtgeMKENaAjphZ1SX0dPin0pXJZaR%2B8d%3DEMXvC6cX-NpZsqQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/puppet-dev/CAE%2BtgeMKENaAjphZ1SX0dPin0pXJZaR%2B8d%3DEMXvC6cX-NpZsqQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAC76iT8PquryseW873Sx2Q9URq4bdmCA3oX1FnMxKU6-%3D7Esjg%40mail.gmail.com > > <https://groups.google.com/d/msgid/puppet-dev/CAC76iT8PquryseW873Sx2Q9URq4bdmCA3oX1FnMxKU6-%3D7Esjg%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. Eric Sorenson - [email protected] <mailto:[email protected]> director of product, ecosystem and platform -- 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/367CC459-5E44-4164-9096-B34D5DE1CAB6%40puppet.com. For more options, visit https://groups.google.com/d/optout.
