From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2@gmail.com Subject: Re: How to announce important changes Date: Wed, 20 Jun 2018 20:39:31 -0400 Message-ID: <87fu1hynuk.fsf@g1.i-did-not-set--mail-host-address--so-tickle-me> References: <87sh5juas9.fsf@gnu.org> <87muvrkg6k.fsf@gmail.com> <59B0BB21-3AE5-4D30-87FC-3B6439D0E88B@riseup.net> <87muvrgj78.fsf@gmail.com> <87a7rrj6t4.fsf@gmail.com> <87sh5hqjft.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]:57672) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVndT-0005s1-8b for help-guix@gnu.org; Wed, 20 Jun 2018 20:39:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVndO-00073j-Qe for help-guix@gnu.org; Wed, 20 Jun 2018 20:39:37 -0400 In-Reply-To: <87sh5hqjft.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Wed, 20 Jun 2018 22:41:58 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: help-guix Hi Ludo=E2=80=99, > I agree. The patch for the new =E2=80=98guix pull=E2=80=99 was discussed= 2-3 weeks > before being applied, and the principle was discussed even earlier than > this, but for someone not following the mailing list, I understand this > is a problem. > > Perhaps it=E2=80=99s time for an announcement mailing list, and/or blog p= osts. > What do people think? I think you did a good job of providing a "heads up" for the new 'guix pull'. From your posts it was obvious it was a significant Guix change and that there could/would be glitches. So I applied my standard "self help" for this situation: I stopped doing pulls and I am watching the lists to seen when it is safe to resume pulling changes into my systems ;-) I think the users that have had problems didn't see your posts, didn't understand what they meant, or didn't know how to respond. ISTM the best thing you could do for these users is to send an alert like "major update about to happen, hold off on updates if you are risk adverse", followed by a "coast is clear" or "workaround" alert. IMO the best way to send such alerts is a cross-post to all the existing lists. - George