Just grab the previous stable tarball, unroll it, change the version to
a higher one, and release. If it's a bitch to backout that one path,
backout the entire stable release to the previous one.
Did you see the number of bug fixes between 0.60 and 0.61? No, I'm not
rolling back the entire release.
I did see the number. And yet 11 days ago 1000 other CPAN modules worked
fine and it wasn't a huge problem they were only in a devel release, and
now many of them will be broken, and they are going to stay broken.
Regressing those bugs for a short time pales in comparison to the
problems our our current situation.
Just upgrading TB::Tester isn't going to be enough, because then it
needs to be forced to upgrade everywhere, which means we actually have
to change 27 distributions.
And in the mean time CPAN is badly broken.
Unless you are suggesting I...
a) Go fix someone elses testing module
b) Take upload permissions by force
c) Upload their package.
d) Contact the authors of all 26 modules
e) Get them to increment and release
f) Go increment all the ones I can't contact for them
g) Take upload permissions by force from all 26 - $responsive
h) Upload ALL of those packages
... I don't see any other way to fix a badly broken CPAN and fix it today.
Or you can roll back some bug fixes that have only been visible to the
world for 10 days, until we can do a more fine-grained backout, and then
deal with the larger situation.
If you have any other alternatives to fix CPAN _today_, I'd like to hear
them.
Adam K
