Thanks for the clarification. I will be sure to reflect the suggestion in the IPMC vote thread.
Sent via a mobile device. Please excuse typos or brevity. -----Original Message----- From: Ate Douma [mailto:[email protected]] Sent: Wednesday, June 29, 2011 02:32 PM Eastern Standard Time To: [email protected] Subject: Re: [DISCUSS] Apache Rave 0.1-incubating Release Candidate Great work Matt and looking good so far! One minor detail concerning the [VOTE] email itself: Only the *-source-release.zip distributions for the rave-master-pom and the rave-project projects represent true and valid (complete!) source distributions. The other two *-sources.jar for rave-portal and rave-shindig are supportive artifacts intended to be used by IDEs, but do are not valid source distributions from ASF requirements POV. An ASF source release must be completely self-contained from which the project(s) can be build by itself. For one, this requires build scripts etc. (our maven pom.xml) to be embedded. So only the primary *-source-release.zip files qualify for this (and the one for rave-project also covers/contains everything for rave-shindig and rave-portal as well). For future release [VOTE] messages only these *-source-release.zip archives needs to be indicated as such. Furthermore, after the VOTE (if accepted) the only these two zip archives and the binary distributions need/should be provided from the official dist download area. Regards, Ate On 06/29/2011 07:37 PM, Franklin, Matthew B. wrote: > Discussion thread for vote on 0.1-incubating release candidate. > > For more information on the release process, checkout - > http://www.apache.org/dev/release.html > http://incubator.apache.org/guides/releasemanagement.html > > Some of the things to check before voting are: > - can you run the demo binaries > - can you build the contents of source-release.zip and svn tag > - do all of the staged jars/zips contain the required LICENSE, NOTICE and > DISCLAIMER files > - are all of the staged jars signed and the signature verifiable > - is the signing key in the project's KEYS file and on a public server >
