Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • PAUSE doesn't allow new uploads with the exact same version number as what is there already.

    And as long as the code, nor the docs, change, I wouldn't upload anything, yet. There's no reason for people to upgrade.

    Just my 2 cents.

  • If PAUSE knows about you taking over (that is, you have PAUSE permission to upload those modules), you don't need to do anything else.

    People should submit bugs via RT, and you have access to that. If the previous maintainer is still reading e-mail sent to the address written in the docs, (s)he'll forward people to you.

    When you have a new release of a module, add yourself to the AUTHORS, and publish it (with a higher version number, of course).

    Don't do a release just to say "hey I'm here".

  • I'm assuming you took over the modules mainly because you had some bug that you needed fixing, or some feature you needed to add.

    When you do the release with that change, change the author value.

    If you take it over, and then disappear and don't do anything, you don't want your name in there. The need to release acts as a kind of sincerity filter.