Mail Archives: cygwin-apps/2001/12/20/14:09:39
On Thu, Dec 20, 2001 at 07:38:39AM -0500, Earnie Boyd wrote:
>Corinna Vinschen wrote:
>>
>> On Thu, Dec 20, 2001 at 08:53:30PM +1100, Robert Collins wrote:
>> > Ok, I bit. Step 5:
>> >
>> > 5. Create setup.hint file following the documentation on this web page.
>> > For new packages the first upload MUST be tagged as experimental. Once
>> > the package has no major bug reports from the users, then a current
>> > package may be introduced
>>
>> I hate that. Quote from a few lines above the `setup.hint' section:
>>
>> Test versions are specified via the setup.hint file as described
>> below. It is not required that your package have a test version.
>> Use of a test version of a package is at the discretion of the
>> package maintainer.
>>
>> And how long does it take to wait for "major bug reports from the users"?
>> 1 day? A week? A month?
>>
>> Not amused,
>> Corinna
>
>Nor, am I amused. If it must be tagged I'd rather see the tag NEW
>instead, unless the maintainer believes that it's actually an
>experimental version.
I think I've already given my opinion on this, too. I don't see any
reason for a new package to be marked "Test". What's the gain? It
will just result in the package getting almost no exposure.
What extra information will be gained by making it "Test"? Will the
new user be more forgiving? More apt to report bugs? I don't get
it.
I thought the intent of Test was to have a version of a product for
people to try while still providing a safety net of a "stable" version
to fall back to.
I don't see how that applies to the first release of a new package.
cgf
- Raw text -