GTK Support For macOS Potentially Moving Back To "Best Effort" Approach
The GTK toolkit and GLib support for Apple's macOS may be taking a back-seat to other platforms moving forward and would fall into a "best effort" category.
GNOME developers are looking at potentially retiring their macOS continuous integration (CI) builder for GLib and GTK. Besides the CI hardware getting old, the CI maintainers aren't too experienced with macOS while the GTK/GLib developers aren't particularly interested or familiar with macOS development either. No one in the open-source community has consistently stepped up to deal with these GNOME projects on macOS and ensure that any CI issues are addressed for macOS.
Barring any volunteers from stepping up and deal with any macOS-specific regressions, the macOS CI builder may be phased out and in turn the GTK/GLib macOS support moving "back to being best effort" and rely on downstream packers and consumers to test changes.
More details on this possible shift around GLib/GTK macOS support can be found via this GNOME Discourse thread.
GNOME developers are looking at potentially retiring their macOS continuous integration (CI) builder for GLib and GTK. Besides the CI hardware getting old, the CI maintainers aren't too experienced with macOS while the GTK/GLib developers aren't particularly interested or familiar with macOS development either. No one in the open-source community has consistently stepped up to deal with these GNOME projects on macOS and ensure that any CI issues are addressed for macOS.
Barring any volunteers from stepping up and deal with any macOS-specific regressions, the macOS CI builder may be phased out and in turn the GTK/GLib macOS support moving "back to being best effort" and rely on downstream packers and consumers to test changes.
More details on this possible shift around GLib/GTK macOS support can be found via this GNOME Discourse thread.
34 Comments