Priority: Low
Current State: No Action Required
Released In:
Target Release: n/a
Applies To: Engine
Component: configure
Branches:
Where do the two columns
Most Recent Version and
Installed Version get their data from? They are sometimes different although the same (latest) version of an extension is installed.
- Can this be somehow harmonized?
- Or can the Action column be made more intelligent so that it doesn't show Upgrade if the versions match already?
- Is it planned to implement a batch install/upgrade feature? (checkboxes marking several extensions that shall be installed/upgraded in a batch)
- Shall I create further feature request topics on codev?
--
TWiki:Main/FranzJosefGigler - 13 Oct 2008
The problem is that people use different standards for the release version.
I tried to change some of the defaults from the very little usefull SVN number and to a more standard major.minor version scheme.
I for sure prefer that a release version follows the somewhat intelligent version scheme that tells me if someone has really changed or it is just a minor little thing. And I also want to see a date. The SVN checkin numbers say very little. They are easy to apply (automatic) for the latest version but we see all the time that people forget to update the change history. People put too little emphasis on change histories and proper version control. It tell me a lot to know the exact changes done, the version number and the date. I do not know how many times I have updated a default plugin to discover that the only thing that changed is an automated SVN checkin number that changes each time TWiki is released.
So I would like to see a version number either like 1.2.3 or 1.2 + a date made standard where the configure script looks for the version string.
--
TWiki:Main.KennethLavrsen - 13 Oct 2008
it would be nice, but you
have to guard against someone uploading a new version and forgetting to change the version number. (its happened many times). We do this using the svn rev number atm. the topic or attachment upload date&time would be even safer, but that will not be embedded in the topics installed on the user's system.
It needs to be a numbering system that does not rely on people remembering to do the right thing
--
TWiki:Main.SvenDowideit - 18 Oct 2008
Followed up by
Item1198