Re: [VOTE] Chukwa 0.5.0 Release Candidate 3
+1 Same comment on the NOTICE file as over here: http://apache.markmail.org/message/hlfebouyg3r5w27i ...ant On Fri, Jan 20, 2012 at 6:46 AM, Eric Yang eric...@gmail.com wrote: Still missing one IPMC vote. Could someone help out? regards, Eric On Tue, Jan 17, 2012 at 12:06 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 1/15/2012 1:42 AM, Ralph Goers wrote: You know, you have 4 mentors all of whom are supposed to be IPMC members. Have they voted? Nope, traveling, and now back in project hell at one of my own homes. I did review the Chukwa monthly report and comment on several apparent issues on dev@. I don't expect to have time to review this specific candidate, owing to a backlog of work accumulated over this short vacation. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC4)
On Thu, Jan 19, 2012 at 4:38 PM, Reto Bachmann-Gmür m...@farewellutopia.com wrote: On Wed, Jan 18, 2012 at 10:36 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jan 17, 2012 at 2:52 PM, Reto Bachmann-Gmür r...@apache.org wrote: ...The reason the license files is not at the root is that we are releasing a few dozen modules which are released together for voting convenience but could also released separately. I suggest to add a note in the readme pointing out that the some modules contain additional license and notice files I agree with that, but it doesn't require cutting a new release IMO - releasing with an open issue in Clerezza's jira about this would be fine from my Clerezza mentor's point of view. I've added a README in the root, see http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/README.txt Also I've added a project to create an assembly of that contains only the sources of the modules of an active build project, it is here: http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/clerezza-jar-resource-bundle/ With these I plan to prepare a new release candidate tomorrow. Reto Its not clear if that will change the binary distribution so just a quick note to remind about that as it also needs to note all the licenses it uses. (i did check on you dev list and it doesn't look like the respin has happen yet so hopefully that isn't an inconvenience) ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC4)
On Mon, Jan 23, 2012 at 10:00 AM, Reto Bachmann-Gmür m...@farewellutopia.com wrote: On Mon, Jan 23, 2012 at 9:55 AM, ant elder ant.el...@gmail.com wrote: On Thu, Jan 19, 2012 at 4:38 PM, Reto Bachmann-Gmür m...@farewellutopia.com wrote: On Wed, Jan 18, 2012 at 10:36 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jan 17, 2012 at 2:52 PM, Reto Bachmann-Gmür r...@apache.org wrote: ...The reason the license files is not at the root is that we are releasing a few dozen modules which are released together for voting convenience but could also released separately. I suggest to add a note in the readme pointing out that the some modules contain additional license and notice files I agree with that, but it doesn't require cutting a new release IMO - releasing with an open issue in Clerezza's jira about this would be fine from my Clerezza mentor's point of view. I've added a README in the root, see http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/README.txt Also I've added a project to create an assembly of that contains only the sources of the modules of an active build project, it is here: http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/clerezza-jar-resource-bundle/ With these I plan to prepare a new release candidate tomorrow. Reto Its not clear if that will change the binary distribution so just a quick note to remind about that as it also needs to note all the licenses it uses. (i did check on you dev list and it doesn't look like the respin has happen yet so hopefully that isn't an inconvenience) Yes I adapted the NOTICE of the launcher (i.e. the one in the binary distro) as follows: http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/platform.launcher.tdb/NOTICE?view=markup Cheers, Reto I don't think the NOTICE file is the correct place for these, and i don't think thats enough to document the licenses that apply. As one example, the binary release clerezza-tdb-distribution.zip contains a big jar platform.launcher.tdb-0.5-incubating.jar which embeds other jars, for example it contains servlet-api-3.0.20100224.jar, which is EPL licensed so that needs to be mentioned in clerezza-tdb-distribution.zip. There are many jars within jars using various licenses included in clerezza-tdb-distribution.zip which also need to be mentioned. Ask your mentors for help if the requirements aren't clear, or at least ask them to vote here if they disagree. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC4)
On Mon, Jan 23, 2012 at 11:32 AM, ant elder antel...@apache.org wrote: On Mon, Jan 23, 2012 at 10:00 AM, Reto Bachmann-Gmür m...@farewellutopia.com wrote: On Mon, Jan 23, 2012 at 9:55 AM, ant elder ant.el...@gmail.com wrote: On Thu, Jan 19, 2012 at 4:38 PM, Reto Bachmann-Gmür m...@farewellutopia.com wrote: On Wed, Jan 18, 2012 at 10:36 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jan 17, 2012 at 2:52 PM, Reto Bachmann-Gmür r...@apache.org wrote: ...The reason the license files is not at the root is that we are releasing a few dozen modules which are released together for voting convenience but could also released separately. I suggest to add a note in the readme pointing out that the some modules contain additional license and notice files I agree with that, but it doesn't require cutting a new release IMO - releasing with an open issue in Clerezza's jira about this would be fine from my Clerezza mentor's point of view. I've added a README in the root, see http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/README.txt Also I've added a project to create an assembly of that contains only the sources of the modules of an active build project, it is here: http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/clerezza-jar-resource-bundle/ With these I plan to prepare a new release candidate tomorrow. Reto Its not clear if that will change the binary distribution so just a quick note to remind about that as it also needs to note all the licenses it uses. (i did check on you dev list and it doesn't look like the respin has happen yet so hopefully that isn't an inconvenience) Yes I adapted the NOTICE of the launcher (i.e. the one in the binary distro) as follows: http://svn.apache.org/viewvc/incubator/clerezza/trunk/parent/platform.launcher.tdb/NOTICE?view=markup Cheers, Reto Thanks Ant, for looking at this this in such detail. After 4 candidates had to be dismissed for license reasons it would be good to have this things fixed for the next release candidate. I don't think the NOTICE file is the correct place for these, and i don't think thats enough to document the licenses that apply. What would the right place be then? As one example, the binary release clerezza-tdb-distribution.zip contains a big jar platform.launcher.tdb-0.5-incubating.jar which embeds other jars, for example it contains servlet-api-3.0.20100224.jar, which is EPL licensed so that needs to be mentioned in clerezza-tdb-distribution.zip. Is there a way to systematically find out the license of such transitive maven dependencies? The jar you mention contains no license or notice file, it contains a maven pom file without licensing information. It seems to be part of the pre-eclipse jetty release, on the mortbay website I read that jetty is apache licensed. Other jetty files are in org/eclipse and thus probably EPL. There are many jars within jars using various licenses included in clerezza-tdb-distribution.zip which also need to be mentioned. Ask your mentors for help if the requirements aren't clear, or at least ask them to vote here if they disagree. I added our mentors to the cc, hoping they step into the conversation and that I eventually know what step I need to do for a legally acceptable release. Cheers, Reto
Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC4)
On Mon, Jan 23, 2012 at 12:12 PM, Reto Bachmann-Gmür r...@apache.org wrote: On Mon, Jan 23, 2012 at 11:32 AM, ant elder antel...@apache.org wrote: ...As one example, the binary release clerezza-tdb-distribution.zip contains a big jar platform.launcher.tdb-0.5-incubating.jar which embeds other jars, for example it contains servlet-api-3.0.20100224.jar, which is EPL licensed so that needs to be mentioned in clerezza-tdb-distribution.zip. Is there a way to systematically find out the license of such transitive maven dependencies? The jar you mention contains no license or notice file, it contains a maven pom file without licensing information... I'm afraid the only way to find out about such a license is to hunt that project's website. The techniques mentioned on my blog at [1] should list all the dependencies of a Maven project, and after you remove all the known good ones (org.apache.* etc.) you're left with a list of dependencies that need to be checked. The cleanest way to handle that for Clerezza might be to add a note to the LICENSE file that lists which other licenses besides Apache are included, and points to a text file with licensing information for those additional dependencies. Putting some simple structure in that file might help automating (at least partially) that check for future releases. -Bertrand [1] http://grep.codeconsult.ch/2010/07/08/list-all-your-maven-dependencies/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC4)
On Mon, Jan 23, 2012 at 2:27 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Jan 23, 2012 at 12:12 PM, Reto Bachmann-Gmür r...@apache.org wrote: On Mon, Jan 23, 2012 at 11:32 AM, ant elder antel...@apache.org wrote: ...As one example, the binary release clerezza-tdb-distribution.zip contains a big jar platform.launcher.tdb-0.5-incubating.jar which embeds other jars, for example it contains servlet-api-3.0.20100224.jar, which is EPL licensed so that needs to be mentioned in clerezza-tdb-distribution.zip. Is there a way to systematically find out the license of such transitive maven dependencies? The jar you mention contains no license or notice file, it contains a maven pom file without licensing information... I'm afraid the only way to find out about such a license is to hunt that project's website. The techniques mentioned on my blog at [1] should list all the dependencies of a Maven project, and after you remove all the known good ones (org.apache.* etc.) you're left with a list of dependencies that need to be checked. Thanks for the hint. We have to do this for the tdb launcher as well as for the storageless parent as the tdb launcher includes all of the storageless launcher without its dependencies resulting as tdb launcher dependencies (the scope 'provided' prevents transitivity) The cleanest way to handle that for Clerezza might be to add a note to the LICENSE file that lists which other licenses besides Apache are included, and points to a text file with licensing information for those additional dependencies. Putting some simple structure in that file might help automating (at least partially) that check for future releases. I prefer having different files for the different licenses so that two LICENSE*-files always have the same content. Reto
Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC4)
On Mon, Jan 23, 2012 at 4:00 PM, Reto Bachmann-Gmür r...@apache.org wrote: On Mon, Jan 23, 2012 at 2:27 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ... The cleanest way to handle that for Clerezza might be to add a note to the LICENSE file that lists which other licenses besides Apache are included, and points to a text file with licensing information for those additional dependencies. Putting some simple structure in that file might help automating (at least partially) that check for future releases. I prefer having different files for the different licenses so that two LICENSE*-files always have the same content... Ok, but note http://www.apache.org/dev/release.html#distributing-code-under-several-licenses which says all license information should be contained in the LICENSE file. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Rave 0.7-incubating
This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGELOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release MRUnit version 0.8.0-incubating
Hi Brock, I'm -1 on this release. checksums check out: mrunit-0.8.0-incubating-dist.tar.gz mrunit-0.8.0-incubating-dist.tar.gz.sha1 mrunit-0.8.0-incubating-dist.zip.md5 mrunit-0.8.0-incubating-dist.tar.gz.asc mrunit-0.8.0-incubating-dist.zip mrunit-0.8.0-incubating-dist.zip.sha1 mrunit-0.8.0-incubating-dist.tar.gz.md5 mrunit-0.8.0-incubating-dist.zip.asc [chipotle:~/tmp/mrunit-0.8.0] mattmann% ls -al total 576 drwxr-xr-x 10 mattmann staff 340 Jan 23 10:52 ./ drwxr-xr-x 30 mattmann staff1020 Jan 23 10:52 ../ -rw-r--r-- 1 mattmann staff 109300 Jan 23 10:52 mrunit-0.8.0-incubating-dist.tar.gz -rw-r--r-- 1 mattmann staff 836 Jan 23 10:52 mrunit-0.8.0-incubating-dist.tar.gz.asc -rw-r--r-- 1 mattmann staff 32 Jan 23 10:52 mrunit-0.8.0-incubating-dist.tar.gz.md5 -rw-r--r-- 1 mattmann staff 40 Jan 23 10:52 mrunit-0.8.0-incubating-dist.tar.gz.sha1 -rw-r--r-- 1 mattmann staff 158705 Jan 23 10:52 mrunit-0.8.0-incubating-dist.zip -rw-r--r-- 1 mattmann staff 836 Jan 23 10:52 mrunit-0.8.0-incubating-dist.zip.asc -rw-r--r-- 1 mattmann staff 32 Jan 23 10:52 mrunit-0.8.0-incubating-dist.zip.md5 -rw-r--r-- 1 mattmann staff 40 Jan 23 10:52 mrunit-0.8.0-incubating-dist.zip.sha1 [chipotle:~/tmp/mrunit-0.8.0] mattmann% $HOME/bin/verify_md5_checksums mrunit-0.8.0-incubating-dist.tar.gz: OK mrunit-0.8.0-incubating-dist.zip: OK But, the GPG SIGS don't for whatever reason: [chipotle:~/tmp/mrunit-0.8.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mrunit-0.8.0-incubating-dist.tar.gz.asc gpg: Signature made Sat Jan 7 13:57:38 2012 PST using RSA key ID 8E991CC5 gpg: Can't check signature: No public key Verifying Signature for file mrunit-0.8.0-incubating-dist.zip.asc gpg: Signature made Sat Jan 7 13:57:38 2012 PST using RSA key ID 8E991CC5 gpg: Can't check signature: No public key [chipotle:~/tmp/mrunit-0.8.0] mattmann% It looks like the releases were signed with key 8E991CC5: Looking at: http://www.apache.org/dist/incubator/mrunit/KEYS: [chipotle:~/tmp/mrunit-0.8.0] mattmann% gpg --import KEYS gpg: key 901791C2: Eric Sammer esam...@apache.org not changed gpg: key B4AE10F8: Brock Noland (CODE SIGNING KEY) br...@apache.org not changed gpg: Total number processed: 2 gpg: unchanged: 2 [chipotle:~/tmp/mrunit-0.8.0] mattmann% ls I don't see a key for either you or for Eric that match the key that was used to sign the releases. Am I missing something? Cheers, Chris On Jan 20, 2012, at 5:30 PM, Brock Noland wrote: I am +1 as well. I verified the signatures, checksums, and unit tests. Does anyone else have a few minutes to vote the on the release? Brock On Wed, Jan 11, 2012 at 11:49 AM, Patrick Hunt ph...@apache.org wrote: +1 sig/xsum match up, tested clean and RAT reports fine. It's a bit odd to me that there are two source release artifacts here (one archived with tar/gz the other with zip), I've not seen that for other projects. Typically you want to have a single source release artifact. You could then create convenience artifacts off that. I verified that the contents of the two artifacts are exactly the same, just differing archiving tools. Patrick On Mon, Jan 9, 2012 at 3:52 PM, Brock Noland br...@cloudera.com wrote: This is an incubator release for Apache MRUnit, version 0.8.0-incubating. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12316359 *** Please download, test and vote by [3 working days after sending]. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~brock/mrunit-0.8.0-incubating-candidate-0 Maven staging repo: https://repository.apache.org/content/repositories/orgapachemrunit-031/ The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.8.0-incubating/ MRUnit's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS Note that the Incubator PMC needs to vote upon the release after a successful PPMC vote before any release can be made official. ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rave 0.7-incubating
On 23 January 2012 15:17, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGELOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rave 0.7-incubating
On 1/23/12 3:29 PM, sebb seb...@gmail.com wrote: On 23 January 2012 15:17, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGE LOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? The release was spun on January 4th of 2012 and there were 4 minor changes made between 2012 the release. Based on prior discussions on this list, minor changes don't seem to be a blocker [1]. Additionally, I have created a JIRA ticket for updating the copyright date on all NOTICE files [2]. [1] : http://markmail.org/message/3b776xpdzijynypc [2] : https://issues.apache.org/jira/browse/RAVE-439 Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/ apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-sourc e-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rave 0.7-incubating
On 01/23/2012 10:30 PM, Franklin, Matthew B. wrote: On 1/23/12 3:29 PM, sebbseb...@gmail.com wrote: On 23 January 2012 15:17, Franklin, Matthew B.mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGE LOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? The release was spun on January 4th of 2012 and there were 4 minor changes made between 2012 the release. Based on prior discussions on this list, minor changes don't seem to be a blocker [1]. Additionally, I have created a JIRA ticket for updating the copyright date on all NOTICE files [2]. [1] : http://markmail.org/message/3b776xpdzijynypc [2] : https://issues.apache.org/jira/browse/RAVE-439 Besides this being a minor and certainly non-blocker issue, a similar question came up just last week on legal-discuss@ where the question was if every copyright statement would need to be 'bumped' to adjust for the new year. Greg Stein provided IMO a nice and clear (follow up) answer about the importance of how and when to do this [3]: quote Actually, the shorter answer is get it close, but don't worry about it. (per a lawyer friend of mine) What you put in the header is advisory. If you end up in court, it has zero impact compared to the actual commit history that demonstrates it is your work. Your work is the operative issue; not when you happened to do that work. /quote Original message and thread link: http://markmail.org/message/v3n7vyd4anxmgzbn So I see no reason at all to worry about these now. And, for the record, none of the NOTICE files in this release themselves were modified since 2011. Ate Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/ apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-sourc e-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rave 0.7-incubating
On 01/23/2012 10:56 PM, Ate Douma wrote: On 01/23/2012 10:30 PM, Franklin, Matthew B. wrote: On 1/23/12 3:29 PM, sebbseb...@gmail.com wrote: On 23 January 2012 15:17, Franklin, Matthew B.mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGE LOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? The release was spun on January 4th of 2012 and there were 4 minor changes made between 2012 the release. Based on prior discussions on this list, minor changes don't seem to be a blocker [1]. Additionally, I have created a JIRA ticket for updating the copyright date on all NOTICE files [2]. [1] : http://markmail.org/message/3b776xpdzijynypc [2] : https://issues.apache.org/jira/browse/RAVE-439 Besides this being a minor and certainly non-blocker issue, a similar question came up just last week on legal-discuss@ where the question was if every copyright statement would need to be 'bumped' to adjust for the new year. Greg Stein provided IMO a nice and clear (follow up) answer about the importance of how and when to do this [3]: quote Actually, the shorter answer is get it close, but don't worry about it. (per a lawyer friend of mine) What you put in the header is advisory. If you end up in court, it has zero impact compared to the actual commit history that demonstrates it is your work. Your work is the operative issue; not when you happened to do that work. /quote Original message and thread link: http://markmail.org/message/v3n7vyd4anxmgzbn On second thought, the above quote might not be relevant in *this* context, as in this case it concerns the NOTICE file, not some copyrighted resource itself. Nonetheless, the fact this was a release cut on January 4th, I think it truely isn't of much concern anyway, and for subsequent releases we'll adjust the copyright date. I do however very much appreciate the proper review and feedback from sebb, and others on general@ alike, because all these tiny issues are soo easy to overlook! Thanks, Ate So I see no reason at all to worry about these now. And, for the record, none of the NOTICE files in this release themselves were modified since 2011. Ate Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/ apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-sourc e-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Rave 0.7-incubating
-Original Message- From: Ate Douma [mailto:a...@douma.nu] Sent: Monday, January 23, 2012 5:14 PM To: rave-...@incubator.apache.org Cc: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.7-incubating On 01/23/2012 10:56 PM, Ate Douma wrote: On 01/23/2012 10:30 PM, Franklin, Matthew B. wrote: On 1/23/12 3:29 PM, sebbseb...@gmail.com wrote: On 23 January 2012 15:17, Franklin, Matthew B.mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7- incubating/CHANGE LOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? The release was spun on January 4th of 2012 and there were 4 minor changes made between 2012 the release. Based on prior discussions on this list, minor changes don't seem to be a blocker [1]. Additionally, I have created a JIRA ticket for updating the copyright date on all NOTICE files [2]. [1] : http://markmail.org/message/3b776xpdzijynypc [2] : https://issues.apache.org/jira/browse/RAVE-439 Besides this being a minor and certainly non-blocker issue, a similar question came up just last week on legal-discuss@ where the question was if every copyright statement would need to be 'bumped' to adjust for the new year. Greg Stein provided IMO a nice and clear (follow up) answer about the importance of how and when to do this [3]: quote Actually, the shorter answer is get it close, but don't worry about it. (per a lawyer friend of mine) What you put in the header is advisory. If you end up in court, it has zero impact compared to the actual commit history that demonstrates it is your work. Your work is the operative issue; not when you happened to do that work. /quote Original message and thread link: http://markmail.org/message/v3n7vyd4anxmgzbn On second thought, the above quote might not be relevant in *this* context, as in this case it concerns the NOTICE file, not some copyrighted resource itself. Nonetheless, the fact this was a release cut on January 4th, I think it truely isn't of much concern anyway, and for subsequent releases we'll adjust the copyright date. I do however very much appreciate the proper review and feedback from sebb, and others on general@ alike, because all these tiny issues are soo easy to overlook! +1. Much better to catch it on January 23rd, 2012 than on January 23rd, 2015. Thanks, Sebb. Thanks, Ate So I see no reason at all to worry about these now. And, for the record, none of the NOTICE files in this release themselves were modified since 2011. Ate Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave- 015/ Source release: https://repository.apache.org/content/repositories/orgapacherave- 015/org/ apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating- sourc e-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7- incubating/apache-rave -0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7- incubating/apache-rave -0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release MRUnit version 0.8.0-incubating
OK, I switch my VOTE to +1. The update worked perfectly: [chipotle:~/tmp/mrunit-0.8.0] mattmann% curl -O http://www.apache.org/dist/incubator/mrunit/KEYS % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 5950 100 59500 0 56767 0 --:--:-- --:--:-- --:--:-- 87500 [chipotle:~/tmp/mrunit-0.8.0] mattmann% gpg --import KEYS gpg: key 901791C2: Eric Sammer esam...@apache.org not changed gpg: key 8E991CC5: public key Brock Noland (CODE SIGNING KEY) br...@apache.org imported gpg: key B4AE10F8: Brock Noland (CODE SIGNING KEY) br...@apache.org not changed gpg: Total number processed: 3 gpg: imported: 1 (RSA: 1) gpg: unchanged: 2 [chipotle:~/tmp/mrunit-0.8.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mrunit-0.8.0-incubating-dist.tar.gz.asc gpg: Signature made Sat Jan 7 13:57:38 2012 PST using RSA key ID 8E991CC5 gpg: Good signature from Brock Noland (CODE SIGNING KEY) br...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 2847 DD2B 26E1 A3D8 1949 C883 9DC2 7AFB 8E99 1CC5 Verifying Signature for file mrunit-0.8.0-incubating-dist.zip.asc gpg: Signature made Sat Jan 7 13:57:38 2012 PST using RSA key ID 8E991CC5 gpg: Good signature from Brock Noland (CODE SIGNING KEY) br...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 2847 DD2B 26E1 A3D8 1949 C883 9DC2 7AFB 8E99 1CC5 [chipotle:~/tmp/mrunit-0.8.0] mattmann% Thanks Brock! Cheers, Chris On Jan 23, 2012, at 11:13 AM, Brock Noland wrote: Hi, On Mon, Jan 23, 2012 at 12:57 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Brock, I don't see a key for either you or for Eric that match the key that was used to sign the releases. Am I missing something? Yep, my fault. I created my original key on my laptop while traveling and then my laptop died before I could copy it to my home machine. As such, I had to generate a new key. Looks like I missed uploading this: https://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS to here: http://www.apache.org/dist/incubator/mrunit/KEYS I have now done so, but I think it takes an hour or two before the public site updates. Brock ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rave 0.7-incubating
+1 (non-binding) Cheers, Andreas On 23.01.2012 16:17, Franklin, Matthew B. wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGELOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
