• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Item6064: Harmonize Most Recent Version and Installed Version of Find More Extensions in configure

Item Form Data

AppliesTo: Component: Priority: CurrentState: WaitingFor: TargetRelease ReleasedIn
Engine configure Low New   n/a  

Edit Form Data

Summary:
Reported By:
Codebase:
Applies To:
Component:
Priority:
Current State:
Waiting For:
Target Release:
Released In:
 

Detail

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? wink

-- 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 frown

-- TWiki:Main.SvenDowideit - 18 Oct 2008

ItemTemplate
Summary Harmonize Most Recent Version and Installed Version of Find More Extensions in configure
ReportedBy TWiki:Main.FranzJosefGigler
Codebase 4.2.2
SVN Range TWiki-5.0.0, Sun, 05 Oct 2008, build 17588
AppliesTo Engine
Component configure
Priority Low
CurrentState New
WaitingFor

Checkins

TargetRelease n/a
ReleasedIn

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2008-10-18 - SvenDowideit
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback