Last modified: 2012-12-23 22:57:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45354, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43354 - [Enhancement] SpecialVersion.php: version info: in addition to SHA hashes, please show also the date (perhaps more info)
[Enhancement] SpecialVersion.php: version info: in addition to SHA hashes, pl...
Status: RESOLVED DUPLICATE of bug 38783
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.21.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Dereckson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-22 20:17 UTC by T. Gries
Modified: 2012-12-23 22:57 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description T. Gries 2012-12-22 20:17:30 UTC
I always have difficulties to quickly identify the current versions of core and extensions (quickly= without following the linked hash to gerrit and to look there for the commit date)


Hereby I suggest:

- to use in https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob_plain;f=includes/specials/SpecialVersion.php;hb=master a different git log command
- with the goal to list not only the SHA hashes, but at least also the date, and perhaps also the ref name.


 git log --pretty=format:"%h %ai" -n 1

resulting in something like

 a441912 2012-06-16 18:04:43 +0000

or 

 git log --pretty=format:"%d %h [%ai]" -n 1

 (HEAD, origin/master, origin/HEAD, master) a441912 2012-06-16 18:04:43 +0000
Comment 1 Dereckson 2012-12-23 04:03:50 UTC
Thank you for your bug report.

Looking Special:Version following it, I noted our credits list weren't up to date. Gerrit change #40079 solves that.

A column date (YYYY-MM-DD) seems the most convenient solution, but there is already several columns and the description column width is already rather small in 1280x1024.

I don't think hour or branch is really relevant.

So I offer to put the date in the second column.

That would give for example for ParserFunctions:

ParserFunctions (Version 1.4.1)

(8d2534b)
2012-12-22

Enhance parser with logical functions

Tim Starling, Robert Rohde, Ross McClure and Juraj Simlovic
Comment 2 T. Gries 2012-12-23 08:54:41 UTC
Thank you.

As a space-saving alternative, the date could be written in a second _row_, I mean a column layout such as

 hash<br/>
 date

for core, an for extensions table in SpecialVersion.
Comment 3 Dereckson 2012-12-23 22:51:57 UTC
Yes, this is what I wanted to convey as presentation. Read the Comment 1 as "a blank line = column separator".
Comment 4 Dereckson 2012-12-23 22:57:05 UTC
It seems this topic has been previously discussed. This is bug 38783.

*** This bug has been marked as a duplicate of bug 38783 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links