Item12583: revert to simple floats in $VERSION

This breaks updating plugins on RHEL and SLES which ship an incompatible version.pm

use version; our $VERSION = version->declare("v1.2.0");

Instead, I'll use:

our $VERSION = '1.20';
our $RELEASE = '1.20';

... simple and compatible.

See also Item12225 and Development.ConvertToModernPerlVersionStrings

I'll take care of plugins that I maintain at first. These are:

1. CaptchaPlugin
2. DBCacheContrib
3. DBCachePlugin
4. EditChapterPlugin
5. FlexFormPlugin
6. ImagePlugin
7. JSTreeContrib
8. JQTwistyContrib
9. JQueryPlugin
10. JsonRpcContrib
11. MetaCommentPlugin
12. MoreFormfieldsPlugin
13. NatEditPlugin
14. PiwikPlugin
15. SetVariablePlugin
16. SolrPlugin
17. SqlPlugin
18. TrashPlugin
19. UpdatesPlugin
20. VirtualHostingContrib

Other plugins affected and in danger of breaking during an update are:

1. AutoViewTemplatePlugin
2. BuildContrib
3. CommentPlugin
4. CompareRevisionsAddonPlugin
5. EditRowPlugin
6. EmptyContrib
7. EmptyPlugin
8. FamFamFamContrib
9. HistoryPlugin
10. HomePagePlugin
11. InterwikiPlugin
12. JEditableContrib
13. JQueryPlugin
14. JSCalendarContrib
15. MailerContrib
16. PatternSkin
17. PreferencesPlugin
18. PublishPlugin
19. RenderListPlugin
20. SpreadSheetPlugin
21. SubscribePlugin
22. TablePlugin
23. TinyMCEPlugin
24. TopicUserMappingContrib
25. TWikiCompatibilityPlugin
26. TwistyPlugin
27. UnitTestContrib
28. WysiwygPlugin

Just to name those in common use (add more if you find a use version ...->declare( in them.)

-- MichaelDaum - 12 Sep 2013

The solution is to install the latest CPAN:version. Any perl >= 5.10.1 will have the correct version. It's quite simple to install the latest version, and it ensures we'll be compatible with new perl going forward.

-- GeorgeClark - 23 Oct 2013

Sure this is a solution ... after having upgraded and seeing their Foswiki going down in flames. Not good.

This happens on current RHEL and SLES. Distrowatch says the situation is not going to get better any time soon. I hope they are wrong.

What do people next? Of course they revert the upgrade. Some fearless soles might google for the error, find 100s other hate messages about failing plugin updates ... and one search hit is about their very own upgrade guide that they didn't read in the first place (they never do).

So we HAVE to paddle backwards OR ship a working version.pm with upcoming Foswikies ... which of course won't mitigate the situation for people running Foswiki < 1.1.9 yet still in need of plugin upgrades.

-- MichaelDaum - 23 Oct 2013

Commenting is disabled while not logged in