Re: [Cava] Suitable name search - choosing a name

2019-03-18 Thread Antoine Toulme
All, the results are in, from VP Legal:
>I am happy to approve the name in isolation. Specifically, the community must 
>refrain from linking the project to any Star Wars references. The view of the 
>community is that the community is likely to find that difficult. It was 
>therefore agreed to look for a different name.

We need to pick another name.

> On Mar 4, 2019, at 2:32 PM, Dave Fisher  wrote:
> 
> Hi -
> 
>> On Mar 4, 2019, at 2:10 PM, Antoine Toulme  wrote:
>> 
>> 
>> 
>>> On Mar 4, 2019, at 2:00 PM, Dave Fisher  wrote:
>>> 
>>> Hi -
>>> 
>>> I went to look at the Trademark name search and something is either messed 
>>> up or autocorrected.
>>> 
>>> PODLINGNAMESEARCH-165 
>>> Establish 
>>> whether "Apache Obiwarn" is a Suitable Name
>>> 
>>> Isn’t the name supposed to be Obiwan and not Obiwarn?
>> No, the name is Obiwarn. With a r.
> 
> Well, my bad eye sight had my brain auto-correcting to what I expected to 
> see. Then Daniel wrote what he did.
> 
> OK. Let’s look into Obiwarn and deal with Apple autocorrecting it to Obiwan … 
> more Jedi mind tricks.
> 
> Regards,
> Dave
> 
>>> 
>>> Please look into it. Sorry, color me confused.
>>> 
>>> Regards,
>>> Dave
>>> 
 On Mar 4, 2019, at 12:20 PM, Jim Jagielski  wrote:
 
 Thx. We'll wait for the decision.
 
> On Mar 4, 2019, at 2:05 AM, Antoine Toulme  wrote:
> 
> The ticket is now open: 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165
> 
> Cheers,
> 
> Antoine
> 
>> On Mar 1, 2019, at 3:24 PM, Antoine Toulme  wrote:
>> 
>> Perfect, thank you.
>> 
>>> On Mar 1, 2019, at 3:17 PM, Daniel Shahaf  
>>> wrote:
>>> 
>>> Antoine Toulme wrote on Fri, Mar 01, 2019 at 15:09:39 -0800:
 I am happy to mention that you mentioned this term on list.
>>> 
>>> Thanks.
>>> 
 What language should I use?
>>> 
>>> The public part of PNS tickets should be factual, so I'd say:
>>> .
>>> "In the _Star Wars_ universe there exists a character named Obi-Wan 
>>> Kenobi"
>>> .
>>> with a link to Wikipedia for good measure.
>>> 
>>> Cheers,
>>> 
>>> Daniel
>>> 
> On Mar 1, 2019, at 3:06 PM, Daniel Shahaf  
> wrote:
> 
> Antoine Toulme wrote on Fri, Mar 01, 2019 at 09:10:08 -0800:
>> I’ll open a pooling name search ticket for Obiwarn and will test the 
>> waters over there.
> 
> When you create a PNS ticket, please note on it the existence of
> .
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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



[VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

2019-03-18 Thread Mick Semb Wever



After the latest discussion amongst this dev community on this dev mailing 
list[1],  presenting Sheng Wu as the PMC Chair and the maturity model[2], and 
then the discussion again on the incubator list[3],  a vote for Apache 
SkyWalking graduating to a top level project was called and has passed[4]. From 
the past incubator discussions the PPMC altered the draft graduation proposal, 
specifically the proposed PMC list: removing some inactive people and adding 
all the podling Committers. 


Apache SkyWalking entered the incubator on December of 2017.  SkyWalking has 
delivered 8 releases so far in total, and now shows a good cadence of 
successful releases.

During the podling's time in the Apache Incubator there has been
 3200+ commits on development of the project,
  378 Issues tagged as question in GitHub created, 373 resolved,
  850+ Pull request created and resolved,
  97 different contributors,
9 elected new committers, and
3 elected new PPMC members.

And the dev ML has had 72 participants: 
https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019

Attached is the draft Resolution for the PPMC and IPMC to vote upon.

Please take a minute to vote on whether or not Apache SkyWalking should
graduate to a Top Level Project by responding with one of the following:

[ ] +1 Apache SkyWalking should graduate.
[ ] +0 No opinion
[ ] -1 Apache SkyWalking should not graduate (please provide the reason)

The VOTE is open for a minimum of 72 hours. As there has been previous 
discussions on past versions of this proposal, I have not preluded the vote 
with a DISCUSS email. If feedback arises the vote period will be extended in 
good faith.

regards,
Mick


[1] 
https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
[2] 
https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
[3] 
https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
[4] 
https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E




Establish the Apache SkyWalking Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to application performance management and monitoring (APM).

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache SkyWalking Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache SkyWalking Project be and hereby is
responsible for the creation and maintenance of software related to
application performance management and monitoring (APM); and 
be it further

RESOLVED, that the office of "Vice President, Apache SkyWalking" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache
SkyWalking Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache SkyWalking
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache SkyWalking
Project:

  * Haoyang Liu  (刘浩杨)  
  * Hongtao Gao  (高洪涛)  
  * Ignasi Barrera  
  * Mick Semb Wever 
  * Sheng Wu  (吴晟)  
  * Shinn Zhang  (张鑫)   
  * Willem Ning Jiang  (姜宁)
  * Yongsheng Peng  (彭勇升)   
  * DongXue Si (司冬雪)
  * Jian Tan (谭建)   
  * Kai Wang (王凯)   
  * Yang Bai (柏杨)   
  * Yao Wang (王垚)   
  * Zhang Kewei (张科伟)  
 * Can Li (李璨)  
 * Jiaqi Lin (林嘉绮)  
 * Jinlin Fu (付金林)  
 * Lang Li (李浪)   
 * Wenbin Wang (王文斌)
 * Yixiong Cao (曹奕雄)



NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be 
appointed to the office of Vice President, Apache SkyWalking, to serve in 
accordance with and subject to the direction of the Board of Directors and 
the Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it further

RESOLVED, that the Apache SkyWalking Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
SkyWalking podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
SkyWalking 

[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

2019-03-18 Thread David Fisher (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795639#comment-16795639
 ] 

David Fisher commented on INCUBATOR-231:


I got access and I put the new clutch pages with an updated build into 
incubator-git master. After a few iterations everything is good.

I have a couple of loose ends to fix before I announce the update on general@.

There are actually three more sections to move to asciidoctor/jbake with or 
without gsp to read xml files.

# projects index and pages.
# ip-clearance index and pages.
# history page.

I'm still thinking through the approach, but I'm getting ahead.

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

2019-03-18 Thread David Fisher (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795642#comment-16795642
 ] 

David Fisher commented on INCUBATOR-231:


Try https://incubator.apache.org/clutch/

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



Re: Graduated from the Incubator but Releases remain in Incubator Dist SVN

2019-03-18 Thread William Guo
Hi Dave,

Thanks for the reminder, we have removed griffin release from incubator.

Thanks,
William

On Fri, Mar 15, 2019 at 2:01 AM Dave Fisher  wrote:

> Hi -
>
> You still have releases in the Incubator’s area of SVN -
> https://dist.apache.org/repos/dist/release/incubator/ <
> https://dist.apache.org/repos/dist/release/incubator/>
>
> Please plan to move or remove these soon.
>
> Thank you!
>
> Regards,
> Dave


[jira] [Created] (INCUBATOR-232) The Release of OpenWhisk 3.19.0-incubating: OpenWhisk Client JS

2019-03-18 Thread James Thomas (JIRA)
James Thomas created INCUBATOR-232:
--

 Summary: The Release of OpenWhisk 3.19.0-incubating: OpenWhisk 
Client JS
 Key: INCUBATOR-232
 URL: https://issues.apache.org/jira/browse/INCUBATOR-232
 Project: Incubator
  Issue Type: Task
Reporter: James Thomas


The OpenWhisk community is working on its first release 3.19.0-incubating of 
OpenWhisk Client JS under Apache. An email for VOTE will be sent to the dev 
mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache 
OpenWhisk 3.19.0-incubating-rc1: OpenWhisk Client JS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[RESULT] [VOTE] Release Apache Pony Mail (incubating) 0.11

2019-03-18 Thread Daniel Gruno

On 3/14/19 10:34 AM, Daniel Gruno wrote:

Hi folks,
This is a vote to release 0.11 of Apache Pony Mail (incubating).
The vote passed on dev@ponymail with 5x +1 and no 0s or -1s.
Three binding IPMC +1s carry over in this vote (humbedooh, johndament, 
jleroux).


Since there were no additional votes cast, the result remain the same; 
vote passed with 5x+1 (3 binding +1s). I'll start prepping for the 
release/announcement as soon as possible.




Artifacts are available at:
https://dist.apache.org/repos/dist/dev/incubator/ponymail/

Specifically, this is a vote on the source in 
https://dist.apache.org/repos/dist/dev/incubator/ponymail/apache-pony-mail-0.11-incubating.tar.gz 



SHA256 for the artifact is:
0939a90112b95f393b8ca8f73e51540cf22a1629e046468c84689bad55999bf7

git tag for the release is: 8b00e7c8eabf01a68fc119d2ce58bfbfc3c3eea3 
(tagged as 0.11-rc)


Please vote accordingly, the vote will last 72 hours, ending Sunday 17th 
of March at 10AM UTC:



[ ] +1; Full steam ahead
[ ]  0; Meh, I don't care
[ ] -1; Don't release because... [insert reason]


With regards,
Daniel.

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




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



[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

2019-03-18 Thread Bertrand Delacretaz (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794821#comment-16794821
 ] 

Bertrand Delacretaz commented on INCUBATOR-231:
---

If you need more Jenkins rights, a PMC chair needs to add you to 
https://whimsy.apache.org/roster/group/hudson-jobadmin - I canot do that myself.

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Comment Edited] (INCUBATOR-231) Cleanup Git-generated Incubator website

2019-03-18 Thread Bertrand Delacretaz (JIRA)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794821#comment-16794821
 ] 

Bertrand Delacretaz edited comment on INCUBATOR-231 at 3/18/19 8:08 AM:


If you need more Jenkins rights, a PMC chair needs to add you to 
https://whimsy.apache.org/roster/group/hudson-jobadmin - I cannot do that 
myself.


was (Author: bdelacretaz):
If you need more Jenkins rights, a PMC chair needs to add you to 
https://whimsy.apache.org/roster/group/hudson-jobadmin - I canot do that myself.

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[GitHub] [incubator] ottlinger merged pull request #9: Fix formatting

2019-03-18 Thread GitBox
ottlinger merged pull request #9: Fix formatting
URL: https://github.com/apache/incubator/pull/9
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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



Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 (release candidate 3)

2019-03-18 Thread Ovilia
Sorry about that.
I've pushed a commit [1] about it, and we will check the checklist more
carefully in the next release.
I will assume this can be fixed in next release unless you give a -1
explicitly. :)

Thanks!

[1]
https://github.com/apache/incubator-echarts/commit/6d53c516d72fae191ff32f3033d3eb81e0b4b99d

Zhang Wenli
http://zhangwenli.com


Justin Mclean  于2019年3月13日周三 下午2:54写道:

> Hi,
>
> > I checked the release checklist and regulations about NOTICE [1], and
> I'm still wondering what's wrong with the NOTICE file.
> > Is it related to third-party libraries?
>
> No that looks fine (but I’ve not checked in detail).  It quite trivial,
> but from last release vote thread:
> "- NOTICE needs year updating. Please fix for next release.”
>
> It’s one of the things to check in the check list.
>
> Thanks,
> Justin


[GitHub] [incubator] aajisaka opened a new pull request #9: Fix formatting

2019-03-18 Thread GitBox
aajisaka opened a new pull request #9: Fix formatting
URL: https://github.com/apache/incubator/pull/9
 
 
   The champion section is misformatted: 
https://incubator.apache.org/policy/roles_and_responsibilities.html#champion
   
   This patch added a newline to fix formatting.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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



Re: [VOTE] Accept DataSketches into the Apache Incubator

2019-03-18 Thread Mohammad Asif Siddiqui
+1 (binding) 
  
Regards  
Asif

On 2019/03/14 21:23:24, Kenneth Knowles  wrote: 
> Hi all,
> 
> We've discussed the proposal for the DataSketches project in [1] and [2].
> The
> proposal itself has been put on the wiki [3].
> 
> Per incubator rules [4] I'd like to call a vote to accept the new
> "DataSketches" project as a podling in the Apache Incubator.
> 
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
> 
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
> 
> [ ] +1 Accept DataSketches into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept DataSketches into the Apache Incubator because ...
> 
> Thanks to everyone who contributed to the proposal and discussions.
> 
> Kenn
> 
> [1]
> https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E
> [3] https://wiki.apache.org/incubator/DataSketchesProposal
> [4] https://incubator.apache.org/guides/proposal.html#the_vote
> 

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



Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 (releasecandidate 3)

2019-03-18 Thread ???? Sheng Wu
+1 binding


checked
1. incubating in name
2. asc checked
3. sha512 checked
4. compile passed
5. DISCLAIMER, LICENSE, NOTICE exist


One question, when I run 
> shasum -c apache-echarts-4.2.1-rc.3-incubating-src.zip.sha512
 Result is
> shasum: apache-echarts-4.2.1-rc.3-incubating-src.zip.sha512: no properly 
> formatted SHA1 checksum lines found
 

But when I do manually checking, it is literally matched. Do you create this 
sha512 file manually instead of using script? If so, could you consider to use 
command like this?
> shasum -a 512 ${PRODUCT_NAME}-src.tgz > ${PRODUCT_NAME}-src.tgz.sha512




--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "willem.jiang";
Date:  Sat, Mar 16, 2019 10:37 AM
To:  "general";

Subject:  Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 
(releasecandidate 3)



+1 (binding)

I checked
Verified the signature and sha512
DISCLAIMER
LICENSE
NOTICE
Can build the key from source.

Willem Jiang

Twitter: willemjiang
Weibo: willem

On Wed, Mar 6, 2019 at 2:58 PM SHUANG SU  wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.2.1 (release candidate 3).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/6f555bdb3bdc23ac9e260116738af779d4dff7b7e21f77c0a3369905@%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/54a63e2208330dd68c39bdcb5bd444301d0eb8580d433d1ac3fe4500@%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=1a2e990
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/RELEASE_NOTE.txt
>
> Some shell commands for validating the release:
>
> ```shell
> # Download the release:
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/apache-echarts-4.2.1-rc.3-incubating-src.zip
> -o apache-echarts-4.2.1-rc.3-incubating-src.zip
> unzip apache-echarts-4.2.1-rc.3-incubating-src.zip -d
> apache-echarts-4.2.1-rc.3-incubating-src > /dev/null
>
> # Rebuild the project (Node.js environment is required):
> cd "apache-echarts-4.2.1-rc.3-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --help`)
> ```
>
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.2.1 (release candidate 3)
> by "2019-03-09T07:42:38.040Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
>
> --
>  Su Shuang (100pah)
> --

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

[RESULT][VOTE] Release Apache Myriad 0.3.0 (incubating) [rc1]

2019-03-18 Thread Javi Roman
Hi everyone,

The vote for releasing Apache Myriad 0.3.0-RC1 (incubating) is closed,
now. And I’m happy to announce that we have unanimously approved this
release candidate (RC1) to be the Apache Myriad 0.3.0 release.

Vote result:
3 (+1 binding) (lresende, jmclean,  ningjiang)
0 (0 binding)
0 (-1 binding)

And no non-binding votes.

Thank you everyone for taking the time to review the release and help us.

--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

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