Bug #120768 for Try-Tiny: Time for 1.00 release?

Mon Mar 27 04:58:14 2017 NEILB [...] cpan.org - Ticket created

Subject:

Time for 1.00 release?

Given how far Try-Tiny is up river (the highest for any non-dual-life dist), it seems unlikely that the API is going to change. So how about bumping the version to 1.00 sometime soon, to signify "stable interface" and stable implementation? Neil

Mon Mar 27 12:47:36 2017 karen [...] froods.org - Correspondence added

Subject:	Re: [rt.cpan.org #120768] Time for 1.00 release?
Date:	Mon, 27 Mar 2017 09:46:58 -0700
To:	bug-Try-Tiny [...] rt.cpan.org
From:	Karen Etheridge <karen [...] froods.org>

For whom does a 1.x version number indicate stability? Version numbers are arbitrary and everyone uses different degrees of version change to indicate different things. Put another way, will this actually help anyone (any organization, distributor, vendor etc)? (Personally, I start at 0.001 and increment by 0.001 each time, and the version has no further meaning than indicating a sequence.) On Mon, Mar 27, 2017 at 1:58 AM, Neil_Bowers via RT < bug-Try-Tiny@rt.cpan.org> wrote: Show quoted text

> Mon Mar 27 04:58:14 2017: Request 120768 was acted upon. > Transaction: Ticket created by NEILB > Queue: Try-Tiny > Subject: Time for 1.00 release? > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: NEILB@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=120768 > > > > Given how far Try-Tiny is up river (the highest for any non-dual-life > dist), it seems unlikely that the API is going to change. > > So how about bumping the version to 1.00 sometime soon, to signify "stable > interface" and stable implementation? > > Neil >

Mon Mar 27 12:47:37 2017 The RT System itself - Status changed from 'new' to 'open'

Mon Mar 27 19:13:02 2017 NEILB [...] cpan.org - Correspondence added

I start at 0.01 and increment on release, but for 0.* I'm mentally thinking that the interface is unstable. If I'm really thinking it's likely to change, I'll document it, but in general I think that 0.* means it could change, and a transition to 1.* signifies a stabilisation of the interface. I've seen this with a number of dists. The one that came to mind was Type-Tiny, which has an explicit stability policy: https://metacpan.org/pod/distribution/Type-Tiny/lib/Type/Tiny/Manual/Policies.pod#STABILITY Also see its Changes: https://metacpan.org/changes/distribution/Type-Tiny Periodically I look at (some of) my dists and think "am I confident enough to change this to 1.x yet?" But maybe this is one of those situations where I go "oh, so it's just me (and a small number of others), and not in fact everyone else who thinks this?" :-)

Mon Mar 27 20:01:09 2017 ether [...] cpan.org - Correspondence added

On 2017-03-27 16:13:02, NEILB wrote: Show quoted text

> But maybe this is one of those situations where I go "oh, so it's just > me (and a small number of others), and not in fact everyone else who > thinks this?" :-)

Probably :)