Re: [VOTE] Release Apache Hama 0.4-incubating RC6
Thanks. I've created hash files. On Tue, Feb 21, 2012 at 11:44 AM, sebb wrote: > On 20 February 2012 13:54, Edward J. Yoon wrote: >> Hi, >> >> I've create RC6 for the Apache Hama 0.4-incubating release. This fixes >> the license header issue and adds rat-plugin. >> >> Signing KEYS: >> http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/files/KEYS >> Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ > > There are no hashes (MD5 or SHA1). > AIUI these are required. > No need to respin the release, but please create the hashes. > >> Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ >> NOTICE.txt: >> http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt >> LICENSE.txt: >> http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt >> Staging website: http://people.apache.org/~edwardyoon/site/ >> >> You can run the "mvn apache-rat:check" command to check for license headers. >> >> I tested this RC6 builds, single mode, and distributed mode on my 16 >> nodes cluster and 5 VMs with EC2. >> >> Please retry, check signatures, licenses, and vote! >> >> I hope this will be a final, and +1. >> >> Thanks. >> -- >> Best Regards, Edward J. Yoon >> @eddieyoon >> >> - >> 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 > -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1291238 - in /incubator/public/trunk/site-publish: index.html projects/awf.html projects/index.html
On 20 February 2012 13:07, wrote: > Author: elecharny > Date: Mon Feb 20 13:07:13 2012 > New Revision: 1291238 > > URL: http://svn.apache.org/viewvc?rev=1291238&view=rev > Log: > Updated the site to reflect the deft->awf renaming > > Added: > incubator/public/trunk/site-publish/projects/awf.html Next time, please set eol-style:native on new files. > Modified: > incubator/public/trunk/site-publish/index.html > incubator/public/trunk/site-publish/projects/index.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1291363 - /incubator/public/trunk/site-author/projects/isis.xml
On 20 February 2012 16:52, wrote: > Author: danhaywood > Date: Mon Feb 20 16:52:18 2012 > New Revision: 1291363 > > URL: http://svn.apache.org/viewvc?rev=1291363&view=rev > Log: > Updating Isis project summary after 0.2.0-incubating release > > Modified: > incubator/public/trunk/site-author/projects/isis.xml Next time please regenerate the site and commit the updated html version of the file. > > Modified: incubator/public/trunk/site-author/projects/isis.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/site-author/projects/isis.xml?rev=1291363&r1=1291362&r2=1291363&view=diff > == > --- incubator/public/trunk/site-author/projects/isis.xml [utf-8] (original) > +++ incubator/public/trunk/site-author/projects/isis.xml [utf-8] Mon Feb 20 > 16:52:18 2012 > @@ -26,9 +26,9 @@ > News > > > - 2010-09-07 Isis has been accepted to enter incubation > - > + 2012-02-20 Released version 0.2.0-incubating > 2011-07-14 Released version 0.1.2-incubating > + 2010-09-07 Isis has been accepted to enter incubation > > > > @@ -274,20 +274,20 @@ > > > > - http://wiki.apache.org/incubator/October2010#Isis";>October > - 2010 > + + href="http://wiki.apache.org/incubator/December2011#Isis";>December > + 2011 > > > > - href="http://wiki.apache.org/incubator/November2010#Isis";>November > - 2010 > + > href="http://wiki.apache.org/incubator/September2011#Isis";>September > + 2011 > > > > - - href="http://wiki.apache.org/incubator/December2010#Isis";>December > - 2010 > + http://wiki.apache.org/incubator/June2011#Isis";>June > + 2011 > > > > @@ -296,20 +296,20 @@ > > > > - http://wiki.apache.org/incubator/June2011#Isis";>June > - 2011 > + + href="http://wiki.apache.org/incubator/December2010#Isis";>December > + 2010 > > > > - > href="http://wiki.apache.org/incubator/September2011#Isis";>September > - 2011 > + href="http://wiki.apache.org/incubator/November2010#Isis";>November > + 2010 > > > > - - href="http://wiki.apache.org/incubator/December2011#Isis";>December > - 2011 > + http://wiki.apache.org/incubator/October2010#Isis";>October > + 2010 > > > > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: migrating the main site to the CMS- a simple approach
On 21 February 2012 02:31, sebb wrote: > On 15 February 2012 15:44, Jukka Zitting wrote: >> Hi, >> >> On Wed, Feb 15, 2012 at 1:59 AM, sebb wrote: >>> The first thing to do is to decide if the following directory tree can >>> be junked: >>> >>> site-publish/projects/altrmi/ >>> >>> I suspect it can, as altrmi has moved elsewhere, but I just want to >>> check it's not being kept for historical reasons. >> >> +1 to removing. We still have the content archived in svn history. > > Done > >>> The other files currently only in site-publish are: >>> >>> ! 1243649 site-publish\projects\geronimo\status.html >>> ! 1243649 site-publish\projects\geronimo\status.pdf >> >> Remove. Geronimo status is at /projects/geronimo.html. > > Done > >>> ! 1243649 site-publish\projects\lcf.html >> >> Remove. LCF renamed itself to ManifoldCF, and its status is now at >> /projects/manifoldcf.html. > > Done > >>> ! 1243649 site-publish\projects\geronimo-proposal.html >> >> Keep. It should be linked to from the proposal list on the Incubator >> wiki, or perhaps migrated entirely into the wiki (or at least to a >> better place in site-author). > > Not sure why that file was flagged as a problem by my testing - there > is a source file for it under site-author. Discovered the problem. There are two such html files, but only one source: site-author\projects\geronimo\geronimo-proposal.xml site-publish\projects\geronimo-proposal.html site-publish\projects\geronimo\geronimo-proposal.html It looks like the middle file was created a long time ago, and then the xml file was moved. So I will delete the middle file. >>> ! 1243649 site-publish\projects\ruper.html >> >> Remove. AFAICT, Ruper renamed itself to Depot, and its status is now >> at /projects/depot.html. > > Done. > >> BR, >> >> Jukka Zitting >> >> - >> 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: svn commit: r1244915 - /incubator/public/trunk/site-publish/.htaccess
On 16 February 2012 10:12, wrote: > Author: francisdb > Date: Thu Feb 16 10:12:31 2012 > New Revision: 1244915 > > URL: http://svn.apache.org/viewvc?rev=1244915&view=rev > Log: > added redirect for empire-db > > Modified: > incubator/public/trunk/site-publish/.htaccess That won't last - you need to update the source file in site-author and regenerate. > > Modified: incubator/public/trunk/site-publish/.htaccess > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/.htaccess?rev=1244915&r1=1244914&r2=1244915&view=diff > == > --- incubator/public/trunk/site-publish/.htaccess (original) > +++ incubator/public/trunk/site-publish/.htaccess Thu Feb 16 10:12:31 2012 > @@ -16,6 +16,7 @@ RedirectMatch Permanent ^/deltacloud(.*) > RedirectMatch Permanent ^/derby(.*) http://db.apache.org/derby$1 > RedirectMatch Permanent ^/directory(.*) http://directory.apache.org$1 > RedirectMatch Permanent ^/esme(.*) http://esme.apache.org$1 > +RedirectMatch Permanent ^/empire-db(.*) http://empire-db.apache.org$1 > RedirectMatch Permanent ^/felix(.*) http://felix.apache.org$1 > RedirectMatch Permanent ^/ftpserver(.*) http://mina.apache.org/ftpserver$1 > RedirectMatch Permanent ^/geronimo(.*) http://geronimo.apache.org$1 > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1244240 - /incubator/public/trunk/build_cms.sh
On 15 February 2012 13:15, Joe Schaefer wrote: > - Original Message - > >> From: sebb >> To: Joe Schaefer >> Cc: "general@incubator.apache.org" >> Sent: Wednesday, February 15, 2012 5:59 AM >> Subject: Re: svn commit: r1244240 - /incubator/public/trunk/build_cms.sh >> >> On 15 February 2012 02:18, Joe Schaefer wrote: >>> >>> >>> >>> >>> - Original Message - From: sebb To: Joe Schaefer Cc: "general@incubator.apache.org" >> Sent: Tuesday, February 14, 2012 9:11 PM Subject: Re: svn commit: r1244240 - >> /incubator/public/trunk/build_cms.sh On 15 February 2012 01:49, Joe Schaefer >> wrote: > - Original Message - > >> From: sebb >> To: general@incubator.apache.org; Joe Schaefer >> Cc: >> Sent: Tuesday, February 14, 2012 8:40 PM >> Subject: Re: svn commit: r1244240 - /incubator/public/trunk/build_cms.sh >> >> On 15 February 2012 01:30, Joe Schaefer >> wrote: >>> The documentation is in the caller script sebb. >> >> Yes, but how can one find the calling script from the build >> script? > > If you have problems with the level of detail provided in the >> script comments, > please feel free to add your own commentary. > >> BTW, if the script is run at the moment, it will cause >> problems. > > Well with svn 1.7 those problems have been outlined elsethread. >> Hopefully > we will have those resolved by the time the cms host is upgraded. I meant that until snvpubsub is implemented, running the script will cause problems, as it starts by deleting part of the workspace I've just realised that it may also cause problems for the Ant >> build, as I don't think that expects to create any missing directories. The script should probably just delete files. >>> >>> I sure hope not. There is no good reason to expose this level of >>> site structure micromangement to build system users. If ant doesn't >>> know how to recreate the site starting from an empty site-publish >>> dir, let's move the conversation to dev@ant to try and fix ant. >> >> It's the build script that will need fixing (if necessary), not Ant itself. >> >> It may be OK already; it may not. > > It only takes about a minute to test this sebb, could you please look > into this? All you have to do to restore your working copy is to > nuke the publish-site tree again post-build and run svn up, even with svn 1.6, > so really it's no big deal to try it out and see. Seems to be OK. Can also use docs.dest to redirect the output: ant -Ddocs.dest=target > - > 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
[jira] [Resolved] (INCUBATOR-119) site-publish/ip-clearance/lucene-kuromoji.html does not seem to build correctly
[ https://issues.apache.org/jira/browse/INCUBATOR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved INCUBATOR-119. Resolution: Fixed Caused by the fixEOL step; fixed by adding encoding="UTF-8" > site-publish/ip-clearance/lucene-kuromoji.html does not seem to build > correctly > --- > > Key: INCUBATOR-119 > URL: https://issues.apache.org/jira/browse/INCUBATOR-119 > Project: Incubator > Issue Type: Bug > Components: site > Environment: WinXP/SP3 > Apache Ant(TM) version 1.8.2 compiled on December 20 2010 >Reporter: Sebb >Priority: Minor > > If I delete the file site-publish/ip-clearance/lucene-kuromoji.html and > rebuild the site, the generated file has differences from the original. > Looks like there might be an encoding issue to sort out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Hama 0.4-incubating RC6
On 20 February 2012 13:54, Edward J. Yoon wrote: > Hi, > > I've create RC6 for the Apache Hama 0.4-incubating release. This fixes > the license header issue and adds rat-plugin. > > Signing KEYS: > http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/files/KEYS > Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ There are no hashes (MD5 or SHA1). AIUI these are required. No need to respin the release, but please create the hashes. > Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ > NOTICE.txt: > http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt > LICENSE.txt: > http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt > Staging website: http://people.apache.org/~edwardyoon/site/ > > You can run the "mvn apache-rat:check" command to check for license headers. > > I tested this RC6 builds, single mode, and distributed mode on my 16 > nodes cluster and 5 VMs with EC2. > > Please retry, check signatures, licenses, and vote! > > I hope this will be a final, and +1. > > Thanks. > -- > Best Regards, Edward J. Yoon > @eddieyoon > > - > 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
[jira] [Commented] (INCUBATOR-120) Are the following files still needed in site-publish?
[ https://issues.apache.org/jira/browse/INCUBATOR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212311#comment-13212311 ] Sebb commented on INCUBATOR-120: site-publish\projects\geronimo-proposal.html does have a source file at site-author\projects\geronimo-proposal.xml and is to be kept. Other files deleted as per http://mail-archives.apache.org/mod_mbox/incubator-general/201202.mbox/%3CCAOFYJNYOhw61D9brp3Oozj6M9b2hektDMJKsPu28yJWw47QJqw%40mail.gmail.com%3E > Are the following files still needed in site-publish? > - > > Key: INCUBATOR-120 > URL: https://issues.apache.org/jira/browse/INCUBATOR-120 > Project: Incubator > Issue Type: Bug > Components: site >Reporter: Sebb >Priority: Blocker > > [This is listed as a blocker because it's not possible to move to > svnpubsub/CMS until resolved.] > The following files in site-publish have no sources in site-author: > The entire tree under: > site-publish/projects/altrmi/ > Looks like it should be deleted, as the project has gone away. > Also the following individual files have no means to recreate them: > ! 1243649 site-publish\projects\geronimo\status.html > ! 1243649 site-publish\projects\geronimo\status.pdf > ! 1243649 site-publish\projects\lcf.html > ! 1243649 site-publish\projects\geronimo-proposal.html > ! 1243649 site-publish\projects\ruper.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Resolved] (INCUBATOR-120) Are the following files still needed in site-publish?
[ https://issues.apache.org/jira/browse/INCUBATOR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved INCUBATOR-120. Resolution: Fixed > Are the following files still needed in site-publish? > - > > Key: INCUBATOR-120 > URL: https://issues.apache.org/jira/browse/INCUBATOR-120 > Project: Incubator > Issue Type: Bug > Components: site >Reporter: Sebb >Priority: Blocker > > [This is listed as a blocker because it's not possible to move to > svnpubsub/CMS until resolved.] > The following files in site-publish have no sources in site-author: > The entire tree under: > site-publish/projects/altrmi/ > Looks like it should be deleted, as the project has gone away. > Also the following individual files have no means to recreate them: > ! 1243649 site-publish\projects\geronimo\status.html > ! 1243649 site-publish\projects\geronimo\status.pdf > ! 1243649 site-publish\projects\lcf.html > ! 1243649 site-publish\projects\geronimo-proposal.html > ! 1243649 site-publish\projects\ruper.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: migrating the main site to the CMS- a simple approach
On 15 February 2012 15:44, Jukka Zitting wrote: > Hi, > > On Wed, Feb 15, 2012 at 1:59 AM, sebb wrote: >> The first thing to do is to decide if the following directory tree can >> be junked: >> >> site-publish/projects/altrmi/ >> >> I suspect it can, as altrmi has moved elsewhere, but I just want to >> check it's not being kept for historical reasons. > > +1 to removing. We still have the content archived in svn history. Done >> The other files currently only in site-publish are: >> >> ! 1243649 site-publish\projects\geronimo\status.html >> ! 1243649 site-publish\projects\geronimo\status.pdf > > Remove. Geronimo status is at /projects/geronimo.html. Done >> ! 1243649 site-publish\projects\lcf.html > > Remove. LCF renamed itself to ManifoldCF, and its status is now at > /projects/manifoldcf.html. Done >> ! 1243649 site-publish\projects\geronimo-proposal.html > > Keep. It should be linked to from the proposal list on the Incubator > wiki, or perhaps migrated entirely into the wiki (or at least to a > better place in site-author). Not sure why that file was flagged as a problem by my testing - there is a source file for it under site-author. >> ! 1243649 site-publish\projects\ruper.html > > Remove. AFAICT, Ruper renamed itself to Depot, and its status is now > at /projects/depot.html. Done. > BR, > > Jukka Zitting > > - > 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
[jira] [Resolved] (INCUBATOR-118) Are the altrmi files still needed? If so, should they be moved elsewhere?
[ https://issues.apache.org/jira/browse/INCUBATOR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved INCUBATOR-118. Resolution: Fixed Removed altrmi files > Are the altrmi files still needed? If so, should they be moved elsewhere? > - > > Key: INCUBATOR-118 > URL: https://issues.apache.org/jira/browse/INCUBATOR-118 > Project: Incubator > Issue Type: Bug > Components: site >Reporter: Sebb > > There is a large directory tree in the Incubator-public SVN containing the > site for the podling AltRMI which is no longer with the ASF. > See > http://svn.apache.org/repos/asf/incubator/public/trunk/site-publish/projects/altrmi > and > http://incubator.apache.org/projects/altrmi/ > Seems to me the only AltRMI file we should keep is the podling status, i.e. > http://incubator.apache.org/projects/altrmi.html > However, if the files are still to be kept, do they really belong on the > Incubator public website? > Would it not be more appropriate to store them elsewhere and make them > read-only? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-120) Are the following files still needed in site-publish?
[ https://issues.apache.org/jira/browse/INCUBATOR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212303#comment-13212303 ] Sebb commented on INCUBATOR-120: altrmi files dropped as per INCUBATOR-118 > Are the following files still needed in site-publish? > - > > Key: INCUBATOR-120 > URL: https://issues.apache.org/jira/browse/INCUBATOR-120 > Project: Incubator > Issue Type: Bug > Components: site >Reporter: Sebb >Priority: Blocker > > [This is listed as a blocker because it's not possible to move to > svnpubsub/CMS until resolved.] > The following files in site-publish have no sources in site-author: > The entire tree under: > site-publish/projects/altrmi/ > Looks like it should be deleted, as the project has gone away. > Also the following individual files have no means to recreate them: > ! 1243649 site-publish\projects\geronimo\status.html > ! 1243649 site-publish\projects\geronimo\status.pdf > ! 1243649 site-publish\projects\lcf.html > ! 1243649 site-publish\projects\geronimo-proposal.html > ! 1243649 site-publish\projects\ruper.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Lucy as TLP
On Sat, Feb 18, 2012 at 11:31:12PM -0600, Peter Karman wrote: > The Apache Lucy community has voted[0] to graduate. We now ask that the IPMC > vote on recommending this resolution (included below) to the ASF Board. As a member of the Incubator PMC, I will abstain from this VOTE. The IPMC is charged with overseeing podlings, and in my view a potential conflict of interest exists on a vote to recommend that Lucy become an Apache TLP between that oversight role and my personal investment in the success of Lucy as a project. (Notably, my current employer pays me to work on Lucy). An earlier VOTE was held on the Lucy developer's list in which I participated as a member of the Lucy PPMC; I continue to stand behind my vote in that context. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Oozie 3.1.3 (candidate 2)
+1 (non-binding from a user). Downloaded sources and ran bin/mkdistro.sh 2 times. All tests went through fine no my RHEL 5.x Deployed the distro using oozie-setup.sh on a single node un-secure Hadoop 20.205 cluster and launched a co-ordinator with about 20+ workflows. All workflows completed as expected. Thanks for all the hard work, -Thiruvel On 2/20/12 3:19 AM, "Mohamed Battisha" wrote: >+1 >Downloaded the source and ran the unit test > >Everything looks fine > >Thanks! >Mohamed > >On Feb 18, 2012, at 2:54 PM, Jeremy Hanna wrote: > >> +1 (non-binding from a user/contributor) - pulled down the artifacts >>and did the maven tests on them. Got it to complete, but on one of the >>test runs I got test failures for TestPauseTransitService and >>TestSshActionExecutor. I think those may need to just be looked at for >>completion consistency and not anything to do with the code their >>testing. >> >> On Feb 17, 2012, at 1:59 PM, Mayank Bansal wrote: >> >>> +1 >>> >>> looks good. >>> >>> Thanks, >>> Mayank >>> >>> On Fri, Feb 17, 2012 at 3:38 AM, Chris Douglas >>>wrote: >>> On Fri, Feb 17, 2012 at 12:50 AM, Mohammad Islam wrote: > Hi Chris, > So can the other contributors/committers VOTE now? Yes > As oozie-user VOTE is already closed, what would be the best option >at this stage? > 1. Go to genenral@incubator and vote there. > 2. Vote in the same threadat oozie-user Might as well show support/express reservations on the general@incubator thread so it's in one place. IIRC the general@ thread cc'd oozie-dev. -C > Regards, > Mohammad > > > > From: Chris Douglas > To: oozie-...@incubator.apache.org > Cc: Mohammad Islam ; " oozie-us...@incubator.apache.org" > Sent: Thursday, February 16, 2012 11:13 PM > Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) > > That's a pretty dire error in the documentation if that's the > impression. Projects (and podlings) are responsible for their code, > community, and releases. The PPMC certifies that the artifact > represents an iteration of its progress by voting on a release in >some > series, just as a PMC does. > > The IPMC has a functionary, mundane role. It's supposed to make > cursory checks: code being released respects the licensing > requirements of dependencies, notices give accurate guidance to > downstream consumers of that code, etc. Since the ASF is releasing > that code under license, the idea is that IPMC members protect the > foundation from common misunderstandings (e.g. if a podling thought > they could release GPL'd code, someone else's code, etc.). > > Once the project has some experience with releases, a clear > understanding of what the ASF wants w.r.t. community, etc. then > podling graduates. Before that, the voting guidelines are necessary > because the IPMC members are acting on behalf of the foundation. The > vote from the PPMC expresses that the artifact represents their > output. The vote from the IPMC certifies that the artifact won't get > the ASF into legal trouble. > > Release votes are a strict majority per ASF bylaws. AFAICT, asserting > that the IPMC votes are the only ones that are binding in the second > round is just adding a layer of indirection to solve a counting > problem. -C > > On Thu, Feb 16, 2012 at 9:22 PM, Alejandro Abdelnur > wrote: >> Chris, >> >> I'm a bit confused here, I've thought that the significant votes >>where from >> the IPMC. >> >> I guess most of the committers/contributors thought along the same lines. >> >> Thxs. >> >> Alejandro >> >> On Thu, Feb 16, 2012 at 5:39 PM, Chris Douglas wrote: >> >>> The vote didn't attract any votes from contributors. As far as I >>>know, >>> none of the voters in this thread actually develop Oozie. >>> >>> The IPMC vote is a check on the podling's compliance with licensing >>> and other foundation-level practices. It's far, far less >>>significant >>> than the community's appraisal of the release itself. Would the >>>PPMC >>> please weigh in? -C >>> >>> On Thu, Feb 16, 2012 at 2:47 PM, Mohammad Islam >>> >>> wrote: Hi All, As 72 hours has passed, I would like to close the vote. The proposed RC-2 got three +1s from three mentors without -1 or 0. Special thanks to mentors who gave their valuable feedback to make it >>> better. I also want to mention Alejandro and Virag who helped to make the whole >>> process smoother. Now I will ask for vote in general@incubator Regards, Moahmmad ___
[RESULT][VOTE] Release Apache Wookie 0.9.2-incubating (General Incubation List)
The vote has now closed. We had already received 2 IPMC +1 votes (plus an additional 3 PPMC +1 votes) during the release voting on wookie-dev. We now have 1 additional IPMC vote (3 in total). Results: IPMC Members/Mentors: +1 [3] 0 [0] -1 [0] PPMC Members: +1 [3] 0 [0] -1 [0] The vote is successful Voting Record: Scott Wilson: +1 (w) Kris Popat: +1 (w) Raido Kuli: +1 (w) **Ate Douma: +1 (w) **Ross Gardler: +1 (w) **Andrew Savory: +1 (g) (**Denotes a Wookie Mentor/IPMC member) (g) Denotes a vote from the general incubator list (w) Denotes a vote from the wookie-dev incubator list On 17/02/2012 11:52, Paul Sharples wrote: This is the third incubator release for Apache Wookie, with the artifacts being versioned as 0.9.2-incubating. We have already received 2 IPMC +1 votes (plus an additional 3 PPMC +1 votes) during the release voting on wookie-dev. (We need one more IPMC vote) Vote thread: http://incubator.markmail.org/search/?q=wookie-dev+date%3A201202+#query:wookie-dev%20date%3A201202%20+page:1+mid:a7dmraqgu2kcdruq+state:results Result: http://incubator.markmail.org/search/?q=wookie-dev+date%3A201202+#query:wookie-dev%20date%3A201202%20+page:1+mid:avlcw6uj6e7s5mv5+state:results Svn source tag: https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.2-incubating/ Release notes: https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.2-incubating/RELEASE_NOTES Release artifacts: http://people.apache.org/~psharples/wookie/staging-area/0.9.2-incubating Maven artifacts https://repository.apache.org/content/repositories/orgapachewookie-005/ PGP release keys: https://svn.apache.org/repos/asf/incubator/wookie/KEYS 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
[VOTE] Release Apache Hama 0.4-incubating RC6
Hi, I've create RC6 for the Apache Hama 0.4-incubating release. This fixes the license header issue and adds rat-plugin. Signing KEYS: http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/files/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ NOTICE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt Staging website: http://people.apache.org/~edwardyoon/site/ You can run the "mvn apache-rat:check" command to check for license headers. I tested this RC6 builds, single mode, and distributed mode on my 16 nodes cluster and 5 VMs with EC2. Please retry, check signatures, licenses, and vote! I hope this will be a final, and +1. Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Lucy as TLP
+1 (binding) Mike Sent from my iPad On Feb 19, 2012, at 12:31 AM, Peter Karman wrote: > The Apache Lucy community has voted[0] to graduate. We now ask that the IPMC > vote on recommending this resolution (included below) to the ASF Board. > > Please cast your vote: > [ ] +1 yes, I recommend Lucy's graduation > [ ] 0 > [ ] -1 no, don't recommend yet, because... > > > cheers, > pek > > > [0] http://s.apache.org/KUX > > From http://wiki.apache.org/lucy/LucyCharter > > X. Establish the Apache Lucy Project > > WHEREAS, the Board of Directors deems it to be in the best > interests of the Foundation and consistent with the > Foundation's purpose to establish a Project Management > Committee charged with the creation and maintenance of > open source software related to providing full-text search > for dynamic programming languages for distribution at no > charge to the public. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Lucy Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that the Apache Lucy Project be and hereby is > responsible for the creation and maintenance of software > related to providing full-text search for dynamic programming > languages; and be it further > > RESOLVED, that the office of "Vice President, Apache Lucy" be > and hereby is created, the person holding such office to > serve at the direction of the Board of Directors as the chair > of the Apache Lucy Project, and to have primary responsibility > for management of the projects within the scope of > responsibility of the Apache Lucy Project; and be it further > > RESOLVED, that the persons listed immediately below be and > hereby are appointed to serve as the initial members of the > Apache Lucy Project: > > * Logan Bell > * Brad C. Harder > * Marvin Humphrey > * Peter Karman > * Nathan Kurz > * Dan Markham > * Mike McCandless > * Joe Schaefer > * Upayavira > * David E. Wheeler > * Nick Wellnhofer > * Simon Willnauer > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Peter Karman > be appointed to the office of Vice President, Apache Lucy, to > serve in accordance with and subject to the direction of the > Board of Directors and the Bylaws of the Foundation until > death, resignation, retirement, removal or disqualification, > or until a successor is appointed; and be it further > > RESOLVED, that the initial Apache Lucy PMC be and hereby is > tasked with the creation of a set of bylaws intended to > encourage open development and increased participation in the > Apache Lucy Project; and be it further > > RESOLVED, that the Apache Lucy Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator Lucy podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator Lucy podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > > > > > > -- > Peter Karman . http://peknet.com/ . pe...@peknet.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
Re: [VOTE] Release Oozie 3.1.3 (candidate 2)
+1 Downloaded the source and ran the unit tests Things look fine Thanks! Mohamed On Feb 17, 2012, at 11:59 AM, Mayank Bansal wrote: > +1 > > looks good. > > Thanks, > Mayank > > On Fri, Feb 17, 2012 at 3:38 AM, Chris Douglas wrote: > >> On Fri, Feb 17, 2012 at 12:50 AM, Mohammad Islam >> wrote: >>> Hi Chris, >>> So can the other contributors/committers VOTE now? >> >> Yes >> >>> As oozie-user VOTE is already closed, what would be the best option at >> this stage? >>> 1. Go to genenral@incubator and vote there. >>> 2. Vote in the same threadat oozie-user >> >> Might as well show support/express reservations on the >> general@incubator thread so it's in one place. IIRC the general@ >> thread cc'd oozie-dev. -C >> >>> Regards, >>> Mohammad >>> >>> >>> >>> From: Chris Douglas >>> To: oozie-...@incubator.apache.org >>> Cc: Mohammad Islam ; " >> oozie-us...@incubator.apache.org" >>> Sent: Thursday, February 16, 2012 11:13 PM >>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) >>> >>> That's a pretty dire error in the documentation if that's the >>> impression. Projects (and podlings) are responsible for their code, >>> community, and releases. The PPMC certifies that the artifact >>> represents an iteration of its progress by voting on a release in some >>> series, just as a PMC does. >>> >>> The IPMC has a functionary, mundane role. It's supposed to make >>> cursory checks: code being released respects the licensing >>> requirements of dependencies, notices give accurate guidance to >>> downstream consumers of that code, etc. Since the ASF is releasing >>> that code under license, the idea is that IPMC members protect the >>> foundation from common misunderstandings (e.g. if a podling thought >>> they could release GPL'd code, someone else's code, etc.). >>> >>> Once the project has some experience with releases, a clear >>> understanding of what the ASF wants w.r.t. community, etc. then >>> podling graduates. Before that, the voting guidelines are necessary >>> because the IPMC members are acting on behalf of the foundation. The >>> vote from the PPMC expresses that the artifact represents their >>> output. The vote from the IPMC certifies that the artifact won't get >>> the ASF into legal trouble. >>> >>> Release votes are a strict majority per ASF bylaws. AFAICT, asserting >>> that the IPMC votes are the only ones that are binding in the second >>> round is just adding a layer of indirection to solve a counting >>> problem. -C >>> >>> On Thu, Feb 16, 2012 at 9:22 PM, Alejandro Abdelnur >> wrote: Chris, I'm a bit confused here, I've thought that the significant votes where >> from the IPMC. I guess most of the committers/contributors thought along the same >> lines. Thxs. Alejandro On Thu, Feb 16, 2012 at 5:39 PM, Chris Douglas >> wrote: > The vote didn't attract any votes from contributors. As far as I know, > none of the voters in this thread actually develop Oozie. > > The IPMC vote is a check on the podling's compliance with licensing > and other foundation-level practices. It's far, far less significant > than the community's appraisal of the release itself. Would the PPMC > please weigh in? -C > > On Thu, Feb 16, 2012 at 2:47 PM, Mohammad Islam > wrote: >> Hi All, >> As 72 hours has passed, I would like to close the vote. >> The proposed RC-2 got three +1s from three mentors without -1 or 0. >> >> Special thanks to mentors who gave their valuable feedback to make it > better. >> I also want to mention Alejandro and Virag who helped to make the >> whole > process smoother. >> Now I will ask for vote in general@incubator >> >> Regards, >> Moahmmad >> >> >> >> From: Devaraj Das >> To: oozie-...@incubator.apache.org >> Cc: Oozie-users >> Sent: Tuesday, February 14, 2012 9:42 PM >> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) >> >> I ran the tests and also inspected the top level txt files. Looks >> good. >> >> +1 for the release. >> >> On Feb 13, 2012, at 4:43 PM, Mohammad Islam wrote: >> >>> Hi, >>> >>> Thanks everyone for giving valuable comments for the RC0 and RC1. >>> >>> I created a new candidate (RC2) build for Oozie-3.1.3 incorporating > most of the comments (including Chris's finding). >>> The following JIRAs were resolved based on the comments: >>> >>> OOZIE-694 Update the Install and Quick start guide with appropriate > hadoop versions for branch-3.1 (Mohammad) >>> OOZIE-602 Update the Hadoop version to be an Apache Hadoop version > (tucu) >>> OOZIE-689 XTestCase proxyuser settings fails with Hadoop >> 1.0.0/0.23.1 > (tucu) >>> OOZIE-601 Oozie's POMs should use org.apache.oozie as group (tucu) >>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 2)
+1 Downloaded the source and ran the unit test Everything looks fine Thanks! Mohamed On Feb 18, 2012, at 2:54 PM, Jeremy Hanna wrote: > +1 (non-binding from a user/contributor) - pulled down the artifacts and did > the maven tests on them. Got it to complete, but on one of the test runs I > got test failures for TestPauseTransitService and TestSshActionExecutor. I > think those may need to just be looked at for completion consistency and not > anything to do with the code their testing. > > On Feb 17, 2012, at 1:59 PM, Mayank Bansal wrote: > >> +1 >> >> looks good. >> >> Thanks, >> Mayank >> >> On Fri, Feb 17, 2012 at 3:38 AM, Chris Douglas wrote: >> >>> On Fri, Feb 17, 2012 at 12:50 AM, Mohammad Islam >>> wrote: Hi Chris, So can the other contributors/committers VOTE now? >>> >>> Yes >>> As oozie-user VOTE is already closed, what would be the best option at >>> this stage? 1. Go to genenral@incubator and vote there. 2. Vote in the same threadat oozie-user >>> >>> Might as well show support/express reservations on the >>> general@incubator thread so it's in one place. IIRC the general@ >>> thread cc'd oozie-dev. -C >>> Regards, Mohammad From: Chris Douglas To: oozie-...@incubator.apache.org Cc: Mohammad Islam ; " >>> oozie-us...@incubator.apache.org" Sent: Thursday, February 16, 2012 11:13 PM Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) That's a pretty dire error in the documentation if that's the impression. Projects (and podlings) are responsible for their code, community, and releases. The PPMC certifies that the artifact represents an iteration of its progress by voting on a release in some series, just as a PMC does. The IPMC has a functionary, mundane role. It's supposed to make cursory checks: code being released respects the licensing requirements of dependencies, notices give accurate guidance to downstream consumers of that code, etc. Since the ASF is releasing that code under license, the idea is that IPMC members protect the foundation from common misunderstandings (e.g. if a podling thought they could release GPL'd code, someone else's code, etc.). Once the project has some experience with releases, a clear understanding of what the ASF wants w.r.t. community, etc. then podling graduates. Before that, the voting guidelines are necessary because the IPMC members are acting on behalf of the foundation. The vote from the PPMC expresses that the artifact represents their output. The vote from the IPMC certifies that the artifact won't get the ASF into legal trouble. Release votes are a strict majority per ASF bylaws. AFAICT, asserting that the IPMC votes are the only ones that are binding in the second round is just adding a layer of indirection to solve a counting problem. -C On Thu, Feb 16, 2012 at 9:22 PM, Alejandro Abdelnur >>> wrote: > Chris, > > I'm a bit confused here, I've thought that the significant votes where >>> from > the IPMC. > > I guess most of the committers/contributors thought along the same >>> lines. > > Thxs. > > Alejandro > > On Thu, Feb 16, 2012 at 5:39 PM, Chris Douglas >>> wrote: > >> The vote didn't attract any votes from contributors. As far as I know, >> none of the voters in this thread actually develop Oozie. >> >> The IPMC vote is a check on the podling's compliance with licensing >> and other foundation-level practices. It's far, far less significant >> than the community's appraisal of the release itself. Would the PPMC >> please weigh in? -C >> >> On Thu, Feb 16, 2012 at 2:47 PM, Mohammad Islam >> wrote: >>> Hi All, >>> As 72 hours has passed, I would like to close the vote. >>> The proposed RC-2 got three +1s from three mentors without -1 or 0. >>> >>> Special thanks to mentors who gave their valuable feedback to make it >> better. >>> I also want to mention Alejandro and Virag who helped to make the >>> whole >> process smoother. >>> Now I will ask for vote in general@incubator >>> >>> Regards, >>> Moahmmad >>> >>> >>> >>> From: Devaraj Das >>> To: oozie-...@incubator.apache.org >>> Cc: Oozie-users >>> Sent: Tuesday, February 14, 2012 9:42 PM >>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) >>> >>> I ran the tests and also inspected the top level txt files. Looks >>> good. >>> >>> +1 for the release. >>> >>> On Feb 13, 2012, at 4:43 PM, Mohammad Islam wrote: >>> Hi, Thanks everyone for giving valuable comments for the RC0 and RC1. I created a new candidate (RC2) buil
