Skip Menu |
 
rt.cpan.org will be shut down on March 1st, 2021.

This queue is for tickets about the JSON-XS CPAN distribution.

Report information
The Basics
Id: 128571
Status: new
Priority: 0/
Queue: JSON-XS

People
Owner: Nobody in particular
Requestors: WATERKIP [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Please release 3.04 as 4.01 and use X.Y_Z notation for trial releases
Download (untitled) / with headers
text/plain 1.1k
Hi, Thank you for making JSON::XS, we use it at work for our project! But during the last recreation of our Docker image I came across an issue that could have been prevented by using the X.Y_Z notation to make trial releases[1][2]. Everyone installing JSON::XS from the command line (with `cpanm JSON::XS`) will install the latest version and since you declared it a trial release I think you should have named is 4.0_1. This way your consumers don't automatically update to the trial release unless they ask for it. I had a fun couple of hours looking at this issue because a new build of a Docker image pulled the latest (un)stable version of JSON::XS and we encountered a bug. Now I can work around it by setting `requires 'JSON::XS' => '<=3.04';` in the cpanfile, but then I need to manually check if you update 4.0 or make more changes to the 3.x-release. Could you make a 4.01 release based on 3.04 so your consumers will always install a stable version? Cheers, Wesley [1]: http://blogs.perl.org/users/oliver_gorwits/2011/10/releasing-trialdevbeta-versions-with-distzilla.html [2]: http://blogs.perl.org/users/grinnz/2018/04/a-guide-to-versions-in-perl.html


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.