Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 8 Sep 2005 09:47:07 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: About Cygwin announcements
Message-ID: <20050908134707.GA4965@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20050908072916 DOT GZ5555 AT calimero DOT vinschen DOT de> <20050908081215 DOT 6C12683D23 AT pessard DOT research DOT canon DOT com DOT au> <20050908083951 DOT GB5555 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0509080913450 DOT 11417 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0509080913450.11417@slinky.cs.nyu.edu>
User-Agent: Mutt/1.5.8i

On Thu, Sep 08, 2005 at 09:21:33AM -0400, Igor Pechtchanski wrote:
>While I agree with everything Corinnal posted above, there was an
>alternative approach: for a bit, someone was following announcements
>that forgot to describe the package with a description message.  If
>this is done properly (i.e., for all affected package announcements,
>with threading kept, and all of the missing information and "cool new
>features" concentrated in one message), this could be a useful service
>to the Cygwin community and a gentle reminder to the package
>maintainers.  But, as Corinna said, <http://cygwin.com/acronyms/#SHTDI>
>(and it's a thankless, flame-prone job that requires real dedication
>:-D).

I found the "product descriptions" which follow the announcements to be
an annoyance, actually.  I'd prefer just finding descriptions of
products at a static location like the cygwin web site.  Perhaps someday
the http://cygwin.com/packages/ will have more detailed information.

OTOH, it's probably no surprise that I'm in Corinna's camp wrt release
documentation.  Given that announcements are always going to rely on the
gumption of the person doing the announcing, you can never be 100%
assured that they have covered all of the new and exciting improvements.
This was also true of product updates at Red Hat, FWIW.

What that means is, that if you are managing an implementation of Cygwin
it pays to spend some time educating yourself about what you're using and
adopting an update discipline that makes sense for your organization.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/