Bug 24814 - WebKit should expose some sort of revision number
Summary: WebKit should expose some sort of revision number
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 13:34 PDT by Eric Seidel (no email)
Modified: 2017-07-18 08:29 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2009-03-25 13:34:35 PDT
WebKit should expose some sort of revision number

Chromium is currently misusing the webkit revision numbers (like 528.0), shipping multiple versions of WebKit with the same revision number.

WebKit has no releases.  So there really isn't a version number I can suggest for Chromium to use.  (Apple maintains the 520.x numbers for their own internal build trains).

One simple solution would be to expose a webkit svn revision number, or build date off of window.navigator.

I'm partial to the svn revision number.  The only problem with that is when we eventually switch to a new version control system which is not monotonically increasing.
Comment 1 Darin Adler 2009-03-25 13:39:09 PDT
An svn revision number would not work. Apple uses branches and revision numbers are not monotonically increasing.

I think what we need is a way to bump the existing WebKit revision number at the right time, when someone ships a release. There's absolutely no reason to reuse the same number. You can always bump the "low digit".