Mail Archives: cygwin-apps/2001/12/21/00:07:39
On Fri, Dec 21, 2001 at 03:27:33PM +1100, Robert Collins wrote:
>----- Original Message -----
>From: "Christopher Faylor" <cgf AT redhat DOT com>
>>I don't see how that applies to the first release of a new package.
>
>I'd call it pretty basic risk management. If the package doesn't cause
>any havoc, then put it in current really quickly. I'm just nervous
>with the concept that any new package go directly into curr.
But, I still don't understand what you expect to happen. Do you think
that a non-adventurous person would be interested in the package but
would pass on it because it says "Test" and would therefore potentially
be saved from disaster?
Or, conversely, are you expecting that there is a group of people who
would be interested in downloading Test versions and providing useful
feedback for first time package providers?
I just think of this as "It's a new package. Since it's brand new, it
could have bugs". If you want people to try the package then don't put
any barriers in the path of downloading it.
Maybe if this was the first release of a disk optimization tool or
something, I could see a need to be very careful. But, so far this
discussion has been wrt a program which generates large characters and a
program which converts between various systems of units.
The *only* thing I can think of that would require care with packages
like these would be to ensure that they didn't overwrite other parts
of cygwin's installation. I can see that becoming more of an issue
as time progresses. But, that's something that should be handled in
software, not by end-users downloading test versions.
Btw, I think Earnie's idea of having a *New!* category is actually a
good one. I have been meaning to implement something like that for the
web package lister, in fact.
cgf
- Raw text -