> On Oct 22, 2022, at 12:11 PM, Caitlin Potter <ca...@igalia.com> wrote:
> Would it make sense to, rather than referring to downstream browsers, have a 
> canonical WebKit version number that could be exposed in about:version or 
> something? A friendly semver-ish thing + short git hash could be a lot more 
> useful for doing things like bisecting.
> I think part of the reason the version numbers havent been useful is they are 
> very detached from the actual open source product, and don't necessarily help 
> with triage or reproduction, or hint at a cause.

I personally am not looking to add something. I’d rather remove the thing we 
currently have that is not useful. I am definitely open to adding something 
later if we come up with something great.

It’s not clear how easy it would be to improve things by adding more than the 
git hashes and the commit.webkit.org increasing numbers we already have. On 
Apple’s platforms there are already both  Safari version numbers and WebKit 
version numbers and it’s not clear where an additional WebKit open source 
reference version number would go, and how to best express the effects of 

— Darin
webkit-dev mailing list

Reply via email to