public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: Nirbheek Chauhan <nirbheek@gentoo.org>
Cc: Rich Freeman <rich0@gentoo.org>,
	Gentoo Dev <gentoo-dev@lists.gentoo.org>,
	pr@gentoo.org,  gnome <gnome@gentoo.org>
Subject: [gentoo-dev] Re: RFC: Gentoo News file about GNOME 3.2's unmasking
Date: Sat, 26 Nov 2011 09:35:36 -0500	[thread overview]
Message-ID: <CAL0O3aMLMqw6D8NZU53cSWzsJyw3UFKqVcXLUFEycP-ezNdpYQ@mail.gmail.com> (raw)
In-Reply-To: <CADqQcK4WxZ56HUTpVcjbhAgp8sUDV5oCrBXKPwqhnL=_WfUPgw@mail.gmail.com>

On Sat, Nov 26, 2011 at 7:56 AM, Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> On Sat, Nov 26, 2011 at 5:56 PM, Rich Freeman <rich0@gentoo.org> wrote:
>> On Sat, Nov 26, 2011 at 2:13 AM, Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
>>> Since GNOME 3 is already in the
>>> tree, and the news file content is straightforward, I'd like to commit
>>> this in 24hrs if there are no problems.
>>
>> If we're gong to go to all the trouble to create upgrade guides and
>> news/etc, wouldn't it make sense to send out the news item a few days
>> BEFORE making the change?
>>
>
> That was indeed the intention, but there was a miscommunication.

On my part, it was a failure of imagination. I had always seen large
changes dumped in ~arch with no warning or documentation (even the
png15 upgrade didn't get a news item until libpng-1.5.x went stable),
and so unquestioningly came to assume that it's the way things are
done because that's the way things were always done. Then some hours
after gnome-3 was unmasked, I saw Nirbheek talking on IRC about making
a news item, and winced: of course! why didn't I think of that? As an
~arch user, I had not particularly enjoyed massive changes being
dumped on my head without warning, so now that I was a developer and
it was in my power to write news items, why didn't I think of writing
one before unmasking?

-Alexandre



  parent reply	other threads:[~2011-11-26 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26  7:13 [gentoo-dev] RFC: Gentoo News file about GNOME 3.2's unmasking Nirbheek Chauhan
2011-11-26 12:26 ` [gentoo-dev] " Rich Freeman
2011-11-26 12:56   ` Nirbheek Chauhan
2011-11-26 13:23     ` Rich Freeman
2011-11-26 14:35     ` Alexandre Rostovtsev [this message]
2011-11-26 15:14       ` Rich Freeman
2011-11-26 18:21 ` [gentoo-dev] " Mart Raudsepp
2011-11-26 18:55   ` Nirbheek Chauhan
2011-11-26 20:06     ` Zac Medico
2011-11-27  7:25       ` Nirbheek Chauhan
2011-11-27 18:55         ` Zac Medico

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL0O3aMLMqw6D8NZU53cSWzsJyw3UFKqVcXLUFEycP-ezNdpYQ@mail.gmail.com \
    --to=tetromino@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gnome@gentoo.org \
    --cc=nirbheek@gentoo.org \
    --cc=pr@gentoo.org \
    --cc=rich0@gentoo.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