From: myglc2@gmail.com
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to announce important changes
Date: Wed, 20 Jun 2018 20:39:31 -0400 [thread overview]
Message-ID: <87fu1hynuk.fsf@g1.i-did-not-set--mail-host-address--so-tickle-me> (raw)
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")
Hi Ludo’,
> I agree. The patch for the new ‘guix pull’ 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’s time for an announcement mailing list, and/or blog posts.
> 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
next prev parent reply other threads:[~2018-06-21 0:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 20:24 Can't configure guix, no guile-sqlite3 Thorsten Wilms
2018-06-18 19:58 ` Ludovic Courtès
2018-06-18 20:12 ` Pierre Neidhardt
2018-06-19 10:26 ` swedebugia
2018-06-19 10:32 ` Pierre Neidhardt
2018-06-19 12:27 ` swedebugia
2018-06-19 12:32 ` Pierre Neidhardt
2018-06-20 20:41 ` How to announce important changes Ludovic Courtès
2018-06-20 22:05 ` Pierre Neidhardt
2018-06-21 0:39 ` myglc2 [this message]
2018-06-21 10:52 ` Ricardo Wurmus
2018-06-19 10:33 ` Can't configure guix, no guile-sqlite3 Thorsten Wilms
2018-07-23 19:51 ` Thorsten Wilms
2018-08-02 7:12 ` Chris Marusich
2018-08-02 11:40 ` Thorsten Wilms
2018-08-02 12:18 ` Ricardo Wurmus
2018-08-02 13:21 ` Thorsten Wilms
2018-08-19 21:31 ` Maxim Cournoyer
2018-08-23 20:03 ` Thorsten Wilms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu1hynuk.fsf@g1.i-did-not-set--mail-host-address--so-tickle-me \
--to=myglc2@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).