On Thu, 2019-09-12 at 19:14 +0100, Emmanuele Bassi wrote: > On Thu, 12 Sep, 2019 at 19:08, Philip Withnall < > phi...@tecnocode.co.uk> wrote: > > That sounds like something people are going to forget to do. Would > > it be possible to use computers to automate this? > > It's software: anything is possible. > > As to whether we can automate this **right now**, the answer is: no. > > I'm not going to block on a feature that may or may not appear in > Gitlab's enterprise edition and then may or may not be backported to > the community edition we have. Of course, enterprising hackers are > strongly encouraged to work on that.
The link to the GitLab EE issue was illustrative, not definitive. If it solves the problem, a cronjob which polls every module’s `/meson.build` and `/meson_options.txt` files every 30 minutes and uses sendmail to send you an e-mail about changes would work. > From my perspective, I don't think is much to ask to the community of > GNOME maintainers to help us on the release team (and all the people > that build GNOME components) in ensuring their projects actually > build instead of deploying hopes and prayers to users. I don’t think anyone is going to begrudge you their time, it’s just the practicality of having ~30 humans remember to send an e-mail to a list every time they (infrequently and rarely) touch a particular part of their code base. I will endeavour to remember to do so, but I can pretty much guarantee I’ll forget at some point. I apologise in advance. Philip
_______________________________________________ desktop-devel-list mailing list email@example.com https://mail.gnome.org/mailman/listinfo/desktop-devel-list