Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Whomever your release-engineers, qa.. etc.. the post-development people are, incremental releases are annoying.

That hasn't been my experience - people usually thank me for regular incremental releases :-) A few things to consider:

  • Just because there are regular updates doesn't mean you need to use them. I don't go around every live project and update modules every time a new release comes out. Release and integration are independent tasks.
  • If integrating code is causing problems spend some time figuring out why. You can often make it easier (e.g. one of my dev boxes happily updates from CPAN every day, runs the test suites on all my code and mails me if it comes across any problems - no manual intervention needed.)
  • Incremental releases means that you can practice your QA and integration tasks more if you wish. People get better with practice.
  • Incremental releases mean more bug fixes are available sooner. The sooner I get a bug fix the more time I have for integration and regression testing. More time is good.
  • Incremental releases mean you get more opportunities to re-prioritise. You can lobby to get the patches that are more important to you done earlier.
  • Small releases are easier to schedule, so are more likely to come out on time - making the work of QA and integration people much easier to plan.
Doing something once in a while with a lot of work feels a lot nicer than doing a little bit less work often.

It can do. It can also be a complete pain. I come across reactions of the "You want us to do what by when?!?!" variety a lot more than "Please stop giving me these small bits of work".

In reply to Re^2: Small incremental releases are good! by adrianh
in thread Small incremental releases are good! by adrianh

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others surveying the Monastery: (8)
    As of 2018-06-25 17:59 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (128 votes). Check out past polls.