Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

[Ian Dunlop]

Hello,

TL/DR +1 (non-binding).

So I had a go at running toree & jupyter from the artifacts and it all
seems ok although there were a couple of things I noticed.

I downloaded toree-pip from
https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/ since
that is what the original vote thread suggests
(https://lists.apache.org/thread.html/493874de453d9ccbdbc3aecc2f527dea6af82d657104732d726e07f9@%3Cdev.toree.apache.org%3E)rather
than attempting to build from source. I did try to build the source from
https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/toree-src/apache-toree-0.1.0-incubating-source-release.tar.gz

but 'make release' resulted in "fatal: Not a git repository (or any
parent up to mount point /home/ian)". I then git cloned the repo from
github and tried again. This resulted in "/bin/sh: 1: sbt: not found
". I have no idea what sbt is and the readme at
https://github.com/apache/incubator-toree didn't help.

It would be worth mentioning the spark install process via
http://spark.apache.org/downloads.html. I just downloaded the suggested
1.6.x version (1.6.3 in fact), unzipped it and placed it in my home
directory and used that as spark_home for the jupyter toree install
part. Would probably be a good idea if the email to general included as
much info as the original vote thread.

I'm also not sure what I'm supposed to do with
https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/toree-pip/apache_toree.egg-info/


I checked the md5 and sha512 sums for all the artifacts and they match.

I'll give it a +1 (non-binding) since it seems to work and the sums are
ok but maybe a bit more is needed in the docs to help people build it
from source.

Cheers,

Ian


On 16/01/17 19:36, Luciano Resende wrote:
> It's ok, let's concentrate on getting the reviews done and 3 required
> binding votes from IPMC members.
>
> On Mon, Jan 16, 2017 at 10:57 AM, Chip Senkbeil <chip.senkb...@gmail.com>
> wrote:
>
>> Can't tell if my other mail got through. Do I need to open a new thread to
>> indicate that the vote stays open for more than 72 hours? Or is it okay to
>> make that statement here and keep this thread open?
>>
>> On Mon, Jan 16, 2017 at 11:19 AM Ian Dunlop <ianwdun...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I wonder if it would be better to say
>>>
>>> "The vote is open for *at least* 72 hours " (ie will not be closed until
>>> at least 72 hours have passed)
>>>
>>> rather than
>>>
>>> "The vote is open for 72 hours " (ie will definitely be closed in 72
>> hours
>>> regardless of votes)
>>>
>>> The first version means that you have the option to keep the vote open
>>> after the 72 hours have passed in case you don't have enough votes
>> gathered.
>>> Cheers,
>>>
>>> Ian
>>>
>>>
>>> On 16/01/17 15:34, Luciano Resende wrote:
>>>
>>> Bringing up my +1 from dev list.
>>>
>>> On Fri, Jan 13, 2017 at 2:43 PM, Chip Senkbeil <chip.senkb...@gmail.com>
>> <chip.senkb...@gmail.com>
>>> wrote:
>>>
>>>
>>> Please vote on releasing the following candidate as Apache Toree
>>> (incubating) version 0.1.0.
>>>
>>> A vote on this release has passed within the Toree PPMC.
>>>
>>> PPMC vote result thread:https://lists.apache.org/thread.html/
>> 5589e9b729333b0d95ccea639fcacf
>>> 03fdc3d9480aaeb8e80399ad35@
>>> 
>>>
>>> PPMC vote thread:https://lists.apache.org/thread.html/
>> 493874de453d9ccbdbc3aecc2f527d
>>> ea6af82d657104732d726e07f9@
>>> 
>>>
>>> The tag to be voted on is v0.1.0-rc4
>>> (1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located here:
>> https://github.com/apache/incubator-toree/commit/
>>> 1d526954ecaba1d5dc0f40ec555dd598b2b11df7
>>>
>>> All distribution packages, including signatures, digests, etc. can be
>> found
>>> at:https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/
>>>
>>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/chipsenkbeil.asc
>>> The list of keys associated with Toree is available at:
>> https://people.apache.org/keys/group/toree.asc
>>> Staging artifacts can be found at:https://repository.apache.
>> org/content/repositories/orgapachetoree-1002/
>>> Please vote on releasing this package as Apache Toree 0.1.0-incubating!
>>>
>>> The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
>>> and passes if a majority of at least 3 +1 IPMC votes are cast.
>>>
>>> [ ] +1 Release this package as Apache Toree 0.1.0-incubating
>>> [ ] -1 Do not release this package because ...
>>>
>>> To learn more about Apache Toree, please seehttp://toree.incubator.
>> apache.org/
>>>
>>>
>>>
>>>
>
>




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Impala 2.8.0 release candidate 1

[Ian Dunlop]

Hello,

Thanks Jim. I hadn't realised that I needed to download the apache-rat
jar (I got it from Maven
https://mvnrepository.com/artifact/org.apache.rat/apache-rat/0.12). I
also had to clone the impala repo from github to create the git archive
since the archive available from
https://dist.apache.org/repos/dist/dev/incubator/impala/2.8.0/RC1/
doesn't seem to have the .git directory needed. After doing this the rat
check passed with an 'OK'.

So it is definitely a +1 (non-binding).

Cheers,

Ian

On 16/01/17 21:14, Jim Apple wrote:
> Thank you for taking the time to check the artifact and vote.
>
>> I didn't RAT check because I didn't have a rat.xml to use the script
>> against and I wasn't sure how to create one.
> bin/check-rat-report.py describes, on lines 28-30, how to run it,
> including how to create rat.xml.
>
>> Also the build uses a lot of bandwidth and takes quite some time. Might
>> be worth pointing that out.
> Good point. bin/bootstrap_build.sh takes 30-45 minutes on an ec2
> c3xlarge instance, which voters can read about (in order to compare it
> to their build machines) here:
> https://aws.amazon.com/ec2/instance-types/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

[Ian Dunlop]

Hello,

I wonder if it would be better to say

"The vote is open for _at least_ 72 hours " (ie will not be closed until
at least 72 hours have passed)

rather than

"The vote is open for 72 hours " (ie will definitely be closed in 72
hours regardless of votes)

The first version means that you have the option to keep the vote open
after the 72 hours have passed in case you don't have enough votes gathered.


Cheers,

Ian

On 16/01/17 15:34, Luciano Resende wrote:
> Bringing up my +1 from dev list.
>
> On Fri, Jan 13, 2017 at 2:43 PM, Chip Senkbeil 
> wrote:
>
>> Please vote on releasing the following candidate as Apache Toree
>> (incubating) version 0.1.0.
>>
>> A vote on this release has passed within the Toree PPMC.
>>
>> PPMC vote result thread:
>> https://lists.apache.org/thread.html/5589e9b729333b0d95ccea639fcacf
>> 03fdc3d9480aaeb8e80399ad35@
>> 
>>
>> PPMC vote thread:
>> https://lists.apache.org/thread.html/493874de453d9ccbdbc3aecc2f527d
>> ea6af82d657104732d726e07f9@
>> 
>>
>> The tag to be voted on is v0.1.0-rc4
>> (1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located here:
>> https://github.com/apache/incubator-toree/commit/
>> 1d526954ecaba1d5dc0f40ec555dd598b2b11df7
>>
>> All distribution packages, including signatures, digests, etc. can be found
>> at:
>> https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/chipsenkbeil.asc
>>
>> The list of keys associated with Toree is available at:
>> https://people.apache.org/keys/group/toree.asc
>>
>> Staging artifacts can be found at:
>> https://repository.apache.org/content/repositories/orgapachetoree-1002/
>>
>> Please vote on releasing this package as Apache Toree 0.1.0-incubating!
>>
>> The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
>> and passes if a majority of at least 3 +1 IPMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Toree 0.1.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Toree, please see
>> http://toree.incubator.apache.org/
>>
>
>



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Impala 2.8.0 release candidate 1

[Ian Dunlop]

Hello,

+1

I checked:

MD5 sum

SHA1 sum

build

I didn't RAT check because I didn't have a rat.xml to use the script
against and I wasn't sure how to create one.

Note. Build passed but complained slightly:

cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for
C/ObjC but not for C++
sasl/saslwrapper.cpp: In member function ‘bool
saslwrapper::ClientImpl::init()’:
sasl/saslwrapper.cpp:89:9: warning: unused variable ‘cbIndex’
[-Wunused-variable]
 int cbIndex = 0;
 ^
sasl/saslwrapper.cpp: In member function ‘void
saslwrapper::ClientImpl::interact(sasl_interact_t*)’:
sasl/saslwrapper.cpp:319:11: warning: unused variable ‘input’
[-Wunused-variable]
 char* input;
   ^
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for
C/ObjC but not for C++


Also the build uses a lot of bandwidth and takes quite some time. Might
be worth pointing that out.

Cheers,

Ian


On 12/01/17 15:57, Jim Apple wrote:
> Impala 2.8.0 release candidate 1 has passed a PPMC vote; this email is
> a call for an IPMC vote.
>
> The PPMC vote thread is:
>
> https://lists.apache.org/thread.html/f873d0f82f0619d7d9a18440a74ea2961e63e4db0c5216a9d08b6517@%3Cdev.impala.apache.org%3E
>
> http://mail-archives.apache.org/mod_mbox/impala-dev/201701.mbox/%3CCAC-pSX2TG7z6L8qWP9NjmonJfmUfTD_xxHs-YH44C--3aaPFUQ%40mail.gmail.com%3E
>
> The vote result thread is:
>
> https://lists.apache.org/thread.html/856ea124d95b58f251f2737955bd70b1160d29d9c3dd960e1bb90cea@%3Cdev.impala.apache.org%3E
>
>  The artifacts for testing are at
> .
> That is git tag 2.8.0-rc1, tree hash
> cc8de358d5c64778d171ad47aa6b513d437ac4b0, visible at
> .
>
> The KEYS are at 
> .
>
> To run RAT, follow the instructions in bin/check-rat-report.py. To
> build, follow the instructions in bin/bootstrap_build.sh.
>
> One of the binding votes from the PPMC was Tom White, who is one of
> our mentors and an IPMC member.
>
> This vote will be open for at least 72 hours, or until the necessary
> number of votes (3 +1) is reached.
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>




signature.asc
Description: OpenPGP digital signature

Re: www.incubator.apache.org goes to apache.org

[Ian Dunlop]

Hello,

You could probably raise an issue on Infrastructure via
https://issues.apache.org/jira/secure/Dashboard.jspa to take care of this.

Cheers,

Ian

On 30/11/16 15:17, Benjamin Young wrote:
> This matters because Yahoo! searches (at least) for "apache incubator" pull 
> up `www.incubator.apache.org` rhater than `incubator.apache.org`. The result 
> being that people get lost when looking for the incubator.
>
> Proposed Action:
>  - setup `www.incubator.apache.org` => incubator.apache.org redirect
>
> Cheers!
> Benjamin
>  --
>  http://bigbluehat.com/
>  http://linkedin.com/in/benjaminyoung
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>




signature.asc
Description: OpenPGP digital signature

Re: Github tagging, was Re: [VOTE] Release Apache Joshua 6.1 RC#2

[Ian Dunlop]

Hello,

Isn't the only official release via www.apache.org/dist
(http://www.apache.org/dev/release.html#where-do-releases-go) so the
fact that github does anything with tags is just a side issue?

I think the whole github mirror is just a very handy convenience for
forks/pulls and public visibility. Makes life easier for everyone. If
github want to mark things as 'github' releases then it's a small price
to pay.

Cheers,

Ian


On 29/11/16 20:45, Jim Apple wrote:
>> You can just make the release on a branch rather than in a fork/mirror.
> This is what Impala did and Github still happily treats those
> off-master-branch tags as "releases".
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>




signature.asc
Description: OpenPGP digital signature

Trademark registration

[Ian Dunlop]

Hello,

I saw the following on trademark registrations
http://www.apache.org/foundation/marks/register#register and wondered if
this was possible for incubator projects or only for those which have
graduated. Any ideas?

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature

Re: ASF Android release policy

[Ian Dunlop]

Hello,

Infra have done a lot of the work on this now. They needed an ASF email
address to act as the release manager so I have used mine. We'll see how it
goes.

Cheers,

Ian

On 16 September 2016 at 09:43, Ian Dunlop <ianwdun...@gmail.com> wrote:

> Hello,
>
> Thanks for all the advice. I have created https://issues.apache.
> org/jira/browse/INFRA-12614 to ask for an ASF Google play account.
>
> Cheers,
>
> Ian
>
> On 13 September 2016 at 16:01, David Nalley <da...@gnsa.us> wrote:
>
>> On Tue, Sep 13, 2016 at 4:49 AM, Ian Dunlop <ianwdun...@gmail.com> wrote:
>> > Hello,
>> >
>> > In the Taverna Incubator project we have been developing an Android
>> mobile
>> > app which is almost ready for a first release. Are there any ASF
>> procedures
>> > and policies for doing an Android release? Can an ASF based Android app
>> be
>> > released into the Google play store (or others)?
>> >
>>
>> We've signed up to be able to push IOS apps, so at least in principle
>> nothing that prohibits that. I do not believe we've signed up for
>> Google Play or Amazon stores, and we'd need to look at the T
>> associated with that and look at the mechanics.
>>
>> --David
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Re: ASF Android release policy

[Ian Dunlop]

Hello,

Thanks for all the advice. I have created
https://issues.apache.org/jira/browse/INFRA-12614 to ask for an ASF Google
play account.

Cheers,

Ian

On 13 September 2016 at 16:01, David Nalley <da...@gnsa.us> wrote:

> On Tue, Sep 13, 2016 at 4:49 AM, Ian Dunlop <ianwdun...@gmail.com> wrote:
> > Hello,
> >
> > In the Taverna Incubator project we have been developing an Android
> mobile
> > app which is almost ready for a first release. Are there any ASF
> procedures
> > and policies for doing an Android release? Can an ASF based Android app
> be
> > released into the Google play store (or others)?
> >
>
> We've signed up to be able to push IOS apps, so at least in principle
> nothing that prohibits that. I do not believe we've signed up for
> Google Play or Amazon stores, and we'd need to look at the T
> associated with that and look at the mechanics.
>
> --David
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

ASF Android release policy

[Ian Dunlop]

Hello,

In the Taverna Incubator project we have been developing an Android mobile
app which is almost ready for a first release. Are there any ASF procedures
and policies for doing an Android release? Can an ASF based Android app be
released into the Google play store (or others)?

Cheers,

Ian

Re: [VOTE] Release of Apache MRQL 0.9.6 incubating (RC1)

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

+1 (non binding)
Code in zip & tar.gz builds ok on Windows 7, Java 8, Maven 3.3.3
SHA1 checksum verified for all artifacts.
Licence and notice present and look ok.
GPG key matches for all artifacts (although owner not in my web of
trust so can't verify it).

gpg: Signature made 02/22/16 20:07:39 GMT Standard Time using RSA key
ID 798764F1
gpg: Good signature from "Leonidas Fegaras (for release signing)
<fega...@cse.uta.edu>" [unknown]
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: F04A 300F 731F 3F10 4A68  24B2 B773 7C07 7987
64F1

Cheers,

Ian


On 28/02/2016 23:11, Leonidas Fegaras wrote:
> Hello, This is a call for a vote on Apache MRQL 0.9.6 incubating. 
> Apache MRQL is a query processing and optimization system for 
> large-scale, distributed data analysis, built on top of Apache
> Hadoop, Hama, Spark, and Flink. This is our fourth release during
> Apache Incubation. A vote was held on the MRQL developer mailing
> list and it passed with four +1 PPMC votes, no -1 votes, and no 0
> votes (see the vote thread [1] and result thread [2]). Two of these
> votes (from Alan D. Cabrera and Edward J. Yoon) carry over as
> binding IPMC votes. We are now requesting that the IPMC members
> review and vote on this release. The vote will be open for at least
> 72 hours and passes if a majority of at least three +1 IPMC votes
> are cast.
> 
> [ ] +1 Release this package as Apache MRQL 0.9.6-incubating [ ]  0
> I don't feel strongly about it, but I'm okay with the release [ ]
> -1 Do not release this package because ...
> 
> The release tarballs, including signatures, digests, etc can be
> found at: 
> https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.6-incubating
- -RC1/
>
> 
The release candidate consists of the following source distribution
> archives: - apache-mrql-0.9.6-incubating-src.[tar.gz|zip] SHA1 of
> TGZ: C703 9516 1B19 BCAF 4E7E  B460 0E8C 0468 64FE 3995 SHA1 of
> ZIP: 9416 E031 37AE D784 E165  FB5A D0B4 02E0 09AE 3030 You can
> compile the sources using 'mvn clean install'. In addition, the
> following supplementary binary distributions are provided for user
> convenience at the same location: -
> apache-mrql-0.9.6-incubating-bin.[tar.gz|zip] SHA1 of TGZ: D4FC
> 63D1 A4F0 B701 B265  790D 35B9 0701 64C2 47DB SHA1 of ZIP: 733E
> 9033 6085 3ED1 F5A0  270E A160 1230 EB2A 7086
> 
> A staged Maven repository is available for review at: 
> https://repository.apache.org/content/repositories/orgapachemrql-1004
>
>  The release candidate has been signed through the key 798764F1
> in: http://www.apache.org/dist/incubator/mrql/KEYS
> 
> The release candidate is based on the sources tagged with 
> MRQL-0.9.6-incubating-RC1 in: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;
h=ad4d7c183cb6e8a4b81f89a9cd9a3561a151d18d
>
> 
> 
> List of fixed issues: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=blob_pl
ain;f=RELEASE_NOTES;hb=ad4d7c183cb6e8a4b81f89a9cd9a3561a151d18d
>
> 
> 
> To learn more about Apache MRQL, please visit: 
> http://wiki.apache.org/mrql/ Thanks, Leonidas Fegaras
> 
> [1] http://markmail.org/message/w4shq2ndxvrmmnkd [2]
> http://markmail.org/message/ysoji5v74bbsfjdn
> 
> 
> ---------
>
> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

- -- 
Ian Dunlop, eScience Lab
School of Computer Science
The University of Manchester
http://orcid.org/-0001-7066-3350
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJW1FqxAAoJEPK45GBX+Cy5XqIH/Rg13LzUIPSGo2mFi6xV1l+v
qqS2cOIjmTwFM7XQG533SssI56/pe4wExxIfo38/jLXf6KokHwErq/cQPfXXTxUt
RkE/XpD2VxChPqsi80KeKzwraViYUFT32lwneSTI6KBKFdw+X5VphUo48JzKsdGJ
1zVcqJ7tLZ30nseJwopyG0Qeju62xjq5a3xeqGV82AcC7KjaVL2iO4A1eJ3em1F3
PVEsfHsDvJjabiDYGqWbg4e1j7nXcMboLvN05eJsFsUFHeSuNVq95mHgj4s4ORcy
Egs0pEgONspLoSJWYWwd9k+W/mR/nIOJ3ncQTM3ZjkMkkcecUrivRX4kHIrEcmg=
=A5Re
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: New mentors for Taverna?

[Ian Dunlop]

Hello,

It's an exciting phase for Apache Taverna. We are pushing out a new
release and it is a great time for new mentors to get involved. We are a
very friendly community. With the new Apache Beam proposal getting
started and the Apache Taverna integration points with the Common
Workflow Language initiative it's a great time to move into the workflow
space.

Cheers,

Ian

On 15/02/2016 08:13, Stian Soiland-Reyes wrote:
> No, we are still hoping for a new mentor..
> On 14 Feb 2016 17:13, "John D. Ament" <johndam...@apache.org> wrote:
> 
>> Just wondering, has anyone stepped up to help Taverna?
>>
>> John
>>
>> On Sat, Feb 6, 2016 at 6:56 AM Andy Seaborne <a...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> I'm one of the "semi-active mentors" of Taverna. In my case, I have a
>>> new $job, which is related to some Apache communities but not Taverna.
>>> A new job is a busy time so I'm really not able to properly support the
>>> podling at the moment.  I wish I could but I also have to be realistic.
>>>
>>> Taverna is (I believe) in good shape. Having done an incubator release
>>> of part of the codebase, they understand and take the IP issues
>>> seriously.  They have added a person to the PPMC.  All-in-all, good
>>> progress towards graduation and getting more of the codebase out is the
>>> next step.
>>>
>>> So - please could Taverna have some additional mentors?
>>>
>>>  Andy
>>>
>>> On 01/02/16 14:36, Stian Soiland-Reyes wrote:
>>>> The majority of the mentors of the Taverna podling have raised
>>>> concerns that they no longer have sufficient time available to help
>>>> Taverna in the incubator.
>>>>
>>>> In effect we will then have 2 semi-active mentors remaining for
>>> continuity.
>>>>
>>>> This has become a concern because Taverna is picking up speed and
>>>> moving towards releases of the main code base (our first release was
>>>> for a more self-contained library), and this means some effort is
>>>> needed to review and guide us through those releases.
>>>>
>>>> We in the Taverna PPMC have already learnt a lot about the Apache Way,
>>>> we have done our first release, we had 3 very successful GSOC
>>>> students, and we have voted in our first new PPMC member.
>>>>
>>>> However knowing the effort needed to review a "new" code base for a
>>>> release, we think it would not be fair on the remaining 2 mentors to
>>>> take the full burden of responsibility.
>>>>
>>>>
>>>> Therefore we would like to ask the Incubator PMC if anyone would be
>>>> interested in becoming an active mentor of Taverna as we enter this
>>>> exciting phase?
>>>>
>>>>
>>>>
>>>> About Taverna:
>>>>
>>>> http://taverna.incubator.apache.org/
>>>>
>>>> Taverna is a domain-independent suite of tools used to design and
>>>> execute data-driven workflows, which invoke a mixture of local and
>>>> remote (REST, WSDL) services. Taverna is used by scientists and
>>>> researchers in domains like bioinformatics, chemistry, musicology,
>>>> biodiversity and virtual physiology to combine and process data from
>>>> multiple sources using a wide variety of analytical tools.
>>>>
>>>> Taverna workflows can be designed in a graphical workbench,
>>>> programmatically through the Taverna Language API, or using an
>>>> RDF/JSON-based workflow format. They can be executed locally (command
>>>> line, within workbench or through OSGi-based APIs), or on a Taverna
>>>> server (REST/WSDL), which has been integrated by portals and
>>>> frontends, including an Android mobile app. Taverna results include
>>>> full provenance trace of the execution as we strive to support
>>>> reproducible computational research.
>>>>
>>>> This is an exciting time for us, as we are not just releasing version
>>>> 3 of Taverna, but also working on a Common Workflow Language
>>>> integration (YaML), including support for coordinating Docker-based
>>>> command line tools.
>>>>
>>>> We rely on a large selection of Apache tools, like Woden, Felix, Jena,
>>>> Derby, Tika, Velocity, Commons, HTTP Client and Maven.
>>>>
>>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
> 

-- 
Ian Dunlop, eScience Lab
School of Computer Science
The University of Manchester
http://orcid.org/-0001-7066-3350

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

No issues. I have now managed to compile it with no problems on Ubuntu
14.04. (Thanks for the reminder :) )

+1

Cheers,

Ian

On 29/12/2015 08:02, Yuri Z wrote:
> Hi Ian Are there any more issues that hold you from voting on the
> Apache Wave release on general@apache?
> 
> On Sat, Nov 7, 2015 at 3:25 AM Ali Lown <a...@lown.me.uk> wrote:
> 
>> Hi Ian,
>> 
>> I am not sure about the best way to import this into eclipse, I
>> have always used the CLI tools directly. I have CC'd the dev-list
>> in case they have a better answer for you.
>> 
>> The inability to find  ${build.classpath.path},
>> ${build.macros.path} suggests that you are
>> missing/failed-to-import/failed-to-reference the build.properties
>> file which contains the values for these macros.
>> 
>> The follow-up problem about missing define-gxpc is to be
>> expected because of the above problem resulting in it not
>> importing build-macros.xml, which defines "define-gxpc" amongst
>> other things.
>> 
>> Ali
>> 
>> On 6 November 2015 at 14:51, Ian Dunlop
>> <ian.dun...@manchester.ac.uk> wrote:
> Hello,
> 
> I'll give it at 0 the moment since I encountered a build issue. I 
> downloaded the src zip and imported the code into Eclipse Mars
> (4.50) with jdk 1.7.0_79 & ANT 1.9.4 but found the following
> issues:
> 
> 1) BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:28:
> Cannot find 
> C:\Users\idunlop\workspace\waveinabox\${build.classpath.path}
> imported from C:\Users\idunlop\workspace\waveinabox\build.xml
> 
> Resolved by commenting out
> 
> 
> 
>  
> 
> and tried again
> 
> 2)
> 
> BUILD FAILED Target "define-gxpc" does not exist in the project
> "waveinabox". It is used from target "gen-gxp".
> 
> Resolved by removing define-gxpc from
> 
>  depends="init, define-gxpc, gen-gxp-dep" unless="skip.gen-gxp"> 
>  destdir="${gen.dir}/gxp" target="org.waveprotocol.box.server.gxp"
> />  
> 
> 3)
> 
> BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:120:
> Problem: failed to create task or type buildproto Cause: The name
> is undefined. Action: Check the spelling. Action: Check that any
> custom tasks/types have been declared. Action: Check that any
> / declarations have taken place.
> 
> At that point I figured it best to report the issues here:
> 
> Is there a procedure for building in eclipse, am I missing an ant 
> setting somewhere?
> 
> So, apart fromn the compile issue everything else looks good:
> 
> signatures are good artifact/hashes good DISCLAIMER OK LICENCE OK 
> NOTICE OK
> 
> Cheers,
> 
> Ian
> 
> 
> 
> On 04/11/2015 07:14, Justin Mclean wrote:
>>>>> Hi,
>>>>> 
>>>>> +1 binding.
>>>>> 
>>>>> Could you please fix the LICENCE Appendix in the next
>>>>> release. The text should be "Copyright [] [name of
>>>>> copyright owner]” not "Copyright 2013 The Apache Software
>>>>> Foundation”.
>>>>> 
>>>>> I checked: - artefact has incubating in name - signatures
>>>>> and hashes good - DISCLAIMER exists - LICENSE  has minor
>>>>> issue with the copyright in the appendix. Not required but
>>>>> it could also use the sort form in LICENSE [1] particularly
>>>>> as you bundle the software LICENSE files. - NOTICE good. -
>>>>> All source files have Apache headers - No unexpected binary
>>>>> file in source release (but see below) - can compile from
>>>>> source - test pass
>>>>> 
>>>>> I notice there’s a couple of photographs in the source
>>>>> release, I assume you have permission from the person who
>>>>> took them to use these? IF so you may want to put that in
>>>>> the LICENSE.
>>>>> 
>>>>> There's a number of binary file without extensions in 
>>>>> /thumbnail_patterns/ but they all look to be PNGs is this
>>>>> the case? Where did these images come from?
>>>>> 
>>>>> I had a quick look at the binary release and the LICENCE
>>>>> and NOTICE appear comprehensive. I didn;t do a though
>>>>> check. I did notice that the year is incorrect in the
>>>>> NOTICE file and LICENSE appendix has the same issue.  It’s
>>>>> actually wrong here as non ASF Apache licensed software is
>&

Grant wiki access for iandunlop

[Ian Dunlop]

Hello,

Could you add iandunlop to the contributors list for the incubator wiki
please.

Cheers,

Ian
-- 
Ian Dunlop, eScience Lab
School of Computer Science
The University of Manchester
http://orcid.org/-0001-7066-3350

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I did try to use the CLI to build it but ran into java issues since
windows seems determined to use java 8 and i can only get java 7 to
run inside eclipse. Getting windows to use an older version of java
seems like a fairly difficult or poorly documented task nowadays.
Suggestions welcome (though as noted earlier they may belong a a
different list).

Cheers,

Ian

On 08/11/15 19:41, John D. Ament wrote:
> Typically speaking, releases should compile.  If there are steps
> required to make it compile they should be shared. On Nov 8, 2015
> 14:33, "Upayavira" <u...@odoko.co.uk> wrote:
> 
>> Ian,
>> 
>> Please bear in mind that this release vote is to validate the
>> legal aspects of the release, not its technical merits. Technical
>> merits can be resolved in subsequent releases.
>> 
>> Upayavira
>> 
>> On Fri, Nov 6, 2015, at 02:51 PM, Ian Dunlop wrote:
> Hello,
> 
> I'll give it at 0 the moment since I encountered a build issue. I 
> downloaded the src zip and imported the code into Eclipse Mars
> (4.50) with jdk 1.7.0_79 & ANT 1.9.4 but found the following
> issues:
> 
> 1) BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:28:
> Cannot find 
> C:\Users\idunlop\workspace\waveinabox\${build.classpath.path}
> imported from C:\Users\idunlop\workspace\waveinabox\build.xml
> 
> Resolved by commenting out
> 
> 
> 
>  
> 
> and tried again
> 
> 2)
> 
> BUILD FAILED Target "define-gxpc" does not exist in the project
> "waveinabox". It is used from target "gen-gxp".
> 
> Resolved by removing define-gxpc from
> 
>  depends="init, define-gxpc, gen-gxp-dep" unless="skip.gen-gxp"> 
>  destdir="${gen.dir}/gxp" target="org.waveprotocol.box.server.gxp"
> />  
> 
> 3)
> 
> BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:120:
> Problem: failed to create task or type buildproto Cause: The name
> is undefined. Action: Check the spelling. Action: Check that any
> custom tasks/types have been declared. Action: Check that any
> / declarations have taken place.
> 
> At that point I figured it best to report the issues here:
> 
> Is there a procedure for building in eclipse, am I missing an ant 
> setting somewhere?
> 
> So, apart fromn the compile issue everything else looks good:
> 
> signatures are good artifact/hashes good DISCLAIMER OK LICENCE OK 
> NOTICE OK
> 
> Cheers,
> 
> Ian
> 
> 
> 
> On 04/11/2015 07:14, Justin Mclean wrote:
>>>>> Hi,
>>>>> 
>>>>> +1 binding.
>>>>> 
>>>>> Could you please fix the LICENCE Appendix in the next
>>>>> release. The text should be "Copyright [] [name of
>>>>> copyright owner]” not "Copyright 2013 The Apache Software
>>>>> Foundation”.
>>>>> 
>>>>> I checked: - artefact has incubating in name - signatures
>>>>> and hashes good - DISCLAIMER exists - LICENSE  has minor
>>>>> issue with the copyright in the appendix. Not required but
>>>>> it could also use the sort form in LICENSE [1] particularly
>>>>> as you bundle the software LICENSE files. - NOTICE good. -
>>>>> All source files have Apache headers - No unexpected binary
>>>>> file in source release (but see below) - can compile from
>>>>> source - test pass
>>>>> 
>>>>> I notice there’s a couple of photographs in the source
>>>>> release, I assume you have permission from the person who
>>>>> took them to use these? IF so you may want to put that in
>>>>> the LICENSE.
>>>>> 
>>>>> There's a number of binary file without extensions in 
>>>>> /thumbnail_patterns/ but they all look to be PNGs is this
>>>>> the case? Where did these images come from?
>>>>> 
>>>>> I had a quick look at the binary release and the LICENCE
>>>>> and NOTICE appear comprehensive. I didn;t do a though
>>>>> check. I did notice that the year is incorrect in the
>>>>> NOTICE file and LICENSE appendix has the same issue.  It’s
>>>>> actually wrong here as non ASF Apache licensed software is
>>>>> mentioned. There no need to mean Apache licensed software
>>>>> in the LICENCE but no harm is done by donning so. [2]
>>>>> 
>>>>> Thanks, Justin
>>>>> 
>>>>> 1.
>>>>> h

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

I'll give it at 0 the moment since I encountered a build issue. I
downloaded the src zip and imported the code into Eclipse Mars (4.50)
with jdk 1.7.0_79 & ANT 1.9.4 but found the following issues:

1)
BUILD FAILED
C:\Users\idunlop\workspace\waveinabox\build.xml:28: Cannot find
C:\Users\idunlop\workspace\waveinabox\${build.classpath.path} imported
from C:\Users\idunlop\workspace\waveinabox\build.xml

Resolved by commenting out

  

  
  

and tried again

2)

BUILD FAILED
Target "define-gxpc" does not exist in the project "waveinabox". It is
used from target "gen-gxp".

Resolved by removing define-gxpc from

  


  

3)

BUILD FAILED
C:\Users\idunlop\workspace\waveinabox\build.xml:120: Problem: failed
to create task or type buildproto
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken
place.

At that point I figured it best to report the issues here:

Is there a procedure for building in eclipse, am I missing an ant
setting somewhere?

So, apart fromn the compile issue everything else looks good:

signatures are good
artifact/hashes good
DISCLAIMER OK
LICENCE OK
NOTICE OK

Cheers,

Ian



On 04/11/2015 07:14, Justin Mclean wrote:
> Hi,
> 
> +1 binding.
> 
> Could you please fix the LICENCE Appendix in the next release. The
> text should be "Copyright [] [name of copyright owner]” not
> "Copyright 2013 The Apache Software Foundation”.
> 
> I checked: - artefact has incubating in name - signatures and
> hashes good - DISCLAIMER exists - LICENSE  has minor issue with the
> copyright in the appendix. Not required but it could also use the
> sort form in LICENSE [1] particularly as you bundle the software
> LICENSE files. - NOTICE good. - All source files have Apache
> headers - No unexpected binary file in source release (but see
> below) - can compile from source - test pass
> 
> I notice there’s a couple of photographs in the source release, I
> assume you have permission from the person who took them to use
> these? IF so you may want to put that in the LICENSE.
> 
> There's a number of binary file without extensions in
> /thumbnail_patterns/ but they all look to be PNGs is this the case?
> Where did these images come from?
> 
> I had a quick look at the binary release and the LICENCE and NOTICE
> appear comprehensive. I didn;t do a though check. I did notice that
> the year is incorrect in the NOTICE file and LICENSE appendix has
> the same issue.  It’s actually wrong here as non ASF Apache
> licensed software is mentioned. There no need to mean Apache
> licensed software in the LICENCE but no harm is done by donning so.
> [2]
> 
> Thanks, Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps 
> 2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> 
> 
> 
> ---------
>
> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

- -- 
Ian Dunlop, eScience Lab
School of Computer Science
The University of Manchester
http://orcid.org/-0001-7066-3350
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWPL6FAAoJEPK45GBX+Cy5agYH/3yPH2vLCltvOqIZlv70TJ9R
EmdbRL6rvpJjcah+GH9BPpsYEeENXw5WTARH42RVZT4gFUz62GBIkZhhqFks0/qx
ubL+bekcivMI2P/eZ3T6S/mKw52d8esRaDvrMKaUZ3Ax3tdkYt/dPaYoXGxAMNS4
5IolSgvMaTT2qKlcx0fmCh+gdfmxHFo0ZTvZ55V9ucnmsvQY8orGqZt7SJ+jdySz
vp9AIvnxStMCorZ8tKSLDVo1H+ciQOXxCZWymFlAlm7nQAw5KoLQYMp/OBUrw6Lk
urdolruKU7YGgdwh5uV8WHi+cCfpIyQIRaIz8nFlXYTFx/VL8Dm7vrgFpcH1jyw=
=d5Aa
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

+1

That's some impressive community growth.

Cheers,

Ian

On 16/09/15 06:14, Steven Noels wrote:
> On Tue, Sep 15, 2015, at 03:56 AM, Julian Hyde wrote:
> 
>> This is a vote for Calcite to become a top-level project.
>> 
>> Since joining the Incubator in May, 2014, the Calcite community
>> has: * Produced eight IPMC-approved releases under two release 
>> managers; * Added five new committers and one new PPMC member; *
>> Collaborated successfully with several other Apache projects
>> (Drill, Hive, Kylin, Phoenix, Samza); * Grown into an active
>> community (typical monthly activity is 100 emails, 30 commits and
>> 20 issues fixed); * Conducted a successful community vote to
>> graduate with 20 +1 votes, of which 2 were from our mentors, 12
>> were from committers, and 6 were from IPMC members.
>> 
>> Further information: the discussion on the dev list [1], vote
>> thread [2] and result [3]. Also relevant are the incubation
>> status page [4] and a thread on this list requesting review of
>> whether Calcite met the criteria to graduate [5].
>> 
>> Below is our proposed resolution for the Board.
>> 
>> Please vote:
>> 
>> [ ] +1 Graduate Apache Calcite as a top-level project [ ] +0 [ ]
>> -1 Do not graduate Apache Calcite because…
> 
> Enthusiastic +1
> 
> Great job!
> 
> Steven.
> 
> 
> -
>
> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV+T7LAAoJEPK45GBX+Cy5UZUH/j5dpdeNgCet//j/9kyqTjq0
ig+i8asO3f6p0+2r11HunWPiIwscoNrgx3NPRIDell93ZzzrPfHIfqMd+mjhmIye
wQsSxSc+k7aOkgp7zV+s0IqirlZ5Di0eAmVDoJ3IM9WzOqTd7I4j6fzvaqjHmTAm
m0gpiFfusiJsG0BupjofHbC8UtYq9tFtBBgj/eLcOcaLC0hsN6ZUxTPJeJqEPwiu
rRIOVuWtnelZaXG2UCMx1Zmt2M6VD59ooFgfgU9MA/DKvPjIMEDyRbTDOP/YGxFH
O9ON302P5kV5vWG8F/Q+LNGex3Cyg2iYvYMNfFUqvSQqGwvUd5qyf3Qu8HwCq9M=
=vpA5
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Release Apache Taverna Parent 1-incubating-RC4 Apache Taverna Language 0.15.0-incubating RC4

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi All,

Voting for Apache Taverna Parent 1-incubating  Apache Taverna
Language 0.15.0-incubating is now closed.  The release has
passed with the following tally:

Binding +1s:

Marlon Pierce (see
http://mail-archives.apache.org/mod_mbox/incubator-taverna-dev/201507.mb
ox/%3CD1E0E778.447EC%25marpierc%40iu.edu%3E)

Andy Seaborne (see
http://mail-archives.apache.org/mod_mbox/incubator-taverna-dev/201508.mb
ox/%3C55C86B79.3040006%40apache.org%3E)

Jan Iversen

Non binding +1s:
Ian Dunlop
Alan Williams
Stian Soiland-Reyes
Donal K. Fellows

Thank you to everyone who voted. We will now continue with the release
process.

Cheers,

Ian

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVyJ3TAAoJEPK45GBX+Cy5Nf8IAK+vtwS7IRRGz/7KruzbNH7B
Q+QGxOmQvF6jfbjz2jNaB/5qQ/UYg+TAh3VHxcjIxANdOhia0QZePfsd0FCP4mTV
aeRqEbJkMRc8xMwhzWQa75PrbOf/UN0IJofUV5y0sszJ949papGLmNACvHfIQZgC
yaX8o93QDlCp2Z+u5agBM2ccTOqntNH9o3dJeGHtZg79Kcfd4NfohPP+fFG2/IQM
K7nX2q+9vE16Zn3Mk9rujvXE7syHHkcH+/1Cuwndt2NFX3IPqmDKppZ4X6bxWMGz
mhyV4E203Wi25V6bnkfIp7SC3IAl6/kzkzptFScnHRG5aELeI/EwqcaiudEXn70=
=hLN/
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Taverna Parent 1-incubating-RC4 Apache Taverna Language 0.15.0-incubating RC4

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

The Apache Taverna Incubator PPMC has voted +5 to release

Apache Taverna Parent 1-incubating (RC4)
Apache Taverna Language 0.15.0-incubating (RC4)

Incubator PMC members please review and vote on this incubator release.

Apache Taverna Language is a set of APIs for workflow definitions
(SCUFL2) and workflow inputs/outputs/run (DataBundle), as consumed and
produced by the Apache Taverna workflow system. The API includes
support for working with Research Object Bundles, and loading/saving
Taverna workflows in different formats.

Please see original [VOTE] thread
http://mail-archives.apache.org/mod_mbox/incubator-taverna-dev/201507.mb
ox/%3C55B8DBC7.2040806%40manchester.ac.uk%3E

and [DISCUSS] thread
http://mail-archives.apache.org/mod_mbox/incubator-taverna-dev/201507.mb
ox/%3C55B8DC3F.2070602%40manchester.ac.uk%3E

Please note that the git commit ids were incorrect in the original
[VOTE] email but were corrected during the vote process.
Also, during the release checks some NOTICE files were found to
contain information that was already in the top level LICENSE and a
bug was raised against it, see
https://issues.apache.org/jira/browse/TAVERNA-864

The release candidates to be voted over are available at:

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-
parent-1-incubating-RC4/
https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-
language-0.15.0-incubating-RC4/

SHA-1 checksums:
3eb09278b914b96fb5c6059523b1bb3e69a09334
taverna-parent-1-incubating-source-release.zip
4eeb37d141fea284cc8de17635d97a47b279ea91
taverna-language-0.15.0-incubating-source-release.zip

MD5 checksums:
bccfe1116189f5ccc640fcbed4a4f96f
taverna-parent-1-incubating-source-release.zip
685b3aed3833a0b921d129995944dfc3
taverna-language-0.15.0-incubating-source-release.zip

Build the release candidates in the above order, using:

Java 7: mvn clean install -Dmaven.javadoc.skip=true  (see
https://issues.apache.org/jira/browse/TAVERNA-867 for the reasons the
maven command line params are required)
Java 8: mvn clean install

The release candidates correspond to the following git commits:

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent
.git;a=commit;h=b12a1cc0ed2540507ab43107124e8ee911da4ddf

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git
;a=commit;h=e2a9954e796d886d137eed3091b21637e9c8d1fd

Release candidates are signed with a GPG key available at:

https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS

A staged Maven repository is available for review at:

https://repository.apache.org/content/repositories/orgapachetaverna-1006
/

The changelog for this release is available from JIRA:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231832
2version=12332247
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231832
2version=12332246

Please vote on releasing these packages as:

Apache Taverna Maven Parent 1-incubating
Apache Taverna Language 0.15.0-incubating

The vote will be open for a minimum of 72 hours.

[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but
don't object
[ ] -1 Do not release this package because...

Cheers,

Ian
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVwe91AAoJEPK45GBX+Cy5lMsH/jiDvvduoZ43y9SVMQcbIvdn
GZDXOviSco5NAWnekqVzR5juXXHGVCZD56NFDfDkzlS1EinQP11HWEZjx1Tgz5TL
0ghvwRtymc5s6Vu2SMlWeiZszja/lD2430zc28jwtBhesd3xckUIa2VHg9viDiaT
w5iCQQB95TiCnShJaUDbFg0TiLB2BH/xZrb07967MsyH1YeSOI72aOhVkxbFthlE
ELJhRmKBtmfl/RJoPydzrs4IOvvml57hcJQT6DjONGEuaIzSvOJVcV8l+oZgmM1a
QqK6bjS0I+rmcK6udAFrgZmtNKsI/n+qufnaTxg1j1ghZRhDWo/ZAawpzGBo/+I=
=K8dX
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org