Hi Marcel, Thx for this valuable response, it is clear that RC2 cannot be released as-is and that improvements are needed. I will create JIRA issues for it, resolve them and come up with an RC3 later on (this week, I hope). See my comments below.
Regards, Ivo From: [email protected] [mailto:[email protected]] On Behalf Of Marcel Offermans Sent: vrijdag 6 mei 2011 18:48 To: [email protected] Subject: Re: [Amdatu-users] Release of Amdatu Cassandra 0.2.0 On 6 May 2011, at 16:56 , Ivo Ladage-van Doorn wrote: This will be the first official release of the Amdatu Cassandra subproject. All issues planned for the Amdatu Cassandra 0.2.0 release have been resolved and closed. The 0.2.0 Release Candidate 1 release has been created and is now available. All information, including download links, can be found on this WIKI page: http://www.amdatu.org/confluence/display/Amdatu/AC+-+Releases As there are no unclosed issues for 0.2.0, it's time to vote for the release of Amdatu Cassandra 0.2.0. The vote will be closed upcoming Thursday, May 12, at 17:00. If there are no binding -1 votes, 0.2.0 will be released on Friday May 13. The version numbers in the trunk have been updated to 0.2.1-SNAPSHOT, as we will start working on the 0.2.1 release. Quickly looked at the artifacts: - there are no versions on exported packages; [Ivo Ladage-van Doorn] Correct, there have never been for any Amdatu artifact. I'll create a JIRA issue to append version numbers to exported packages - there are no import ranges on imported packages; [Ivo Ladage-van Doorn] Correct, again, there have never been. Will add this required change to the previous JIRA issue. - in src/release/src/main/assembly there are xml files with missing license headers; [Ivo Ladage-van Doorn] OK, I'll create a JIRA issue to add these missing headers - are we or are we not releasing cassandra-gadgetstore (the sources are released, the binary is not); [Ivo Ladage-van Doorn] We are not, as the cassandra-gadgetstore depends on the opensocial API, which is not yet officially released. So to bypass this chicken-egg problem (with this artifact, before releasing Cassandra, opensocial should be released and vice versa) I removed the artifact from the reactor. I could have removed the source from the trunk (and still can) but decided to keep the source but disable it in the reactor (discussed this with Angelo). But if you want me to I have no problem to purge the code in the 0.2.0 release. - the LICENSE.ASL2 file is not necessary, as it is the same as the LICENSE file; [Ivo Ladage-van Doorn] Noticed, will fix that - the overall NOTICE file is missing the correct header, stating the component name and version and a copyright message containing the Amdatu Foundation; [Ivo Ladage-van Doorn] Correct, will fix that - we have to check if the Amdatu Foundation already exists, if not I don't think we can legally release; [Ivo Ladage-van Doorn] Ok, I will send an email to the board about that - bundle-license manifest header still states we're releasing GPL code; [Ivo Ladage-van Doorn] Hhmm, correct. Same for the generated license page in mvn site generation, will fix it - cassandra-application contains a Hadoop jar and a Jetty jar, but I don't see either being mentioned in the NOTICE file. [Ivo Ladage-van Doorn] Oh yes, missed these ones as I investigates compile dependencies in the pom.xml, but these dependencies are included in the jar by Embed-Transitive. There are more NOTICE's missing, likes nakeyaml and guava. Will add those. I'm not sure that we actually need more than one NOTICE file per released artifact, but I don't think so. [Ivo Ladage-van Doorn] Only one attribution notice is needed for the entire distribution, so this should not be necessary. So I'm afraid it's a -1 from me. Greetings, Marcel
_______________________________________________ Amdatu-users mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-users
