I created https://tickets.puppetlabs.com/browse/PUP-6169 for those who want to watch/vote/comment further. Thanks everyone!
Rob Nelson rnels...@gmail.com On Sun, Apr 10, 2016 at 9:16 PM, Rob Nelson <rnels...@gmail.com> wrote: > On Sun, Apr 10, 2016 at 5:05 AM, Alex Harvey <alexharv...@gmail.com> wrote > >> >> On 10 April 2016 at 03:59, R.I.Pienaar <r...@devco.net> wrote: >>> >>> >>> Not really sure I follow most of this rant. >>> >> >> Yes, fair enough. It was a bit of an uncalled-for rant. >> > > I think it's a legitimate concern. That's why I brought this up. Being > surprised by some missing or changed functionality on an upgrade makes > everyone less likely to upgrade. That's what I want to address. With that > in mind, my proposal remains to provide deprecated features an ID, log them > to a separate log, and/or provide tools and methods to present these > deprecation messages to the user front and center on demand. > > > Some greater context around this may help describe my concern and goals, > as it really goes beyond just Puppet. Like many people, I and my employer > use products from dozens of vendors and upgrades are, generally speaking, > not fun. To pick on another vendor, going from ASA v8.2 to v8.3 or higher > was fraught with a lot of danger. And that was just a minor release! > > Keeping track of where each vendor logs these messages - if they log them > anywhere at all, rather than just place them in the release notes - is > tiresome. I'd love to get ALL my vendors to create a central deprecation > log so I could review it before upgrades and compare it against the release > notes to see what will break. This would, in my opinion, be a competitive > advantage for any vendor that did this. I'd be far more likely to use them > over a competitor who ambushes me on every upgrade. > > We spoke of openness earlier, and Puppet is the only vendor I work with > that is open enough that we might be able to get such a feature. With a > little refinement past the initial implemention, I could then hold this up > as an example of how to do things for my other vendors. > > > So, if we can drag this discussion back around (split off from the other > thread), are there any other suggestions I should include in the RFE ticket? > > Rob Nelson > rnels...@gmail.com > > -- 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/CAC76iT9QS9G5rTKLcXSemmQo3mmQFh8NnX%2B6Qr0K4f0Yoiz5hQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
