Hello! Clément Lassieur <clem...@lassieur.org> skribis:
> I think we need https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30602 to > be fixed. Done. \o/ With Guile 2.2.4 now released, we can go ahead with 0.15. Could people build the ISO installation image and give it a try: guix system disk-image --file-system-type=iso9660 gnu/system/install.scm and then boot the resulting image (you can do that in QEMU if you prefer), and follow the instructions. Likewise, tests of the binary Guix tarball would be welcome. You can build it with: make guix-binary.x86_64-linux.tar.xz For the record, some of the items Ricardo listed are not entirely addressed either (quoting Ricardo’s previous message): * Outstanding patches. There are many patches in the queue at guix-patches[1] that we should go through, comment on, and/or apply before the release. Who would like to join a task force to do that together? Let’s pick 5 patches each and review them so that we can either comment to ask for changes or to apply them. [1]: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches * breakage since the last core-updates merge. Since the long overdue merge of the “core-updates” branch we have a few serious problems on i686 (e.g. the gst-plugins-base package) and armhf. Who would like to lead an effort to investigate and fix these problems? (Note: you obviously don’t need to fix them yourself, just keep track of these things and coordinate with others who investigate them.) * collecting new features and big changes in NEWS. The NEWS file already lists some of the changes that the next release would provide compared to 0.14.0, but we all know that there are more. Who would like to take charge of the NEWS file? This involves asking people for changes they would really like to be mentioned and coordinating with other volunteers to search through all commits since v0.14.0 to find noteworthy changes. If we all focus on this, we could release by the end of the week or beginning of next week. Let’s do that! :-) Ludo’.