Ask not what CPAN can do for you, ask what you can do for CPAN. CPAN day falls on the 16th of August. What is CPAN day? The anniversary of the first "true" module upload to CPAN, on the 16th August 1995, and a call to arms for bug fixes, releases and other contributions.

A nice idea, considering that (at time of writing) there are 501 pages of issues on RT (yes, I appreciate many of these are very old or for modules which no longer exist).

See also The ghost of CPAN days past.

Update: that should have said 501 pages of issues.

Update 2: /paves/pages/.

Replies are listed 'Best First'.
Re: CPAN Day - 16th of August
by hippo (Archbishop) on Aug 05, 2014 at 13:53 UTC
    there are 501 issues on RT

    I thought that sounded surprisingly low, so I followed the link. Turns out there are 501 pages of issues on RT, which is a different prospect entirely.

    Nonetheless, I like the idea of CPAN day and will try to bring forward at least one release to coincide if I can.

[reply]

      Thanks, I was distracted when posting, and managed to mess up my update when posting from my phone.

[reply]
Re: CPAN Day - 16th of August
by Bloodnok (Vicar) on Aug 06, 2014 at 08:59 UTC
    Hiya marto,

    Would a, IMO sensible, first step not be to close out the RT 'issues' against no longer extant modules ?

    A user level that continues to overstate my experience :-))
[reply]

      I've got a draft email to the powers that be suggesting something similar. It's a work in progress while I work out the reasons for keeping them. I suppose one reason would be that someone could be using a module, unaware that it has been deleted. Bugs, patches and coversations submittied via RT would still be available for reference. As yet this is the only sensible reason I can think of for keeping them. Thanks for your input.

      Update: Raised as a meditation.

[reply]
        NaP marto, pleased (and surprised) to have been of some use/help :-)

        As a CM practitioner, I would suggest that, in addition to your meditation, an extra 'final' lifecycle state is introduced that clearly and unambiguously identifies such tickets as to be raised but unaddressable e.g. 'will not fix - obsolete module' or similar ?

        A user level that continues to overstate my experience :-))
[reply]

        in short :) backpan, thats why :)

[reply]

Back to Perl News