commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@blueyonder.co.uk>
Subject Re: Checking Release Candidates - Wiki Page
Date Thu, 08 Dec 2005 04:17:14 GMT
I included that because Robert indicated it was required and Stephen
voted -1 in the recent Configuration release vote because of it:

http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70746.html
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70942.html

Personally I found the site unclear whether we were required to actually
"apply" for one of the free licenses or not, but if people are going to -1 a
release on that basis, seemed like a good idea to put it in the check list.
Hopefully they'll jump in and answer you properly :-)

I think the same was the case for Validator - the recent 1.2.0 release went
out with it in, but I hadn't seen it raised as an issue at that point.

Niall

----- Original Message ----- 
From: "Martin Cooper" <martinc@apache.org>
Sent: Thursday, December 08, 2005 3:26 AM


On 12/7/05, Niall Pemberton <niall.pemberton@blueyonder.co.uk> wrote:
>
> I started a page on the wiki with notes for checking a release candidate:
>
> http://wiki.apache.org/jakarta-commons/ReleaseChecking


Excellent!

One question, though: I don't understand the part about ensuring that the
component has a license for Simian. The referenced page on the Simian site
says it's free for open source use. Is there something else we're expected
to do?

Frankly, what it produces doesn't seem too useful, but I have it in
FileUpload because I picked up the line from some other project.xml. If
there's more work involved, then I'm probably more likely to simply remove
it.

--
Martin Cooper



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


Mime
View raw message