Hey,
Usually there''s about million things that can go wrong but ever since
3.x
I''ve really had no issue whatsoever with upgrading releases. This was
quite
a bit different from 2.6/2.7 and I think really speaks to the work the QA
folks at Puppet Labs are trying to do.
That being said, most issues we had actually stemmed from our own code
base. Things you know you shouldn''t have done but did tend to bite you
in
the ass when you least expect it. I''ve been able to avoid any major
issues
since 3.x by simply having a sane, fairly well tested, code base. Also a
good tip, don''t patch custom things into Puppet or Hiera etc, that will
break, eventually.
--
Daniele Sluijters
On Monday, 21 October 2013 20:54:13 UTC+2, Kurt Wall
wrote:>
> Hi everyone,
>
> We are working on enhancing our internal testing so we can improve the
> overall quality of Puppet releases. For example, I am one of two QA
> engineers assigned full-time to testing Puppet''s FOSS stack.
I''m seeking
> your input and experience to help us identify what we''re missing
and what
> we can improve. We have an extensive test suite, but there''s
always room
> for more testing and for better testing.
>
> When a new version of Puppet is released, what do you try out before you
> deploy the it in a production setting? What sorts of behaviors do you test
> before you unleash a new release on unsuspecting machines and users? To
> express it differently, what has bitten you in the past when deploying a
> Puppet release? What makes you wary when installing a new release of
Puppet?
>
> Thanks!
>
> Kurt
>
--
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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.