Bug 24814
| Summary: | WebKit should expose some sort of revision number | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | darin, fishd, mjs, mrowe |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
Eric Seidel (no email)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Darin Adler
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".