From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#22687: Online manual not updated automatically Date: Sun, 21 Feb 2016 23:41:04 +0100 Message-ID: <87twl1r8jj.fsf@gnu.org> References: <20160215215024.GA22646@jasmine> <20160216162504.GC5914@solar> <20160216164218.GB5983@solar> <56C3590B.7060701@gmx.net> <8737sss86a.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40668) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXchZ-0006Co-Q4 for bug-guix@gnu.org; Sun, 21 Feb 2016 17:42:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXchW-0007f7-KD for bug-guix@gnu.org; Sun, 21 Feb 2016 17:42:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:39530) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXchW-0007f3-GE for bug-guix@gnu.org; Sun, 21 Feb 2016 17:42:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aXchW-00081C-8j for bug-guix@gnu.org; Sun, 21 Feb 2016 17:42:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8737sss86a.fsf@gnu.org> (Mathieu Lirzin's message of "Tue, 16 Feb 2016 21:37:49 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Mathieu Lirzin Cc: 22687@debbugs.gnu.org Mathieu Lirzin skribis: > Florian Paul Schmidt writes: > >> On 16.02.2016 17:42, Andreas Enge wrote: >>> On Tue, Feb 16, 2016 at 05:33:27PM +0100, Ricardo Wurmus wrote: >>>> I was not courageous enough to suggest that, but this does sound >>>> like a good idea. >>>=20 >>> It is easy enough to have that courage when one is not the person >>> making the releases :-) >> >> Hmm, shouldn't that process be mostly automated? And if not, maybe >> it's worth thinking about how to do that. I guess from a functional >> point of view a release is just a function that takes a revision and >> has as its outputs installer images, binary installers, a new website, >> yada yada yada.. > > IIUC The problem is that making a release involves a lot a build power > that take long long time and makes it difficult to resolve unavoidable > issues encountered during the process. > > I remember hearing Ludo explaining that the release process for Guix was > more involving than for the other software projects he experienced. Yeah it typically takes a lot of time waiting for builds and uploads to complete. See =E2=80=98release.org=E2=80=99 in guix-maintenance.git for a = feel. If people have ideas on how to improve the process, I=E2=80=99m all ears! = :-) Ludo=E2=80=99.