... if you really want to make sure that VAX/VMS support stays working, set up a weekly (or even daily) cron job to do a smoke test.
Under VMS, there is no cron. Instead, what you want is a self resubmitting batch job (written in DCL).

Anyway, the main problem with the testing stats for the VMS platform is that we haven't got CPANPLUS working on VMS yet. (if anyone has achieved this, please drop me a /msg). Once CPANPLUS is up and running, we should be able to run the automated test suites and post the results to cpan_testers, which will get into the stats. This may well highlight general portability issues in the way people write modules, besides exercising (exorcising ??) the VMS port.

Please note that we should aim to test on different hardware platforms (VAX, Alpha and Itanium).

Hewlett Packard provide some hardware for general not-for-profit use, for platform porting, under their Test Drive program. I have a test drive account, and I encourage others who have the time and inclination to get one. Note that I use this in spare time. Again, please /msg me if you want to collaborate with me on testing VMS ports on the HP test drive machines.

--
I'm Not Just Another Perl Hacker


In reply to Re^2: Old VMS still supported? by rinceWind
in thread Old VMS still supported? by pfaut

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.