Re: A prescription for release anxiety
On Fri, 17 May 2002, Ben Armstrong wrote:
>
> By now it is pretty clear to everyone that each time we make a release, it
> is a painful process. Broadcasting that pain doesn't do us any good, and it
> doesn't do the public any good. By analogy, do you *really* want to see a
> graphic live video feed of Aunt Jane's labour and delivery, or would you
> rather just wait for the birth announcement? The only truly significant
> piece of information worth reporting will be when Debian finally releases.
>
I must confess your analogy is apt! Yes, I probably wouldn't want to hear
all the details. It is probably better for people to discern difficulties
from the bug list.
> As for your proposed summary of debianplanet, we have no say over how we are
> represented on debianplanet.org or other news sources, so I don't think
> either copying their material verbatim or linking to it is appropriate. Let
> them say what they say (which will almost certainly be tainted by whatever
> editorial spin they put on it) and leave it at that. People can (and do!)
> watch the soap opera there unfold, kibbitz, and so forth, while the
> developers go about their business making the release ready the best way
> they know how, unhampered (I hope) by the inevitable stream of armchair
> criticism that accompanies every release. These are the anxious friends and
> family waiting in the lobby. While I understand and sympathize with their
> anxiety, I am thankful that they remain in the lobby until we can all
> finally celebrate the much-anticipated joyous event.
>
> > Clearly anyone ALREADY
> > familiar with debian will be well-aware of the release status however
> > the average user or newcomer will not grasp the signficance of
> > the phrases 'Release-critical bugs' etc or will S/he be likely to
> > click on debian-devel-announce mailing list.
>
> Why on earth not? What could be clearer than:
>
> "In addition, general status reports are posted by the
> release manager to the debian-devel-announce mailing list."
>
> That *invites* people to click on the list, and once there, it isn't
> terribly difficult to grok "Release Status Update" posts, even if you aren't
> an incredibly technically gifted person. Point - click - read. Anthony has
> a good "bedside manner". He writes in a very pleasant, precise style that,
> while aimed at developers, should at least convey to the layperson the sense
> that "what do you know, they are actually working on it and are following
> an actual plan".
Yes, upon further mulling.... it is better to merely point people to a general list. The question I
have is: does release-critical bugs have to be 0 before a release occurs. Clearly
at some point it is decided that they are not show stoppers this is not
an absolute requirement or so I have gathered from various discussions...
I agree that the release manager is quite adept at conveying his views ;-)
-walter
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: