News for hackers. Stuff that matters.
Re:GNOME 44 by HeckFeck on Thursday March 23, 2023 @06:33AM (#35272580)
I am looking forward to the days when we ditch memorable release versions and just use the git commit hash to identify a release.
Re:GNOME 44 by rolisz on Thursday March 23, 2023 @06:36AM (#35272602)
Why? There is value in having some sort of easily identifiable ordering to versions
Re:GNOME 44 by HeckFeck on Thursday March 23, 2023 @07:27AM (#35273058)
Absolutely. I was being sarcastic. I'm not fond of this rabid incrementation that originated with Chrome.
Re:GNOME 44 by tuyiown on Thursday March 23, 2023 @06:35AM (#35272594)
dates. dates are good. YYYY.MM.patch.
Re:GNOME 44 by favadi on Thursday March 23, 2023 @06:53AM (#35272741)
Why would anyone want to use Ubuntu 4ee7bb27a0ff1cbc203a0df93919980ccbcfd4f1 over Ubuntu 22.04?
Re:GNOME 44 by Maken on Thursday March 23, 2023 @07:13AM (#35272931)
You should work for Asus.
Re:GNOME 44 by zorr on Thursday March 23, 2023 @07:32AM (#35273096)
How would that work for deprecations and new API introductions? GNOME is built on top of glib/gobject/gtk and a host of other libraries which all have to be ABI-compatible in some way. And GNOME itself is used as a base platform for applications.

Having a predictable versioning scheme helps limit the number of releases for downstream application maintenance work. You can't expect applications to have the full git tree available at build or runtime to make some features conditionally available.