Re: Mark certain versions as "developer release" on CPAN

My understanding is that you just put an underscore anywhere in your version number, and CPAN magically treats it as a "developer release."

Now I have a question of my own, which I was going to post separately but I'll put here instead: what are the responsibilities of a "developer release"? I don't want to upload something half-finished as version "0.00_01" and then get dinged (and one-star-reviewed) because the documentation is practically non-existent or it's rife with bugs...

Comment on Re: Mark certain versions as "developer release" on CPAN

Replies are listed 'Best First'.
Re^2: Mark certain versions as "developer release" on CPAN by holli (Abbot) on Aug 08, 2005 at 17:44 UTC
In a production release, the API should be fixed and all (documented) features thoroughly tested. In a developer release the developer adds new experimental features, either for his beta testers, fellow developers or both. At least that's my understanding. holli, /regexed monk/	[reply] [d/l]
Re^3: Mark certain versions as "developer release" on CPAN by exussum0 (Vicar) on Aug 08, 2005 at 18:16 UTC
Much like gmail, which is not for general consumption. It's a joke. Laugh. :) ---- Give me strength for today.. I will not talk it away.. Just for a moment.. It will burn through the clouds.. and shine down on me.	[reply]
Re^2: Mark certain versions as "developer release" on CPAN by itub (Priest) on Aug 09, 2005 at 14:39 UTC
There are no written rules. I don't give bad ratings for new distributions that have a developer version number, but everyone else can do whatever they want. ;-)	[reply]

It's a joke. Laugh. :)