3.27.90 tarball deadline extended
Hi developers, TL;DR: the 3.27.90 tarball deadline is extended until next Monday The release team is still learning how to get by in a BuildStream world. It turns out that nobody who is currently available knows how to generate release tarballs using BuildStream. Many developers, notably Tristan, are traveling from FOSDEM and unavailable at the moment. I've been discussing with Javier, and we're both kind of lost as to what to do. If you've already released a tarball, you must have done so either using host dependencies, which doesn't work for modules that depend on new stuff, or with JHBuild. We think it's important to actually be able to release all modules without using JHBuild, and we'll need a couple days to figure this out, and you all surely deserve at least one weekend after that before tarballs are due, so let's extend the 3.27.90 tarball deadline until at least next Monday. Expect more development schedule change announcements as we figure out what we're doing. Thanks for your patience throughout this big transition, Michael -- devel-announce-list mailing list devel-announce-list@gnome.org https://mail.gnome.org/mailman/listinfo/devel-announce-list
Freezes begin today
Hi all, Despite the release schedule change, we're now quite close to the final 3.28.0 release, so to ensure quality we should begin all the freezes as previously-scheduled. That means UI freeze, feature freeze, API/ABI freeze for libraries, and the string change announcement period all begin tonight. Thanks for helping to make GNOME 3.28 stable and reliable, Michael -- devel-announce-list mailing list devel-announce-list@gnome.org https://mail.gnome.org/mailman/listinfo/devel-announce-list
Re: 3.27.90 tarball deadline extended
On Mon, Feb 5, 2018 at 11:59 AM, mcatanz...@gnome.org wrote: The release team is still learning how to get by in a BuildStream world. It turns out that nobody who is currently available knows how to generate release tarballs using BuildStream. Hi developers, An update on this. With some help from Mathieu and Jürg, we've figured out how to generate tarballs. You need to use a combination of `bst workspace open` and `bst shell --build`. Then once you enter the bst shell, you can generate a tarball normally (mkdir build; cd build; meson ..; ninja; ninja dist) and it will be generated in the workspace. This is actually pretty simple; I had gotten confused earlier today because I had forgotten the --build flag to `bst shell`. Unfortunately, I discovered a bug that's a blocker for Epiphany [1], so it might not work for you in practice. We'll evaluate later this week whether we'll need to recommend switching back to JHBuild to generate tarballs for the time being, or whether we can get this working reliably. Thanks for your patience, Michael [1] https://gitlab.com/BuildStream/buildstream/issues/232 -- devel-announce-list mailing list devel-announce-list@gnome.org https://mail.gnome.org/mailman/listinfo/devel-announce-list
