Item1797: Default plugins have their version updated when new releases are built - even when they should not be

The plugins that are shipped with Foswiki AND have the %$VERSION% in the plugin topic have their version updated each time we build.

The result is that I have to spend hours reuploading plugins to foswiki.org to avoid a mismatch between the distrubuted and the one on foswiki.org

The problem can be resolved easily. Remove the dammed %$VERSION% from the Plugin version field.

It is a major mistake that people think this automatic stuff is smart. it is not.

The change history needs to be manually updated anyway.

Also for non-default plugins the %$VERSION% is bad practice as SVN numbers are often not in sequence when a developer creates a branch for specific purpose and then merge back.

What people do with their plugins is their business. But keeping the configuration management working for the releases and default plugins is MY business and creates problems and extra work for me. So I will once and for all remove the %$VERSION% from the default plugins in trunk one at a time.

-- KennethLavrsen - 03 Jul 2009

Well, perhaps these plugings should not get updated version numbers when FW is built.

-- ArthurClemens - 14 Sep 2009

They only get that now if the plugin file was touched.

We still have a problem in trunk where the plugins uploaded to Foswiki no longer has a date in the release field.

This makes them appear in configure when installed with only their SVN checkin number and no date. BAD. There is a bug item for this.

This is because the change done in plugin format will not be visible until we get to 1.1.

We should make BuildContrib revert to putting SVN number (iso date) in the field. It will work better now and be OK also in 1.1

-- KennethLavrsen - 14 Sep 2009