Page MenuHomePhabricator

Unify svn-revision references in Special:Version
Closed, ResolvedPublic

Description

Currently, there are two kinds of references to
revisions in the subversion repository in Special:Version

  1. with a link as (r98765) in the "MediaWiki" entry.
  2. in extension entries like (Revision r01234) without a link.

I suggest to unify them to both include links, and to use
the same message format from the MediaWiki: name space.

See also bug 18592.


Version: 1.15.x
Severity: enhancement
URL: http://translatewiki.net/wiki/Special:Version?uselang=ksh

Details

Reference
bz18593

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:31 PM
bzimport set Reference to bz18593.
bzimport added a subscriber: Unknown Object (MLST).

Partly reverted the external link on the revision number in r49950.
The viewvc link can be browsed by clicking the link on the
MediaWiki website's extension description page.

This was partially reverted in r49950 apparently on the basis that it looks funny. :)

More seriously, it has some real problems:

  • Hardcoded Wikimedia SVN URL means that extensions checked out from a third-party SVN will be totally wrong
  • Hardcoded trunk path means that extensions checked out from branch will link to the totally wrong place
  • Hardcoded path points just to 'extensions' and fails to specify the particular directory

You should be able to extract the actual source path out of the .svn files just like the version, in which case we can identify whether it's our own SVN and we can stick a pretty viewvc link on it -- with the correct path.

Hopefully whis was fixed on r49995.

  • The link will follows which type of the script is downloaded, either trunk, branches and tags.
  • The link on the extension field is only available if it is obtained from the WMF server, other third-party extension links will be disabled and only showing the revision number.
  • The link will follows the path with which extensions is installed. For example CheckUser extension will go to the CheckUser extension, etc.