Mailing-List: contact httpcomponents-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <httpcomponents-dev@jakarta.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <47178F76.7060404@dubioso.net>
Date: Thu, 18 Oct 2007 18:53:10 +0200
From: Roland Weber <ossfwot@dubioso.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.6) Gecko/20070807 SeaMonkey/1.1.4
MIME-Version: 1.0
To: HttpComponents Project <httpcomponents-dev@jakarta.apache.org>
Subject: Re: release labels
References: <47122F30.4020401@dubioso.net>
 <7E075CAF-1967-4689-A31F-B6B2527B2512@codefaktor.de>
In-Reply-To: <7E075CAF-1967-4689-A31F-B6B2527B2512@codefaktor.de>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Eric,

>> It seems that our use of "Release Candidate" for something
>> between beta and final is not the intended interpretation.
> 
> Actually I believe a lot of ASF projects are using the -rcX suffix
> exactly for that purpose 

oh, good. I don't have enough of an overview to judge that.

>> a) ignore it and continue to use the label as before
>> b) find a new label between beta and final
>> c) have betas until we're final
>>
>> I'm -0 on a, but have no preference among b and c.
> 
> I see no problems with a) and c). b) is pretty confusing if there's no
> page describing the new label ;-)

;-)

> IMO the above page should be changed to clarify that the term "release
> candidate" is ambiguous and is used in several ways, e.g.:

What would be the forum to discuss changes to the general Apache pages?
That one doesn't fall into the "legal" category.

> Confusing, eh... ;-)
> 
yepp :-)

cheers,
  Roland


---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org