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. > On Oct 22, 2022, at 10:31 AM, Darin Adler via webkit-dev > <webkit-dev@lists.webkit.org> wrote: > > Hi folks. > > I understand it can be super critical to understand what version someone was > testing when reporting a WebKit bug. But I, at least, haven’t found the > version field at bugs.webkit.org useful in the 20+ years I have been working > on this project. > > Now we have that same noise in GitHub. All my pull requests have the label > WebKit Nightly Build on them when I use the “git webkit pr” command to create > them. And we have lots of labels with various version numbers, such as > “Safari 8” and “417.x". > > Can we just get rid of all this? Is there anyone who’s finding these labels > useful in GitHub? > > I suggest we remove these labels from the project. No objections to leaving > the version field in bugs.webkit.org for the time being, but eventually I > think we should probably get rid of that too. > > — Darin > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
