Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha(2nd round)

[???? Sheng Wu]

Hi Justin


Right now, I updated our rat exclude config as following, is this allowed? The 
concern may about JSON file for our test cases data and frontend/UI dependency 
descriptions, but JSON format is not allowed to add the header.



org.apache.rat
apache-rat-plugin
0.12


**/target/**
**/DISCLAIMER
**/licenses/**
**/codeStyle.xml


**/*.iml
**/.idea/**
**/*.classpath
**/.project
**/.settings/**
**/dependency-reduced-pom.xml


**/skywalking-ui/.editorconfig

**/skywalking-ui/.webpackrc.js
**/skywalking-ui/.roadhogrc.mock.js

**/skywalking-ui/.eslintrc
**/skywalking-ui/.stylelintrc


**/.gitignore
**/.gitmodules
**/.git/**


**/.travis.yml


**/.github/**


**/*.md
**/*.MD
**/*.txt
**/docs/**


**/src/test/resources/json/*.json


**/skywalking-ui/node_modules/**
**/skywalking-ui/node/**
**/skywalking-ui/dist/**


skywalking-ui/package.json
skywalking-ui/package-lock.json




verify

check






--
Sheng Wu
Apache SkyWalking original creator and PPMC member


 




-- Original --
From:  "Justin Mclean";
Date:  Sat, Mar 24, 2018 10:48 AM
To:  "general";

Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) version 
5.0.0-alpha(2nd round)



Hi,

Perhaps a silly question but I notice several people say they used rat to check 
this release. Rat clearly shows the jars, does rat need to flag these in a more 
serious way or were they hidden by a too wide rat exclusion file?

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

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1

[Jean-Baptiste Onofré]

-1 (binding) due to source under CC-BY license which is Cat B. It can be used
but not included in source release.

Regards
JB

On 03/23/2018 10:16 AM, Mohammad Asif Siddiqui wrote:
>  Hi All,  
>   
> This is a call for vote to release Apache ServiceComb Java-Chassis 
> (Incubating) version 1.0.0-m1  
>   
> Apache ServiceComb (Incubating) Community has voted and approved the release. 
>  
>   
> Vote Thread : 
> https://lists.apache.org/thread.html/b778a8787435b963c0743c518c3bc0b4c419a4010edc369f2c12c43c@%3Cdev.servicecomb.apache.org%3E
>   
>   
> Result Thread : 
> https://lists.apache.org/thread.html/81f6fd78e0577853c07e5a1924a9cf5a9c17aba5dd725d58fa397bea@%3Cdev.servicecomb.apache.org%3E
>   
>   
> Release Notes : 
> https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/etc/releaseNotes.md
>   
>   
> Release Candidate : 
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/
>   
>   
> Staging Repo : 
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1196/ 
>  
>   
> Release Tag : 
> https://github.com/apache/incubator-servicecomb-java-chassis/releases/tag/1.0.0-m1
>  
>   
> Release CommitID : 901869b987c6f65c92b5b8b8f05eaf0f9f6e69cb  
>   
> Keys to verify the Release Candidate : 
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS  
>   
> Voting will start now ( Friday, 23rd March, 2018) and will remain open for 
> next 72 hours, we request all IPMC members to give their vote.  
>   
> [ ] +1 Release this package as 1.0.0-m1  
> [ ] +0 No Opinion  
> [ ] -1 Do not release this package because  
>   
> Regards  
> Asif  
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

Re: Altering PMC for graduation

[Stian Soiland-Reyes]

This is not uncommon, at least for filtering the initial PPMC members at
the point of graduation. Obviously it should be the PPMC who decides this
in a regular consensus.

What would be unusual (and perhaps controversial) is using the graduation
for "removing" PPMC members who had been voted in during incubation,
however it is not uncommon for PMC members to step down on their own
initiative.



On Fri, 23 Mar 2018, 16:06 Dave Neuman,  wrote:

> Hey IPMC,
> I had a question about altering the PMC for graduation.
> We have a few folks who are no longer active participants in our project
> that are still a part of our PMC.  In the process of generating our
> graduation resolution we were wondering if we could take the opportunity to
> have these members just be committers and not PMC members anymore?  If yes,
> what would the process look like, would it be enough to just make the
> roster alterations in Whimsy?  I have already spoken to each of these
> people individually and made sure they were on-board with just being
> committers and not PMC members.
>
> We are really excited to draft our resolution and I think this is the last
> thing standing in our way!
>
>
> Thanks in advance for the help!
>
> Dave
>

Re: Altering PMC for graduation

[Dave Fisher]

Hi -

This would be a legitimate thread on private@, or in a generic email on dev@ 
asking for and suggesting responses on private@. The principle is allowing 
personnel/personal decisions to remain private at the individual’s choice.

Regards,
Dave




Sent from my iPhone

> On Mar 23, 2018, at 8:02 PM, David Neuman  wrote:
> 
> Will do, thanks.
> 
>> On Fri, Mar 23, 2018 at 19:04 John D. Ament  wrote:
>> 
>> On Fri, Mar 23, 2018 at 9:02 PM David Neuman 
>> wrote:
>> 
>>> Great, thanks a lot for the info John.  Since I have spoken to each of
>> the
>>> PMC members in question individually, I think we are safe to make our
>>> changes and have them continue on as committers.
>>> 
>> 
>> Remember, if it didn't happen on list it didn't happen.  Please make sure
>> you check with these individuals on list.
>> 
>> 
>>> 
>>> On Fri, Mar 23, 2018 at 16:27 John D. Ament 
>> wrote:
>>> 
 Its quite common that people stop working on open source projects.
 However, part of the Apache way is merit never expires.  While you may
>>> not
 want to include them in your PMC, keeping them available as a committer
 isn't a bad thing.
 
 Most podlings I've seen will send an email "here's the proposed PMC,
>>> speak
 up if you need a change."  If any of those people want to be on the
>> PMC,
 still honor their request.  However if they are not interested then its
 safe to assume they would have responded.
 
 I do recommend if you are going to make changes, that the changes are
 finalized in the roster before submitting the resolution to the board.
 This may involve sending the IPMC notices for new PPMC members ahead of
 time, just to keep it clean.  Having your roster correct means everyone
 gets the right permissions without the chair having to do anything.
 
 John
 
 On Fri, Mar 23, 2018 at 6:14 PM Carlos Santana 
 wrote:
 
> For Apache OpenWhisk we are in same situation so it would be good to
> understand the guideline on how to handle such situation.
> 
> - Carlos Santana
> @csantanapr
> 
>> On Mar 23, 2018, at 4:06 PM, Dave Neuman 
>> wrote:
>> 
>> Hey IPMC,
>> I had a question about altering the PMC for graduation.
>> We have a few folks who are no longer active participants in our
 project
>> that are still a part of our PMC.  In the process of generating our
>> graduation resolution we were wondering if we could take the
 opportunity
> to
>> have these members just be committers and not PMC members anymore?
>>> If
> yes,
>> what would the process look like, would it be enough to just make
>> the
>> roster alterations in Whimsy?  I have already spoken to each of
>> these
>> people individually and made sure they were on-board with just
>> being
>> committers and not PMC members.
>> 
>> We are really excited to draft our resolution and I think this is
>> the
> last
>> thing standing in our way!
>> 
>> 
>> Thanks in advance for the help!
>> 
>> Dave
> 
> -
> 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: Altering PMC for graduation

[David Neuman]

Will do, thanks.

On Fri, Mar 23, 2018 at 19:04 John D. Ament  wrote:

> On Fri, Mar 23, 2018 at 9:02 PM David Neuman 
> wrote:
>
> > Great, thanks a lot for the info John.  Since I have spoken to each of
> the
> > PMC members in question individually, I think we are safe to make our
> > changes and have them continue on as committers.
> >
>
> Remember, if it didn't happen on list it didn't happen.  Please make sure
> you check with these individuals on list.
>
>
> >
> > On Fri, Mar 23, 2018 at 16:27 John D. Ament 
> wrote:
> >
> > > Its quite common that people stop working on open source projects.
> > > However, part of the Apache way is merit never expires.  While you may
> > not
> > > want to include them in your PMC, keeping them available as a committer
> > > isn't a bad thing.
> > >
> > > Most podlings I've seen will send an email "here's the proposed PMC,
> > speak
> > > up if you need a change."  If any of those people want to be on the
> PMC,
> > > still honor their request.  However if they are not interested then its
> > > safe to assume they would have responded.
> > >
> > > I do recommend if you are going to make changes, that the changes are
> > > finalized in the roster before submitting the resolution to the board.
> > > This may involve sending the IPMC notices for new PPMC members ahead of
> > > time, just to keep it clean.  Having your roster correct means everyone
> > > gets the right permissions without the chair having to do anything.
> > >
> > > John
> > >
> > > On Fri, Mar 23, 2018 at 6:14 PM Carlos Santana 
> > > wrote:
> > >
> > > > For Apache OpenWhisk we are in same situation so it would be good to
> > > > understand the guideline on how to handle such situation.
> > > >
> > > > - Carlos Santana
> > > > @csantanapr
> > > >
> > > > > On Mar 23, 2018, at 4:06 PM, Dave Neuman 
> wrote:
> > > > >
> > > > > Hey IPMC,
> > > > > I had a question about altering the PMC for graduation.
> > > > > We have a few folks who are no longer active participants in our
> > > project
> > > > > that are still a part of our PMC.  In the process of generating our
> > > > > graduation resolution we were wondering if we could take the
> > > opportunity
> > > > to
> > > > > have these members just be committers and not PMC members anymore?
> > If
> > > > yes,
> > > > > what would the process look like, would it be enough to just make
> the
> > > > > roster alterations in Whimsy?  I have already spoken to each of
> these
> > > > > people individually and made sure they were on-board with just
> being
> > > > > committers and not PMC members.
> > > > >
> > > > > We are really excited to draft our resolution and I think this is
> the
> > > > last
> > > > > thing standing in our way!
> > > > >
> > > > >
> > > > > Thanks in advance for the help!
> > > > >
> > > > > Dave
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha(2nd round)

[???? Sheng Wu]

Yes. I think our exclusion file of rat is too wide, Jiang has also pointed that 
out.


I am closing this vote. Thanks everyone to help us. We are going to fix them. :)


--
Sheng Wu
Apache SkyWalking original creator and PPMC member








-- Original --
From:  "Justin Mclean";
Date:  Sat, Mar 24, 2018 10:48 AM
To:  "general";

Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) version 
5.0.0-alpha(2nd round)



Hi,

Perhaps a silly question but I notice several people say they used rat to check 
this release. Rat clearly shows the jars, does rat need to flag these in a more 
serious way or were they hidden by a too wide rat exclusion file?

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

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)

[Justin Mclean]

Hi,

Perhaps a silly question but I notice several people say they used rat to check 
this release. Rat clearly shows the jars, does rat need to flag these in a more 
serious way or were they hidden by a too wide rat exclusion file?

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

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)

[Willem Jiang]

-1.

Here are the checkings those I did:
I can build the binary from the source kit.

We need separate License and NOTICE file for binary and source release.
I just checked RAT plugin setting on the parent POM.
There are some exclusion of the configuration, protocol even the test data,
we need to address these files License issue before doing the release.


**/*.yml
**/*.config


**/*.graphqls
**/*.proto


**/src/test/resources/**
**/*.def





Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 23, 2018 at 10:47 AM, 吴晟 Sheng Wu  wrote:

> Hi All,
> This is a call for vote to release Apache SkyWalking (Incubating) version
> 5.0.0-alpha
>
>
>
> The Apache SkyWalking community has tested, voted and approved the proposed
> release of Apache SkyWalking (Incubating) 5.0.0-alpha
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
>
> Skywalking is an APM (application performance monitor), especially for
> microservice, Cloud Native and container-based architecture systems. Also
> known as a distributed tracing system. It provides an automatic way to
> instrument applications: no need to change any of the source code of the
> target application; and an collector with an very high efficiency streaming
> module.
>
>
> This is the first and alpha release of version 5. We write a Release
> Guide[1] and vote check list[2] by following Apache release and
> distribution documents.
>
>
>
> Vote Thread:
>
>
>  * https://lists.apache.org/thread.html/5abdab49ced0ab10059f99157fb983
> 002352205f0ba6469181ec053f@%3Cdev.skywalking.apache.org%3E
>
>
> Result Thread:
>
>
>  * https://lists.apache.org/thread.html/6aaf3f5d2c0c1289796c9b658ac812
> cea2c4b6d619b78dbeb1566a4e@%3Cdev.skywalking.apache.org%3E
>
>
> Release notes:
>
>
>  * https://github.com/apache/incubator-skywalking/blob/v5.
> 0.0-alpha/CHANGES.md
>
>
> Release Candidate:
>
>
>  * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> 5.0.0-alpha/
>
>
> Maven 2 staging repository:
>
>
>  * https://repository.apache.org/content/repositories/
> orgapacheskywalking-1005/org/apache/skywalking/apache-
> skywalking-apm-incubating/5.0.0-alpha/
>
>
> Release Tag :
>
>
>  * v5.0.0-alpha
>
>
> Release CommitID :
>
>
>  * f52d99498f02402d2ce1a0b7b909cd7fcfb3526f
>
>
> Keys to verify the Release Candidate :
>
>
> * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> 5.0.0-alpha/KEYS
> * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777
>
> corresponding to pen...@apache.org
>
>
> Guide to build the release from source :
>
>
>  * https://github.com/apache/incubator-skywalking/blob/v5.
> 0.0-alpha/docs/en/How-to-release.md
>
>
> Voting will start now (March 23th, 2018) and will remain open for at least
> 72 hours, Request IPMC to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because
>
>
>
>
>
> [1] https://github.com/apache/incubator-skywalking/blob/
> master/docs/en/How-to-release.md
> [2] https://github.com/apache/incubator-skywalking/blob/
> master/docs/en/How-to-release.md#vote-check
>
>
>
>
> --
> Sheng Wu
> Apache SkyWalking original creator and PPMC member

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)

[Justin Mclean]

Hi,

Seems to be two open vote threads which is slightly confusing, so re posting 
this just so it doesn’t get lost in the other thread.

-1 binding for including compiled code in a source release. Also LICENSE and 
NOTICE look to be listing dependancies not bundled items [4][5]

I checked:
- incubating in name
- signatures and hashes good
- DISCLAIMER exists
- LICENSE lists items that are not bundled in the source release please remove 
them
- NOTICE  lists items that are not bundled in the source release please remove 
them
- All source files have ASF headers
- Compiled code in source release [1][2][3]
- Can build from source release

MPL  (mentioned in license) is a Category B license so is generally not 
mentioned in a source release LICENSE file. [9]

Note that correct LICENSE and NOTICE may be correct for the binary release 
(I’ve not checked) but it’s not for the source release.

Other NOTICE  files that may effect your binary NOTICE file (assuming the 
software is actually bundled and not just a dependancy) include [6][7][8].

Thanks,
Justin

1. ./ci-dependencies/dubbox-2.8.4.jar
2. ./ci-dependencies/jmxri-1.2.1.jar
3. ./ci-dependencies/jmxtools-1.2.1.jar
4. http://www.apache.org/dev/licensing-howto.html#guiding-principle 

5. http://www.apache.org/dev/licensing-howto.html#permissive-deps 

6. https://github.com/grpc/grpc/blob/master/NOTICE.txt 

7. https://github.com/elastic/elasticsearch/blob/master/NOTICE.txt 

8. https://github.com/JodaOrg/joda-time/blob/master/NOTICE.txt 

9. https://www.apache.org/legal/resolved.html#category-b 

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha(2nd round)

[Justin Mclean]

Hi,

-1 binding for including compiled code in a source release. Also LICENSE and 
NOTICE look to be listing dependancies not bundled items [4][5]

I checked:
- incubating in name
- signatures and hashes good
- DISCLAIMER exists
- LICENSE lists items that are not bundled in the source release please remove 
them
- NOTICE  lists items that are not bundled in the source release please remove 
them
- All source files have ASF headers
- Compiled code in source release [1][2][3]
- Can build from source release

MPL  (mentioned in license) is a Category B license so is generally not 
mentioned in a source release LICENSE file. [9]

Note that correct LICENSE and NOTICE may be correct for the binary release 
(I’ve not checked) but it’s not for the source release.

Other NOTICE  files that may effect your binary NOTICE file (assuming the 
software is actually bundled and not just a dependancy) include [6][7][8].

Thanks,
Justin

1. ./ci-dependencies/dubbox-2.8.4.jar
2. ./ci-dependencies/jmxri-1.2.1.jar
3. ./ci-dependencies/jmxtools-1.2.1.jar
4. http://www.apache.org/dev/licensing-howto.html#guiding-principle
5. http://www.apache.org/dev/licensing-howto.html#permissive-deps
6. https://github.com/grpc/grpc/blob/master/NOTICE.txt
7. https://github.com/elastic/elasticsearch/blob/master/NOTICE.txt
8. https://github.com/JodaOrg/joda-time/blob/master/NOTICE.txt
9. https://www.apache.org/legal/resolved.html#category-b
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1

[Willem Jiang]

Hi Justin,

Thanks for pointing that out.  I just filled a JIRA[1] for it and submit
quick fix for it.
[1]https://issues.apache.org/jira/browse/SCB-427


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Mar 24, 2018 at 8:22 AM, Justin Mclean  wrote:

> Hi,
>
> Sorry but it’s -1 binding from me as the source release contains some
> CC-BY licensed content in plain text. [1][2] CC-BY is considered Category B
> [3] and can’t be included in a source release. These files also incorrectly
> IMO have ASF headers.
>
> Everything else is good. I checked:
> - name includes incubating
> - DISCLAIMER exists
> - LICENSE and NOTICE all good
> - No unexpected binary files
> - All source files have ASF headers
> - Can compile form source
>
> Thanks,
> Justin.
>
> 1. apache-servicecomb-incubating-java-chassis-distribution-1.0.
> 0-m1-src/etc/eclipse-java-google-style.xml
> 2. apache-servicecomb-incubating-java-chassis-distribution-1.0.
> 0-m1-src/etc/intellij-java-google-style.xml
> 3. https://www.apache.org/legal/resolved.html#category-b
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1

[Matt Sicker]

I need to get more familiar with that license list!

Changing to -1 to have licensing fixed

On 23 March 2018 at 19:22, Justin Mclean  wrote:

> Hi,
>
> Sorry but it’s -1 binding from me as the source release contains some
> CC-BY licensed content in plain text. [1][2] CC-BY is considered Category B
> [3] and can’t be included in a source release. These files also incorrectly
> IMO have ASF headers.
>
> Everything else is good. I checked:
> - name includes incubating
> - DISCLAIMER exists
> - LICENSE and NOTICE all good
> - No unexpected binary files
> - All source files have ASF headers
> - Can compile form source
>
> Thanks,
> Justin.
>
> 1. apache-servicecomb-incubating-java-chassis-distribution-1.0.
> 0-m1-src/etc/eclipse-java-google-style.xml
> 2. apache-servicecomb-incubating-java-chassis-distribution-1.0.
> 0-m1-src/etc/intellij-java-google-style.xml
> 3. https://www.apache.org/legal/resolved.html#category-b
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Matt Sicker 

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[Justin Mclean]

Hi,

-1 binding as NOTICE is incorrect. This normally would be is a minor thing but 
you have been previously asked to fix this. [1]

Also unable to build from source please include instruction on how to build 
from source in the releasee.

I checked:
- incubating in name
- signatures and hashed good
- DISCLAIMER exists
- LICENSE is correct
- NOTICE has incorrect year 2016 and is missing information [1]
- No binary files in release
- Source files have ASF headers
- unable to build from source

When trying to build from source I get an error. It's likely that the version 
of protobuf I use is more recent than what is required. Perhaps you should 
consider updating?

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/10fd534d9ea4b0a4574637ab49e5d823a47a864ec27f317f90b14196@%3Cgeneral.incubator.apache.org%3E

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2

[Justin Mclean]

Hi,

-1 binding due to bundled crypto code. If the crypto process been done and just 
not recorded yet or I missed it happy to change my vote.

Everything else is mostly OK. I checked:
- incubating in name
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE look OK (except for below) but I didn’t do an exhaustive 
check
- All source files have ASF headers
- No unexpected binary files
- Can compile from source

The entry for the crate code [1] in LICENSE may need expanding on as I notice 
there a number pf sub projects which have different copyright years in their 
headers and not all of the code is under BSD. The LICENSE file need updating 
for that. I also fail to see any mention that this source release contains 
cryptography code [2] and I don’t see the project listed here [3].

Thanks,
Justin

1. traffic_ops/traffic_ops_golang/vendor/golang.org/x/crypto
2. https://www.apache.org/dev/crypto.html#inform
3. http://www.apache.org/licenses/exports/


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

Give a speech about Apache SkyWalking (Incubating) in QCon Beijing 2018

[???? Sheng Wu]

Hi IPMC,


I have been invited and are going to give a speech about Apache SkyWalking 
(Incubating) in QCon Beijing 2018. The subject is `the Development of 
SkyWalking, from a small project into global community`. Most things in that 
speech will be about the project itself, and its development, such as, refactor 
and rewrite 4 times in 2 years, work in global community with Zipkin, CNCF 
OpenTracing, Distributed tracing workshop, etc. And of course, will mention 
Chinese Apache projects(including TLP and Incubating), and show our honor to be 
part of them.


I will notice every time, I mention the project with `(incubating)` or 
`??`(incubating in Chinese).


I send this mail to inform the IPMC, in case there are others things I should 
take care. Hope IPMC community gives me some advices to do so. 


Here is QCon page: https://2018.qconbeijing.com/presentation/445 Aprial 20th, 
2018, Beijing.


--
Sheng Wu
Apache SkyWalking original creator and PPMC member

Re: Altering PMC for graduation

[John D. Ament]

On Fri, Mar 23, 2018 at 9:02 PM David Neuman 
wrote:

> Great, thanks a lot for the info John.  Since I have spoken to each of the
> PMC members in question individually, I think we are safe to make our
> changes and have them continue on as committers.
>

Remember, if it didn't happen on list it didn't happen.  Please make sure
you check with these individuals on list.


>
> On Fri, Mar 23, 2018 at 16:27 John D. Ament  wrote:
>
> > Its quite common that people stop working on open source projects.
> > However, part of the Apache way is merit never expires.  While you may
> not
> > want to include them in your PMC, keeping them available as a committer
> > isn't a bad thing.
> >
> > Most podlings I've seen will send an email "here's the proposed PMC,
> speak
> > up if you need a change."  If any of those people want to be on the PMC,
> > still honor their request.  However if they are not interested then its
> > safe to assume they would have responded.
> >
> > I do recommend if you are going to make changes, that the changes are
> > finalized in the roster before submitting the resolution to the board.
> > This may involve sending the IPMC notices for new PPMC members ahead of
> > time, just to keep it clean.  Having your roster correct means everyone
> > gets the right permissions without the chair having to do anything.
> >
> > John
> >
> > On Fri, Mar 23, 2018 at 6:14 PM Carlos Santana 
> > wrote:
> >
> > > For Apache OpenWhisk we are in same situation so it would be good to
> > > understand the guideline on how to handle such situation.
> > >
> > > - Carlos Santana
> > > @csantanapr
> > >
> > > > On Mar 23, 2018, at 4:06 PM, Dave Neuman  wrote:
> > > >
> > > > Hey IPMC,
> > > > I had a question about altering the PMC for graduation.
> > > > We have a few folks who are no longer active participants in our
> > project
> > > > that are still a part of our PMC.  In the process of generating our
> > > > graduation resolution we were wondering if we could take the
> > opportunity
> > > to
> > > > have these members just be committers and not PMC members anymore?
> If
> > > yes,
> > > > what would the process look like, would it be enough to just make the
> > > > roster alterations in Whimsy?  I have already spoken to each of these
> > > > people individually and made sure they were on-board with just being
> > > > committers and not PMC members.
> > > >
> > > > We are really excited to draft our resolution and I think this is the
> > > last
> > > > thing standing in our way!
> > > >
> > > >
> > > > Thanks in advance for the help!
> > > >
> > > > Dave
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: Altering PMC for graduation

[David Neuman]

Great, thanks a lot for the info John.  Since I have spoken to each of the
PMC members in question individually, I think we are safe to make our
changes and have them continue on as committers.

On Fri, Mar 23, 2018 at 16:27 John D. Ament  wrote:

> Its quite common that people stop working on open source projects.
> However, part of the Apache way is merit never expires.  While you may not
> want to include them in your PMC, keeping them available as a committer
> isn't a bad thing.
>
> Most podlings I've seen will send an email "here's the proposed PMC, speak
> up if you need a change."  If any of those people want to be on the PMC,
> still honor their request.  However if they are not interested then its
> safe to assume they would have responded.
>
> I do recommend if you are going to make changes, that the changes are
> finalized in the roster before submitting the resolution to the board.
> This may involve sending the IPMC notices for new PPMC members ahead of
> time, just to keep it clean.  Having your roster correct means everyone
> gets the right permissions without the chair having to do anything.
>
> John
>
> On Fri, Mar 23, 2018 at 6:14 PM Carlos Santana 
> wrote:
>
> > For Apache OpenWhisk we are in same situation so it would be good to
> > understand the guideline on how to handle such situation.
> >
> > - Carlos Santana
> > @csantanapr
> >
> > > On Mar 23, 2018, at 4:06 PM, Dave Neuman  wrote:
> > >
> > > Hey IPMC,
> > > I had a question about altering the PMC for graduation.
> > > We have a few folks who are no longer active participants in our
> project
> > > that are still a part of our PMC.  In the process of generating our
> > > graduation resolution we were wondering if we could take the
> opportunity
> > to
> > > have these members just be committers and not PMC members anymore?  If
> > yes,
> > > what would the process look like, would it be enough to just make the
> > > roster alterations in Whimsy?  I have already spoken to each of these
> > > people individually and made sure they were on-board with just being
> > > committers and not PMC members.
> > >
> > > We are really excited to draft our resolution and I think this is the
> > last
> > > thing standing in our way!
> > >
> > >
> > > Thanks in advance for the help!
> > >
> > > Dave
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [Vote] Release of Apache-Griffin-0.2.0-incubating [RC1]

[Justin Mclean]

Hi,

-1 for other reasons than stated by other people. i.e. the source file LICENSE 
file needs work.

Although "unapproved licenses" is misleading as it’s just that those files 
don’t (and shouldn’t) have headers.

I checked:
- incubating in artefact name
- signatures and hashes correct
- LICENSE needs some work and incorrectly lists software that is not bundled in 
the source release [2]
- NOTICE year is incorrect

The start of the license file is a little odd, I suggest using the same format 
as other projects. "Notices for third-party software” is confusing as they 
usually go in the NOTICE file not the LICENSE file. You are also missing the 
full text of the Apache license.

Please do not use URL pointers to licenses, while it useful to know where it 
come from so don’t remove them, these license can change over time or 
disappear. Pleas include the full text of the license in question in the 
release and point to that. [1] Note that for both MIT and B?SD this includes a 
copyright line so you can’t use the same text for all MIT or all BSD licenses, 
please don’t break this up as you have done here. I suggest you follow this [1]

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
2. http://www.apache.org/dev/licensing-howto.html#guiding-principle
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1

[Justin Mclean]

Hi,

Sorry but it’s -1 binding from me as the source release contains some CC-BY 
licensed content in plain text. [1][2] CC-BY is considered Category B [3] and 
can’t be included in a source release. These files also incorrectly IMO have 
ASF headers.

Everything else is good. I checked:
- name includes incubating
- DISCLAIMER exists
- LICENSE and NOTICE all good
- No unexpected binary files
- All source files have ASF headers
- Can compile form source

Thanks,
Justin.

1. 
apache-servicecomb-incubating-java-chassis-distribution-1.0.0-m1-src/etc/eclipse-java-google-style.xml
2. 
apache-servicecomb-incubating-java-chassis-distribution-1.0.0-m1-src/etc/intellij-java-google-style.xml
3. https://www.apache.org/legal/resolved.html#category-b
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.1.0

[Justin Mclean]

Hi,

+1 binding 

I checked:
- name includes incubating
- DISCLAIMER exists
- LICENSE and NOTICE all good
- No unexpected binary files
- All source files have ASF headers
- Can compile form source

Thanks,
Justin

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

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1 - Second Attempt

[Justin Mclean]

Hi,

+1 binding 

I checked:
- name includes incubating
- DISCLAIMER exists
- LICENSE and NOTICE all good
- No unexpected binary files
- All source files have ASF headers
- Can compile form source

Thanks,
Justin

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

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha(2nd round)

[???? Sheng Wu]

John,


OK. Thanks. :)  We shared a check list document for SkyWalking committer and 
ppmc to vote.


 
---Original---
From: "John D. Ament"
Date: Sat, Mar 24, 2018 06:20 AM
To: "general";
Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 
5.0.0-alpha(2nd round)


Sheng,

Its perfectly acceptable for PPMC members to vote on the release here.
From my point of view, it gives me a better feeling that the PPMC knows the
steps required to have a valid release go out the door, what checks have to
be done.  So I encourage PPMC members to vote here, please don't discourage
it.

John

On Fri, Mar 23, 2018 at 10:38 AM Sheng Wu  wrote:

> Xin
>
> You have already voted in SkyWalking dev mail list. That thread is already
> included in this mail. This vote is for IPMC and other Apache community
> people to check our release.
>
> Thanks.
>
> On 2018/03/23 14:00:55, xin zhang  wrote:
> > +1
> >
> > Checked the signed Keys and checksum.
> > Checked the binary with the examples.
> > Run the rat to verify the License header issue.
> > DISCLAIMER exists
> > Verify the nexus Staging repo by running the demo example
> > Compiled from source
> > Checked for archive matching git tag
> >
> >
> >
> > On Fri, Mar 23, 2018 at 11:13 AM, Matt Sicker  wrote:
> >
> > > +1
> > >
> > > * Signatures ok
> > > * Builds ok
> > > * Tests are failing with a NullPointerException inside
> > > maven-surefire-plugin, not sure why.
> > > * Rat check ok
> > >
> > > On 22 March 2018 at 21:47,  Sheng Wu  wrote:
> > >
> > > > Hi All,
> > > > This is a call for vote to release Apache SkyWalking (Incubating)
> version
> > > > 5.0.0-alpha
> > > >
> > > >
> > > >
> > > > The Apache SkyWalking community has tested, voted and approved the
> > > proposed
> > > > release of Apache SkyWalking (Incubating) 5.0.0-alpha
> > > >
> > > > We now kindly request the Incubator PMC members review and vote on
> this
> > > > incubator release.
> > > >
> > > >
> > > > Skywalking is an APM (application performance monitor), especially
> for
> > > > microservice, Cloud Native and container-based architecture systems.
> Also
> > > > known as a distributed tracing system. It provides an automatic way
> to
> > > > instrument applications: no need to change any of the source code of
> the
> > > > target application; and an collector with an very high efficiency
> > > streaming
> > > > module.
> > > >
> > > >
> > > > This is the first and alpha release of version 5. We write a Release
> > > > Guide[1] and vote check list[2] by following Apache release and
> > > > distribution documents.
> > > >
> > > >
> > > >
> > > > Vote Thread:
> > > >
> > > >
> > > >  *
> https://lists.apache.org/thread.html/5abdab49ced0ab10059f99157fb983
> > > > 002352205f0ba6469181ec053f@%3Cdev.skywalking.apache.org%3E
> > > >
> > > >
> > > > Result Thread:
> > > >
> > > >
> > > >  *
> https://lists.apache.org/thread.html/6aaf3f5d2c0c1289796c9b658ac812
> > > > cea2c4b6d619b78dbeb1566a4e@%3Cdev.skywalking.apache.org%3E
> > > >
> > > >
> > > > Release notes:
> > > >
> > > >
> > > >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > > > 0.0-alpha/CHANGES.md
> > > >
> > > >
> > > > Release Candidate:
> > > >
> > > >
> > > >  * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > > > 5.0.0-alpha/
> > > >
> > > >
> > > > Maven 2 staging repository:
> > > >
> > > >
> > > >  * https://repository.apache.org/content/repositories/
> > > > orgapacheskywalking-1005/org/apache/skywalking/apache-
> > > > skywalking-apm-incubating/5.0.0-alpha/
> > > >
> > > >
> > > > Release Tag :
> > > >
> > > >
> > > >  * v5.0.0-alpha
> > > >
> > > >
> > > > Release CommitID :
> > > >
> > > >
> > > >  * f52d99498f02402d2ce1a0b7b909cd7fcfb3526f
> > > >
> > > >
> > > > Keys to verify the Release Candidate :
> > > >
> > > >
> > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > > > 5.0.0-alpha/KEYS
> > > > *
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777
> > > >
> > > > corresponding to pen...@apache.org
> > > >
> > > >
> > > > Guide to build the release from source :
> > > >
> > > >
> > > >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > > > 0.0-alpha/docs/en/How-to-release.md
> > > >
> > > >
> > > > Voting will start now (March 23th, 2018) and will remain open for at
> > > least
> > > > 72 hours, Request IPMC to give their vote.
> > > > [ ] +1 Release this package.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 Do not release this package because
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1] https://github.com/apache/incubator-skywalking/blob/
> > > > master/docs/en/How-to-release.md
> > > > [2] https://github.com/apache/incubator-skywalking/blob/
> > > > master/docs/en/How-to-release.md#vote-check
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sheng Wu
> > > > Apache SkyWalking original creator and PPMC member
> > >
> > >
> > >
> > >
> > > --
> > > Matt Sicker 
> > >
> >
>
> --

Re: Altering PMC for graduation

[John D. Ament]

Its quite common that people stop working on open source projects.
However, part of the Apache way is merit never expires.  While you may not
want to include them in your PMC, keeping them available as a committer
isn't a bad thing.

Most podlings I've seen will send an email "here's the proposed PMC, speak
up if you need a change."  If any of those people want to be on the PMC,
still honor their request.  However if they are not interested then its
safe to assume they would have responded.

I do recommend if you are going to make changes, that the changes are
finalized in the roster before submitting the resolution to the board.
This may involve sending the IPMC notices for new PPMC members ahead of
time, just to keep it clean.  Having your roster correct means everyone
gets the right permissions without the chair having to do anything.

John

On Fri, Mar 23, 2018 at 6:14 PM Carlos Santana  wrote:

> For Apache OpenWhisk we are in same situation so it would be good to
> understand the guideline on how to handle such situation.
>
> - Carlos Santana
> @csantanapr
>
> > On Mar 23, 2018, at 4:06 PM, Dave Neuman  wrote:
> >
> > Hey IPMC,
> > I had a question about altering the PMC for graduation.
> > We have a few folks who are no longer active participants in our project
> > that are still a part of our PMC.  In the process of generating our
> > graduation resolution we were wondering if we could take the opportunity
> to
> > have these members just be committers and not PMC members anymore?  If
> yes,
> > what would the process look like, would it be enough to just make the
> > roster alterations in Whimsy?  I have already spoken to each of these
> > people individually and made sure they were on-board with just being
> > committers and not PMC members.
> >
> > We are really excited to draft our resolution and I think this is the
> last
> > thing standing in our way!
> >
> >
> > Thanks in advance for the help!
> >
> > Dave
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Two new Samoa committers

[John D. Ament]

I suspect its a bad/out dated mail template, or secretary did extra work.
I haven't had to do anything for new podling committers in quite a while.
If something does come up, feel free to ping me and I'll help get it
situated.

I'll also see if I can figure out how to get the email from root updated.

John

On Fri, Mar 23, 2018 at 10:28 AM Alan Gates  wrote:

> When I got the email from root@apache it said:
>
> 
> Please grant additional karma to the projects in your domain
> you wish the user to have commit to.
>
> Only PMC chairs can grant karma.  If needed, please post to the general@/
> dev@/private@ list of your project asking for someone with sufficient
> karma to grant access to 'pwawrzyniak'.
> 
>
> If this is old and no longer applicable and there's nothing else to do,
> then feel free to ignore my request.
>
> Alan.
>
> On Thu, Mar 22, 2018 at 4:07 PM, John D. Ament 
> wrote:
>
> > Alan,
> >
> > i'm not sure what karma you're looking for.  I just checked both
> accounts.
> >
> > - If samoa is using git-wip-us then they already have access as they are
> > committers on incubator (this was likely done by secretary)
> > - If samoa is using gitbox/github then they already have access as they
> are
> > committers on samoa (this may have also been done by secretary)
> >
> > I checked https://whimsy.apache.org/roster/ppmc/samoa to confirm
> > membership
> > of both.  You (as well as the rest of the samoa PPMC) should have access
> to
> > this page to manipulate the roster.
> >
> > Is there anything that they can't do?
> >
> > John
> >
> > On Thu, Mar 22, 2018 at 6:27 PM Alan Gates  wrote:
> >
> > > John, can you grant karma on Samoa to Piotr Wawrzyniak (pwawrzyniak)
> and
> > > Maciej Grzenda (mgrzenda).  Both have recently been voted in as
> > > committers.  Their id's have been created but I do not have power to
> > grant
> > > them karma.  Thanks.
> > >
> > > Alan.
> > >
> >
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)

[John D. Ament]

Sheng,

Its perfectly acceptable for PPMC members to vote on the release here.
>From my point of view, it gives me a better feeling that the PPMC knows the
steps required to have a valid release go out the door, what checks have to
be done.  So I encourage PPMC members to vote here, please don't discourage
it.

John

On Fri, Mar 23, 2018 at 10:38 AM Sheng Wu  wrote:

> Xin
>
> You have already voted in SkyWalking dev mail list. That thread is already
> included in this mail. This vote is for IPMC and other Apache community
> people to check our release.
>
> Thanks.
>
> On 2018/03/23 14:00:55, xin zhang  wrote:
> > +1
> >
> > Checked the signed Keys and checksum.
> > Checked the binary with the examples.
> > Run the rat to verify the License header issue.
> > DISCLAIMER exists
> > Verify the nexus Staging repo by running the demo example
> > Compiled from source
> > Checked for archive matching git tag
> >
> >
> >
> > On Fri, Mar 23, 2018 at 11:13 AM, Matt Sicker  wrote:
> >
> > > +1
> > >
> > > * Signatures ok
> > > * Builds ok
> > > * Tests are failing with a NullPointerException inside
> > > maven-surefire-plugin, not sure why.
> > > * Rat check ok
> > >
> > > On 22 March 2018 at 21:47, 吴晟 Sheng Wu  wrote:
> > >
> > > > Hi All,
> > > > This is a call for vote to release Apache SkyWalking (Incubating)
> version
> > > > 5.0.0-alpha
> > > >
> > > >
> > > >
> > > > The Apache SkyWalking community has tested, voted and approved the
> > > proposed
> > > > release of Apache SkyWalking (Incubating) 5.0.0-alpha
> > > >
> > > > We now kindly request the Incubator PMC members review and vote on
> this
> > > > incubator release.
> > > >
> > > >
> > > > Skywalking is an APM (application performance monitor), especially
> for
> > > > microservice, Cloud Native and container-based architecture systems.
> Also
> > > > known as a distributed tracing system. It provides an automatic way
> to
> > > > instrument applications: no need to change any of the source code of
> the
> > > > target application; and an collector with an very high efficiency
> > > streaming
> > > > module.
> > > >
> > > >
> > > > This is the first and alpha release of version 5. We write a Release
> > > > Guide[1] and vote check list[2] by following Apache release and
> > > > distribution documents.
> > > >
> > > >
> > > >
> > > > Vote Thread:
> > > >
> > > >
> > > >  *
> https://lists.apache.org/thread.html/5abdab49ced0ab10059f99157fb983
> > > > 002352205f0ba6469181ec053f@%3Cdev.skywalking.apache.org%3E
> > > >
> > > >
> > > > Result Thread:
> > > >
> > > >
> > > >  *
> https://lists.apache.org/thread.html/6aaf3f5d2c0c1289796c9b658ac812
> > > > cea2c4b6d619b78dbeb1566a4e@%3Cdev.skywalking.apache.org%3E
> > > >
> > > >
> > > > Release notes:
> > > >
> > > >
> > > >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > > > 0.0-alpha/CHANGES.md
> > > >
> > > >
> > > > Release Candidate:
> > > >
> > > >
> > > >  * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > > > 5.0.0-alpha/
> > > >
> > > >
> > > > Maven 2 staging repository:
> > > >
> > > >
> > > >  * https://repository.apache.org/content/repositories/
> > > > orgapacheskywalking-1005/org/apache/skywalking/apache-
> > > > skywalking-apm-incubating/5.0.0-alpha/
> > > >
> > > >
> > > > Release Tag :
> > > >
> > > >
> > > >  * v5.0.0-alpha
> > > >
> > > >
> > > > Release CommitID :
> > > >
> > > >
> > > >  * f52d99498f02402d2ce1a0b7b909cd7fcfb3526f
> > > >
> > > >
> > > > Keys to verify the Release Candidate :
> > > >
> > > >
> > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > > > 5.0.0-alpha/KEYS
> > > > *
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777
> > > >
> > > > corresponding to pen...@apache.org
> > > >
> > > >
> > > > Guide to build the release from source :
> > > >
> > > >
> > > >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > > > 0.0-alpha/docs/en/How-to-release.md
> > > >
> > > >
> > > > Voting will start now (March 23th, 2018) and will remain open for at
> > > least
> > > > 72 hours, Request IPMC to give their vote.
> > > > [ ] +1 Release this package.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 Do not release this package because
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1] https://github.com/apache/incubator-skywalking/blob/
> > > > master/docs/en/How-to-release.md
> > > > [2] https://github.com/apache/incubator-skywalking/blob/
> > > > master/docs/en/How-to-release.md#vote-check
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sheng Wu
> > > > Apache SkyWalking original creator and PPMC member
> > >
> > >
> > >
> > >
> > > --
> > > Matt Sicker 
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Altering PMC for graduation

[Carlos Santana]

For Apache OpenWhisk we are in same situation so it would be good to understand 
the guideline on how to handle such situation. 

- Carlos Santana
@csantanapr

> On Mar 23, 2018, at 4:06 PM, Dave Neuman  wrote:
> 
> Hey IPMC,
> I had a question about altering the PMC for graduation.
> We have a few folks who are no longer active participants in our project
> that are still a part of our PMC.  In the process of generating our
> graduation resolution we were wondering if we could take the opportunity to
> have these members just be committers and not PMC members anymore?  If yes,
> what would the process look like, would it be enough to just make the
> roster alterations in Whimsy?  I have already spoken to each of these
> people individually and made sure they were on-board with just being
> committers and not PMC members.
> 
> We are really excited to draft our resolution and I think this is the last
> thing standing in our way!
> 
> 
> Thanks in advance for the help!
> 
> Dave

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

Altering PMC for graduation

[Dave Neuman]

Hey IPMC,
I had a question about altering the PMC for graduation.
We have a few folks who are no longer active participants in our project
that are still a part of our PMC.  In the process of generating our
graduation resolution we were wondering if we could take the opportunity to
have these members just be committers and not PMC members anymore?  If yes,
what would the process look like, would it be enough to just make the
roster alterations in Whimsy?  I have already spoken to each of these
people individually and made sure they were on-board with just being
committers and not PMC members.

We are really excited to draft our resolution and I think this is the last
thing standing in our way!


Thanks in advance for the help!

Dave

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[Matt Sicker]

* Rat check ok
* Signatures ok

I'm having issues building from source. I fixed on issue involving protoc
by installing version 2.5 (as used in the travis config) and adding it to
my PATH for the build. However, I came across another error:

[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-compiler-plugin:3.5:compile (default-compile) on project
omid-hbase-tools: Compilation failure: Compilation failure:
[ERROR] /Users/matt/Downloads/apache-omid-incubating-0.9.0.0-src/
hbase-tools/src/main/java/org/apache/omid/tools/hbase/OmidTableManager.java:[33,23]
cannot find symbol
[ERROR]   symbol:   class HBaseShims
[ERROR]   location: package org.apache.omid
[ERROR] /Users/matt/Downloads/apache-omid-incubating-0.9.0.0-src/
hbase-tools/src/main/java/org/apache/omid/tools/hbase/OmidTableManager.java:[153,13]
cannot find symbol
[ERROR]   symbol:   variable HBaseShims
[ERROR]   location: class org.apache.omid.tools.hbase.OmidTableManager

I attempted to rerun the tests with the "hbase-0" profile activated, but
that caused test failures:

Failed tests:

TestTSOClientConnectionToTSO.testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing:214
» Execution
  TestTSOClientConnectionToTSO.testSuccessfulConnectionToTSOThroughZK:176 »
Execution


On 23 March 2018 at 10:33, James Taylor  wrote:

> Forwarding my +1 from the dev list.
>
> James
>
> On Thu, Mar 22, 2018 at 8:31 AM Henk P. Penning  wrote:
>
> > On Thu, 22 Mar 2018, Ohad Shacham wrote:
> >
> > > Date: Thu, 22 Mar 2018 13:29:55 +0100
> > > From: Ohad Shacham 
> > > To: general@incubator.apache.org
> > > Subject: [VOTE] Release Apache Omid 0.9.0.0 (incubating)
> > >
> > > Hi,
> > >
> > >
> > > The Apache Omid community has voted on and approved a proposal
> > > to release Apache Omid 0.9.0.0-incubating.
> >
> > > MD5 Hash:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc1/apache-omid-incubating-0.9.0.0-src.tar.gz.md5
> >
> >Please do NOT publish .md5's anymore.
> >Please DO publish a .sha1, .sha256 or .sha512 instead.
> >
> >https://www.apache.org/dev/release-distribution#sigs-and-sums
> >
> >There is no need to re-vote ; just fix dist/dev/incubator/omid/
> >before you publish.
> >
> > > Ohad
> >
> >Regards,
> >
> >Henk Penning
> >
> >    _
> > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> > Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Matt Sicker 

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1

[Matt Sicker]

+1

* Signatures ok
* Build and test ok
* Rat check has errors regarding files in
java-chassis-distribution/src/release/licenses/, though adding that to the
excludes in the root pom.xml fixes those errors.

On 23 March 2018 at 04:16, Mohammad Asif Siddiqui 
wrote:

>  Hi All,
>
> This is a call for vote to release Apache ServiceComb Java-Chassis
> (Incubating) version 1.0.0-m1
>
> Apache ServiceComb (Incubating) Community has voted and approved the
> release.
>
> Vote Thread : https://lists.apache.org/thread.html/
> b778a8787435b963c0743c518c3bc0b4c419a4010edc369f2c12c43c@%
> 3Cdev.servicecomb.apache.org%3E
>
> Result Thread : https://lists.apache.org/thread.html/
> 81f6fd78e0577853c07e5a1924a9cf5a9c17aba5dd725d58fa397bea@%
> 3Cdev.servicecomb.apache.org%3E
>
> Release Notes : https://github.com/apache/incubator-servicecomb-java-
> chassis/blob/master/etc/releaseNotes.md
>
> Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/
>
> Staging Repo : https://repository.apache.org/content/repositories/
> orgapacheservicecomb-1196/
>
> Release Tag : https://github.com/apache/incubator-servicecomb-java-
> chassis/releases/tag/1.0.0-m1
>
> Release CommitID : 901869b987c6f65c92b5b8b8f05eaf0f9f6e69cb
>
> Keys to verify the Release Candidate : https://dist.apache.org/repos/
> dist/dev/incubator/servicecomb/KEYS
>
> Voting will start now ( Friday, 23rd March, 2018) and will remain open for
> next 72 hours, we request all IPMC members to give their vote.
>
> [ ] +1 Release this package as 1.0.0-m1
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because
>
> Regards
> Asif
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Matt Sicker 

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[James Taylor]

Forwarding my +1 from the dev list.

James

On Thu, Mar 22, 2018 at 8:31 AM Henk P. Penning  wrote:

> On Thu, 22 Mar 2018, Ohad Shacham wrote:
>
> > Date: Thu, 22 Mar 2018 13:29:55 +0100
> > From: Ohad Shacham 
> > To: general@incubator.apache.org
> > Subject: [VOTE] Release Apache Omid 0.9.0.0 (incubating)
> >
> > Hi,
> >
> >
> > The Apache Omid community has voted on and approved a proposal
> > to release Apache Omid 0.9.0.0-incubating.
>
> > MD5 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc1/apache-omid-incubating-0.9.0.0-src.tar.gz.md5
>
>Please do NOT publish .md5's anymore.
>Please DO publish a .sha1, .sha256 or .sha512 instead.
>
>https://www.apache.org/dev/release-distribution#sigs-and-sums
>
>There is no need to re-vote ; just fix dist/dev/incubator/omid/
>before you publish.
>
> > Ohad
>
>Regards,
>
>Henk Penning
>
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)

[Sheng Wu]

Xin

You have already voted in SkyWalking dev mail list. That thread is already 
included in this mail. This vote is for IPMC and other Apache community people 
to check our release.

Thanks.

On 2018/03/23 14:00:55, xin zhang  wrote: 
> +1
> 
> Checked the signed Keys and checksum.
> Checked the binary with the examples.
> Run the rat to verify the License header issue.
> DISCLAIMER exists
> Verify the nexus Staging repo by running the demo example
> Compiled from source
> Checked for archive matching git tag
> 
> 
> 
> On Fri, Mar 23, 2018 at 11:13 AM, Matt Sicker  wrote:
> 
> > +1
> >
> > * Signatures ok
> > * Builds ok
> > * Tests are failing with a NullPointerException inside
> > maven-surefire-plugin, not sure why.
> > * Rat check ok
> >
> > On 22 March 2018 at 21:47, 吴晟 Sheng Wu  wrote:
> >
> > > Hi All,
> > > This is a call for vote to release Apache SkyWalking (Incubating) version
> > > 5.0.0-alpha
> > >
> > >
> > >
> > > The Apache SkyWalking community has tested, voted and approved the
> > proposed
> > > release of Apache SkyWalking (Incubating) 5.0.0-alpha
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > >
> > > Skywalking is an APM (application performance monitor), especially for
> > > microservice, Cloud Native and container-based architecture systems. Also
> > > known as a distributed tracing system. It provides an automatic way to
> > > instrument applications: no need to change any of the source code of the
> > > target application; and an collector with an very high efficiency
> > streaming
> > > module.
> > >
> > >
> > > This is the first and alpha release of version 5. We write a Release
> > > Guide[1] and vote check list[2] by following Apache release and
> > > distribution documents.
> > >
> > >
> > >
> > > Vote Thread:
> > >
> > >
> > >  * https://lists.apache.org/thread.html/5abdab49ced0ab10059f99157fb983
> > > 002352205f0ba6469181ec053f@%3Cdev.skywalking.apache.org%3E
> > >
> > >
> > > Result Thread:
> > >
> > >
> > >  * https://lists.apache.org/thread.html/6aaf3f5d2c0c1289796c9b658ac812
> > > cea2c4b6d619b78dbeb1566a4e@%3Cdev.skywalking.apache.org%3E
> > >
> > >
> > > Release notes:
> > >
> > >
> > >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > > 0.0-alpha/CHANGES.md
> > >
> > >
> > > Release Candidate:
> > >
> > >
> > >  * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > > 5.0.0-alpha/
> > >
> > >
> > > Maven 2 staging repository:
> > >
> > >
> > >  * https://repository.apache.org/content/repositories/
> > > orgapacheskywalking-1005/org/apache/skywalking/apache-
> > > skywalking-apm-incubating/5.0.0-alpha/
> > >
> > >
> > > Release Tag :
> > >
> > >
> > >  * v5.0.0-alpha
> > >
> > >
> > > Release CommitID :
> > >
> > >
> > >  * f52d99498f02402d2ce1a0b7b909cd7fcfb3526f
> > >
> > >
> > > Keys to verify the Release Candidate :
> > >
> > >
> > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > > 5.0.0-alpha/KEYS
> > > * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777
> > >
> > > corresponding to pen...@apache.org
> > >
> > >
> > > Guide to build the release from source :
> > >
> > >
> > >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > > 0.0-alpha/docs/en/How-to-release.md
> > >
> > >
> > > Voting will start now (March 23th, 2018) and will remain open for at
> > least
> > > 72 hours, Request IPMC to give their vote.
> > > [ ] +1 Release this package.
> > > [ ] +0 No opinion.
> > > [ ] -1 Do not release this package because
> > >
> > >
> > >
> > >
> > >
> > > [1] https://github.com/apache/incubator-skywalking/blob/
> > > master/docs/en/How-to-release.md
> > > [2] https://github.com/apache/incubator-skywalking/blob/
> > > master/docs/en/How-to-release.md#vote-check
> > >
> > >
> > >
> > >
> > > --
> > > Sheng Wu
> > > Apache SkyWalking original creator and PPMC member
> >
> >
> >
> >
> > --
> > Matt Sicker 
> >
> 

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

Re: Two new Samoa committers

[Alan Gates]

When I got the email from root@apache it said:


Please grant additional karma to the projects in your domain
you wish the user to have commit to.

Only PMC chairs can grant karma.  If needed, please post to the general@/
dev@/private@ list of your project asking for someone with sufficient
karma to grant access to 'pwawrzyniak'.


If this is old and no longer applicable and there's nothing else to do,
then feel free to ignore my request.

Alan.

On Thu, Mar 22, 2018 at 4:07 PM, John D. Ament 
wrote:

> Alan,
>
> i'm not sure what karma you're looking for.  I just checked both accounts.
>
> - If samoa is using git-wip-us then they already have access as they are
> committers on incubator (this was likely done by secretary)
> - If samoa is using gitbox/github then they already have access as they are
> committers on samoa (this may have also been done by secretary)
>
> I checked https://whimsy.apache.org/roster/ppmc/samoa to confirm
> membership
> of both.  You (as well as the rest of the samoa PPMC) should have access to
> this page to manipulate the roster.
>
> Is there anything that they can't do?
>
> John
>
> On Thu, Mar 22, 2018 at 6:27 PM Alan Gates  wrote:
>
> > John, can you grant karma on Samoa to Piotr Wawrzyniak (pwawrzyniak) and
> > Maciej Grzenda (mgrzenda).  Both have recently been voted in as
> > committers.  Their id's have been created but I do not have power to
> grant
> > them karma.  Thanks.
> >
> > Alan.
> >
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)

[xin zhang]

+1

Checked the signed Keys and checksum.
Checked the binary with the examples.
Run the rat to verify the License header issue.
DISCLAIMER exists
Verify the nexus Staging repo by running the demo example
Compiled from source
Checked for archive matching git tag



On Fri, Mar 23, 2018 at 11:13 AM, Matt Sicker  wrote:

> +1
>
> * Signatures ok
> * Builds ok
> * Tests are failing with a NullPointerException inside
> maven-surefire-plugin, not sure why.
> * Rat check ok
>
> On 22 March 2018 at 21:47, 吴晟 Sheng Wu  wrote:
>
> > Hi All,
> > This is a call for vote to release Apache SkyWalking (Incubating) version
> > 5.0.0-alpha
> >
> >
> >
> > The Apache SkyWalking community has tested, voted and approved the
> proposed
> > release of Apache SkyWalking (Incubating) 5.0.0-alpha
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> >
> > Skywalking is an APM (application performance monitor), especially for
> > microservice, Cloud Native and container-based architecture systems. Also
> > known as a distributed tracing system. It provides an automatic way to
> > instrument applications: no need to change any of the source code of the
> > target application; and an collector with an very high efficiency
> streaming
> > module.
> >
> >
> > This is the first and alpha release of version 5. We write a Release
> > Guide[1] and vote check list[2] by following Apache release and
> > distribution documents.
> >
> >
> >
> > Vote Thread:
> >
> >
> >  * https://lists.apache.org/thread.html/5abdab49ced0ab10059f99157fb983
> > 002352205f0ba6469181ec053f@%3Cdev.skywalking.apache.org%3E
> >
> >
> > Result Thread:
> >
> >
> >  * https://lists.apache.org/thread.html/6aaf3f5d2c0c1289796c9b658ac812
> > cea2c4b6d619b78dbeb1566a4e@%3Cdev.skywalking.apache.org%3E
> >
> >
> > Release notes:
> >
> >
> >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > 0.0-alpha/CHANGES.md
> >
> >
> > Release Candidate:
> >
> >
> >  * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > 5.0.0-alpha/
> >
> >
> > Maven 2 staging repository:
> >
> >
> >  * https://repository.apache.org/content/repositories/
> > orgapacheskywalking-1005/org/apache/skywalking/apache-
> > skywalking-apm-incubating/5.0.0-alpha/
> >
> >
> > Release Tag :
> >
> >
> >  * v5.0.0-alpha
> >
> >
> > Release CommitID :
> >
> >
> >  * f52d99498f02402d2ce1a0b7b909cd7fcfb3526f
> >
> >
> > Keys to verify the Release Candidate :
> >
> >
> > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/
> > 5.0.0-alpha/KEYS
> > * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777
> >
> > corresponding to pen...@apache.org
> >
> >
> > Guide to build the release from source :
> >
> >
> >  * https://github.com/apache/incubator-skywalking/blob/v5.
> > 0.0-alpha/docs/en/How-to-release.md
> >
> >
> > Voting will start now (March 23th, 2018) and will remain open for at
> least
> > 72 hours, Request IPMC to give their vote.
> > [ ] +1 Release this package.
> > [ ] +0 No opinion.
> > [ ] -1 Do not release this package because
> >
> >
> >
> >
> >
> > [1] https://github.com/apache/incubator-skywalking/blob/
> > master/docs/en/How-to-release.md
> > [2] https://github.com/apache/incubator-skywalking/blob/
> > master/docs/en/How-to-release.md#vote-check
> >
> >
> >
> >
> > --
> > Sheng Wu
> > Apache SkyWalking original creator and PPMC member
>
>
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2

[sebb]

On 22 March 2018 at 17:36, Robert Butts  wrote:
> Ah, thanks for the clarification.
>
> Ok, the 2.0.0 RPMs have been removed from dist

Huh? I still see files here:

https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/2.0.0-incubating/

Please remove the folder and its contents.

> , and the webpage links updated to archive.apache.org.

Agreed; thanks.


> On Mon, Mar 19, 2018 at 5:48 PM, sebb  wrote:
>
>> On 19 March 2018 at 19:01, Robert Butts  wrote:
>> > MD5s have been removed.
>> >
>> > Henk, I'm not sure what you mean about a 2.x branch. We don't have a
>> branch
>> > named 2.x. We do our primary development in master, then create branches
>> > for each release, e.g. 2.0.x, 2.1.x, 2.2.x. Those branches are only ever
>> > updated with backported fixes. There's no separate branch for version 2
>> > development, just master.
>> >
>> > Is that ok? Or do we still need to move 2.0.0?
>>
>> I think Henk meant that the mirrors should only hold the current release.
>> At present that is 2.1.0, so 2.0.0 should be removed, and the download
>> page updated to refer to the archive server at:
>> http://archive.apache.org/dist/incubator/trafficcontrol/2.0.0-incubating/
>>
>> When 2.2.0 is released, the same should be done for 2.1.0.
>> i.e. update the download page to add 2.2.0; change 2.1.0 and any
>> earlier links to use the archive server.
>> Once the new release has been announced, remove the older releases from
>>
>> https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/
>>
>> which will remove them from the ASF mirror system.
>>
>> >
>> > On Mon, Mar 19, 2018 at 11:57 AM, Henk P. Penning  wrote:
>> >
>> >> On Mon, 19 Mar 2018, Robert Butts wrote:
>> >>
>> >> Date: Mon, 19 Mar 2018 18:34:22 +0100
>> >>> From: Robert Butts 
>> >>> To: general@incubator.apache.org
>> >>> Cc: d...@trafficcontrol.incubator.apache.org
>> >>> Subject: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
>> >>>
>> >>> Hello Incubator PMC,
>> >>>
>> >>> The Apache Traffic Control community has voted on and approved a
>> >>> proposal to release Apache Traffic Control 2.2-incubating. We now
>> >>> kindly request that the Incubator PMC members review and vote on this
>> >>> incubator release.
>> >>>
>> >>
>> >> The previous approved releases and release notes (along with links to
>> >>> artifacts, signatures/checksums, and updated documentation) can be
>> >>> found here:
>> >>> http://trafficcontrol.incubator.apache.org/downloads/
>> >>>
>> >>
>> >>   Regarding you download page :
>> >>
>> >>   -- It appears you have only one development branch (2.x) going ;
>> >>  If so, 2.0.0 should not be in /dist/ (and on the mirrors) anymore.
>> >>  Please refer to 2.0.0 files as :
>> >>
>> >>  http://archive.apache.org/dist/incubator/trafficcontrol/2.
>> >> 0.0-incubating/
>> >>
>> >> The source distribution is here:
>> >>> https://dist.apache.org/repos/dist/dev/incubator/trafficcont
>> >>> rol/2.2.0/RC2/
>> >>>
>> >>
>> >>   Please don't publish .md5's anymore ; remove before moving 2.2.0
>> >>   from dist/dev/ to dist/release/.
>> >>
>> >>   Thanks ; regards,
>> >>
>> >>   Henk Penning
>> >>
>> >>    _
>> >> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
>> >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> >> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>> >>
>>

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

[VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1

[Mohammad Asif Siddiqui]

 Hi All,  
  
This is a call for vote to release Apache ServiceComb Java-Chassis (Incubating) 
version 1.0.0-m1  
  
Apache ServiceComb (Incubating) Community has voted and approved the release.  
  
Vote Thread : 
https://lists.apache.org/thread.html/b778a8787435b963c0743c518c3bc0b4c419a4010edc369f2c12c43c@%3Cdev.servicecomb.apache.org%3E
  
  
Result Thread : 
https://lists.apache.org/thread.html/81f6fd78e0577853c07e5a1924a9cf5a9c17aba5dd725d58fa397bea@%3Cdev.servicecomb.apache.org%3E
  
  
Release Notes : 
https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/etc/releaseNotes.md
  
  
Release Candidate : 
https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/
  
  
Staging Repo : 
https://repository.apache.org/content/repositories/orgapacheservicecomb-1196/  
  
Release Tag : 
https://github.com/apache/incubator-servicecomb-java-chassis/releases/tag/1.0.0-m1
 
  
Release CommitID : 901869b987c6f65c92b5b8b8f05eaf0f9f6e69cb  
  
Keys to verify the Release Candidate : 
https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS  
  
Voting will start now ( Friday, 23rd March, 2018) and will remain open for next 
72 hours, we request all IPMC members to give their vote.  
  
[ ] +1 Release this package as 1.0.0-m1  
[ ] +0 No Opinion  
[ ] -1 Do not release this package because  
  
Regards  
Asif  


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