In fact you should do BOTH! State the minimum required and state the recommended version. The latter should have been thoroughly tested.

Having a lowest supported and a recommended might have a lot of added value to a module. Say that the newest/hippest module adds a feature that can speed up you code by a factor 10, it is worth supporting that with a fallback to the old code if the newest feature is not available.

You META.yml might then have a section similar to:

requires:
    perl:                5.008001
    DBI:                 1.628
    DBD::File:           0.42
    SQL::Statement:      1.405
    Text::CSV_XS:        1.01
recommends:
    DBI:                 1.636
    DBD::File:           0.44
    SQL::Statement:      1.412
    Text::CSV_XS:        1.31
configure_requires:
    ExtUtils::MakeMaker: 0
    DBI:                 1.628
build_requires:
    Config:              0
test_requires:
    Test::Harness:       0
    Test::More:          0.90
    Encode:              0
    Cwd:                 0
    charnames:           0
test_recommends:
    Test::More:          1.302085

[download]

Enjoy, Have FUN! H.Merijn

In reply to Re^2: Checking if your CPAN distributions need to bump their prereq versions (no!) by Tux
in thread Checking if your CPAN distributions need to bump their prereq versions by stevieb

Title:
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, details, 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, summary, 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.