[RESULT] [VOTE] Release Jena Fuseki 0.2.1-incubating
The vote for Jena Fuseki 0.2.1-incubating passes with 3 +1 IPMC votes. +1's: IPMC: * Leo Simons * Benson Margulies * Mark Struberg as well as 3 +1's from PPMC members on the jena-dev list [1] 0's -1's Thanks everybody, I'll go push some buttons, Andy [1] http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201203.mbox/%3c4f63a159.7010...@apache.org%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Jena mentors (Was: [VOTE] Release Jena Fuseki 0.2.1-incubating)
Hi, On Wed, Mar 21, 2012 at 5:54 PM, Jukka Zitting wrote: > ...The Jena team page [2] lists you, Bertrand, Benson and Ross as > mentors. Is that accurate? If yes, please update the status page > accordingly. > > Mentors, do you have time to review the release candidate? Of course > anyone else from the IPMC is also welcome to cast their vote on the > release I wrote about a while ago to the jena private list about my time to mentor Jena being quite limited - in retrospect I should have stepped down at that point, as that got even worse since then. As Jena is about to graduate IIUC, I'll stay around and try to at least help give the last little push. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Rave 0.9-INCUBATING Release
The Apache Rave (Incubating) team is pleased to announce the immediate availability of the Rave 0.9-INCUBATING Alpha release. Apache Rave is a new web and social mashup engine. It will provide an out-of-the-box, as well as extendible, lightweight Java platform to host, serve and manage OpenSocial, W3C and other web widgets. Rave is targeted as an engine for internet and intranet portals and as a building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites. The release can be obtained from the Apache Rave download page (http://incubator.apache.org/rave/downloads.html). Release Notes for this release are available at http://s.apache.org/nP0. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flume version 1.1.0-incubating (rc1)
+1 Verified: * Unpacked source builds correctly. * Flume agent works using the sample config file on the built artifact. * LICENSE, CHANGELOG, NOTICE look good. -- Hari Shreedharan On Monday, March 19, 2012 at 5:46 PM, Arvind Prabhakar wrote: > This is the second incubator release for Apache Flume, version > 1.1.0-incubating. We are now voting on release candidate rc1. > > *** Please cast your vote within the next 72 hours *** > > The list of fixed issues: > https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/CHANGELOG > > The tarball (*.tar.gz), signature (*.asc), checksum (*.md5sum, > *.sha1sum) for the source and binary can be found at: > http://people.apache.org/~arvind/flume/110rc1/ > > The tag to be voted upon: > https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/ > > The KEYS file: > http://www.apache.org/dist/incubator/flume/KEYS > > Changes since last build: > * FLUME-1032. Fix Flume NG build for binary distribution > * Updated change log and release notes. > >
Re: [VOTE] Release for Bigtop version 0.3.0-incubating
I tried building/testing RC1 today. Question, I am probably doing something wrong here, not sure... Build was ok, can run PI test. I am trying to run the smoke tests in bigtop-tests/test-artifacts. I needed to add a to the pom for http://repository.cloudera.comso the dependency for itest will download. It does download (along with other jars it looks like) but I am getting these messages from mvn INFO] [INFO] bigtop-smokes . SUCCESS [6.724s] [INFO] hadoopsmoke ... FAILURE [2.136s] [INFO] hivesmoke . SKIPPED [INFO] packagesmoke .. SKIPPED [INFO] ooziesmoke SKIPPED [INFO] hbasesmoke SKIPPED [INFO] flumesmoke SKIPPED [INFO] sqoop-integration . SKIPPED [INFO] mahoutsmoke ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 9.964s [INFO] Finished at: Wed Mar 21 03:44:00 UTC 2012 [INFO] Final Memory: 10M/58M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project hadoop-smoke: Compilation failure: Compilation failure: [ERROR] error: error reading /home/ubuntu/.m2/repository/org/apache/hadoop/hadoop-core/ 0.20.205.0/hadoop-core-0.20.205.0.jar; error in opening zip file [ERROR] error: error reading /home/ubuntu/.m2/repository/org/apache/hadoop/hadoop-test/ 0.20.205.0/hadoop-test-0.20.205.0.jar; error in opening zip file [ERROR] error: error reading /home/ubuntu/.m2/repository/org/apache/bigtop/itest/itest-common/0.3.0-incubating/itest-common-0.3.0-incubating.jar; error in opening zip file Seems these jar files that were downloaded into my .m2 repository are corrupt. For example, itest-common-0.3.0-incubating.jar is only 392 bytes ubuntu@ip-10-168-178-138:~/.m2/repository/org/apache/bigtop/itest/itest-common/0.3.0-incubating$ ls -l total 20 -rw-r--r-- 1 ubuntu ubuntu 392 2012-03-21 03:38 itest-common-0.3.0-incubating.jar -rw-r--r-- 1 ubuntu ubuntu 282 2012-03-21 03:38 itest-common-0.3.0-incubating.jar.lastUpdated -rw-r--r-- 1 ubuntu ubuntu 392 2012-03-21 03:38 itest-common-0.3.0-incubating.pom -rw-r--r-- 1 ubuntu ubuntu 282 2012-03-21 03:38 itest-common-0.3.0-incubating.pom.lastUpdated -rw-r--r-- 1 ubuntu ubuntu 214 2012-03-21 03:38 _maven.repositories ubuntu@ip-10-168-178-138:~/.m2/repository/org/apache/bigtop/itest/itest-common/0.3.0-incubating$ if I try to unzip manually I get... ubuntu@ip-10-168-178-138:~/.m2/repository/org/apache/bigtop/itest/itest-common/0.3.0-incubating$ unzip itest-common-0.3.0-incubating.jar Archive: itest-common-0.3.0-incubating.jar End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of itest-common-0.3.0-incubating.jar or itest-common-0.3.0-incubating.jar.zip, and cannot find itest-common-0.3.0-incubating.jar.ZIP, period. Any advice would be appreciated Regards Ron On Tue, Mar 20, 2012 at 11:35 AM, Roman Shaposhnik wrote: > This is the third incubator release for Apache Bigtop, version > 0.3.0-incubating. > > It fixes the following issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317841&projectId=12311420 > > The delta between RC0 and RC1 includes fixes for the following issues: >BIGTOP-446. Typo in hadoop module for puppet > BIGTOP-459. remove references to cloudera from the packaging files > BIGTOP-443. deb/oozie/oozie-client.postinst installs an alternative > for a path that isn't there > BIGTOP-382. hadoop-conf-pseudo packages contains subversion metada >BIGTOP-457. Bigtop 0.3.0: Hadoop namenode doesnt start after > installing the deb package > > *** Please download, test, and vote by Mon, March 26 > > Note that we are voting on the source (tag): release-0.3.0-incubating-RC1 > > Source tarball, checksums, signature: >http://people.apache.org/~rvs/bigtop-0.3.0-incubating-RC1/ > > The tag to be voted on: > > https://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.3.0-incubating-RC1/ > > Bigtop's KEYS file, containing the PGP keys used to sign the release: > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS > > Please also make sure to try installing our convenience binary distribution > artifacts. We are publishing the Bigtop 0.3.0 incubating distributions for > the > following Linux platforms: Ubuntu 10.04, Cent
Re: Keeping an eye out for new committers
I'll throw in my +1 too. Folks that provide doc are just as valuable as folks writing code as it delivers value for the consumer of the project. Its value to the project being delivered in different ways. Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine On Mar 19, 2012, at 10:47 AM, Joe Schaefer wrote: > +1 Dan, people really do learn from the codebase as they whittle > on it. I know when I first got commit at the ASF I knew precious > little about C, but after a few years of work here finally got the hang > of it. > > > > - Original Message - >> From: Daniel Kulp >> To: general@incubator.apache.org >> Cc: Alan Gates ; Jukka Zitting >> >> Sent: Monday, March 19, 2012 10:42 AM >> Subject: Re: Keeping an eye out for new committers >> >> On Friday, March 16, 2012 04:28:06 PM Alan Gates wrote: >>> With my mentor hat on, this is a poke to remind you (the PPMC) that >> it's >>> your job to be on the lookout for contributors that may be ready to >>> become committers. >>> >>> I look for several things when I consider making someone a committer: >>> >>> 1) Patches, are they contributing quality features and/or bug fixes. They >>> don't have to have written a new subsystem, but you want to look for >>> patches that demonstrate understanding in some area, not just spelling >>> fixes in error messages, etc. >> >> I just want to mention that patches that fix "just spelling fixes in error >> messages, etc." shouldn't be discounted so harshly. In CXF, one of >> the >> historically most active contributors got started by deluging us with such >> patches. We made him a committer (so he could fix all of that himself) >> which helped build his confidence and he's expanded out from there. His >> work just on the spelling mistakes and messages and stuff has been a big >> help in making things "feel" more professional, especially in a >> projects >> where a large number of people don't have english as their native language. >> >> >> All contributions are welcome and have value. Just because it may not be >> technical in nature doesn't make them have any less value from a >> "should >> this person be a committer" standpoint. >> >> But the rest of this is good. :-) >> >> >> Dan >> >> >> >> >> >>> One good way to find what patches a >>> contributor has done is to look over the contributor report from JIRA. >>> You can get this by going to your project's JIRA, and under the reports >>> drop down on the right side, click on "Contribution Report". >>> >>> 2) Emails, comments on JIRA, etc. giving others feedback, answering user >>> questions, etc. Again you can use the contribution report to see JIRA >>> comments. You can find emails in the mailing list archives for your >>> project. >>> >>> 3) Is this person good to work with? Do they give constructive feedback? >>> Do they take feedback well? >>> >>> 4) Does this person seem likely to stay involved? All Apache positions >>> are volunteer and so we can't ask people to sign up for a period of >> time >>> or promise to be around forever. But if I sense that a contributor is >>> just fixing one problem they need fixed, I usually wait to see if they >>> continue their involvement after that issue is addressed before >>> nominating them as a committer. >>> >>> Alan. >>> >>> >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >> -- >> Daniel Kulp >> dk...@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> >> >> - >> 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 Flume version 1.1.0-incubating (rc1)
+1 Verified checksums, signatures, and source/binary build. On Mon, Mar 19, 2012 at 5:46 PM, Arvind Prabhakar wrote: > This is the second incubator release for Apache Flume, version > 1.1.0-incubating. We are now voting on release candidate rc1. > > *** Please cast your vote within the next 72 hours *** > > The list of fixed issues: > https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/CHANGELOG > > The tarball (*.tar.gz), signature (*.asc), checksum (*.md5sum, > *.sha1sum) for the source and binary can be found at: > http://people.apache.org/~arvind/flume/110rc1/ > > The tag to be voted upon: > https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/ > > The KEYS file: > http://www.apache.org/dist/incubator/flume/KEYS > > Changes since last build: > * FLUME-1032. Fix Flume NG build for binary distribution > * Updated change log and release notes. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flume version 1.1.0-incubating (rc1)
+1. Great work Arvind! On Mon, Mar 19, 2012 at 5:46 PM, Arvind Prabhakar wrote: > This is the second incubator release for Apache Flume, version > 1.1.0-incubating. We are now voting on release candidate rc1. > > *** Please cast your vote within the next 72 hours *** > > The list of fixed issues: > > https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/CHANGELOG > > The tarball (*.tar.gz), signature (*.asc), checksum (*.md5sum, > *.sha1sum) for the source and binary can be found at: > http://people.apache.org/~arvind/flume/110rc1/ > > The tag to be voted upon: > > https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/ > > The KEYS file: > http://www.apache.org/dist/incubator/flume/KEYS > > Changes since last build: > * FLUME-1032. Fix Flume NG build for binary distribution > * Updated change log and release notes. > -- Eric Sammer twitter: esammer data: www.cloudera.com
