Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Dave Fisher]

Consider setting up a redirection of echarts.baidu.com to echarts.apache.org or 
equivalent.

Either way let’s have s a discussion on the ECharts dev list.

Thanks to Justin for pointing this out.

Regards,
Dave

Sent from my iPhone

> On Aug 18, 2020, at 10:20 PM, Ovilia  wrote:
> 
> Hi,
> 
> How should we get the approval of this exception?
> 
> Because the domain echarts.baidu.com has many users who might have saved the
> link in their bookmarks or being linked elsewhere, it may not be wise to
> ban it for
> all. We still have thousands of visitors to that domain everyday.
> 
> Thanks
> 
> *Ovilia*
> 
> 
>> On Wed, Aug 19, 2020 at 1:09 PM Justin Mclean 
>> wrote:
>> 
>> Hi,
>> 
>>> But unfortunately we missed the theme builder page.
>>> All other pages (like https://echarts.baidu.com/option.html ) have been
>>> fixed.
>>> We will solve the theme builder page soon and double check other pages.
>> 
>> IMO the domain echarts.baidu.com probably should not exist as it implies
>> ownership of the project by a company [1] and is not in line with ASF
>> branding policy on domain names. There have been exceptions to this policy
>> but I don’t recall eCharts getting one. Is this the case?
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://www.apache.org/foundation/marks/domains.html#introduction
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

Thanks Justin.

I've updated the medium post and npm description.

But it seems the npm description is cached so the Website is not updated
now.
It takes the README file from GitHub so you may check that file [1]  on
GitHub
to know the npm description without cache.

[1] https://github.com/apache/incubator-echarts#apache-echarts-incubating

Thanks

*Ovilia*


On Wed, Aug 19, 2020 at 1:16 PM Justin Mclean 
wrote:

> Hi,
>
> From a quick search there also seem to be a few branding issues to sort
> out.
>
> For instance this page which I think you recently wrote? [1] There's not a
> single mention there that it’s an Apache project, although it does link to
> echarts.apache.org.
>
> It would be nice if this page [2] was updated to bring in more in line
> with banding policy.
>
> In general it should be called “Apache ECharts” not just “ECharts".
>
> Thanks,
> Justin
>
> 1.
> https://medium.com/@Ovilia/making-a-covid-19-map-with-echarts-and-leaflet-30fdcd8739c6
> 2. https://www.npmjs.com/package/echarts
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

Hi,

How should we get the approval of this exception?

Because the domain echarts.baidu.com has many users who might have saved the
link in their bookmarks or being linked elsewhere, it may not be wise to
ban it for
all. We still have thousands of visitors to that domain everyday.

Thanks

*Ovilia*


On Wed, Aug 19, 2020 at 1:09 PM Justin Mclean 
wrote:

> Hi,
>
> > But unfortunately we missed the theme builder page.
> > All other pages (like https://echarts.baidu.com/option.html ) have been
> > fixed.
> > We will solve the theme builder page soon and double check other pages.
>
> IMO the domain echarts.baidu.com probably should not exist as it implies
> ownership of the project by a company [1] and is not in line with ASF
> branding policy on domain names. There have been exceptions to this policy
> but I don’t recall eCharts getting one. Is this the case?
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/foundation/marks/domains.html#introduction
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Justin Mclean]

Hi,

From a quick search there also seem to be a few branding issues to sort out.

For instance this page which I think you recently wrote? [1] There's not a 
single mention there that it’s an Apache project, although it does link to 
echarts.apache.org.

It would be nice if this page [2] was updated to bring in more in line with 
banding policy.

In general it should be called “Apache ECharts” not just “ECharts".

Thanks,
Justin

1. 
https://medium.com/@Ovilia/making-a-covid-19-map-with-echarts-and-leaflet-30fdcd8739c6
2. https://www.npmjs.com/package/echarts
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Justin Mclean]

Hi,

> But unfortunately we missed the theme builder page.
> All other pages (like https://echarts.baidu.com/option.html ) have been
> fixed.
> We will solve the theme builder page soon and double check other pages.

IMO the domain echarts.baidu.com probably should not exist as it implies 
ownership of the project by a company [1] and is not in line with ASF branding 
policy on domain names. There have been exceptions to this policy but I don’t 
recall eCharts getting one. Is this the case?

Thanks,
Justin

1. https://www.apache.org/foundation/marks/domains.html#introduction
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

Hi Justin,

The domain name has been solved.

But unfortunately we missed the theme builder page.
All other pages (like https://echarts.baidu.com/option.html ) have been
fixed.
We will solve the theme builder page soon and double check other pages.

Thanks

*Ovilia*


On Wed, Aug 19, 2020 at 12:46 PM Justin Mclean 
wrote:

> Hi,
>
> Has the issue with the multiple domain names been resolved? e.g
> https://echarts.baidu.com/theme-builder/en/index.html
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Justin Mclean]

Hi,

Has the issue with the multiple domain names been resolved? e.g 
https://echarts.baidu.com/theme-builder/en/index.html

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

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Ming Wen]

Hi, guo jiwei,
This is not the incubator vote thread.
you should support them in d...@echarts.apache.org.

Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing


guo jiwei  于2020年8月19日周三 下午12:39写道：

> +1 (non-binding)
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Wed, Aug 19, 2020 at 12:33 PM Ovilia  wrote:
>
> > FYI.
> > Apache ECharts (incubating) is running a community graduation vote now.
> >
> > Thanks
> >
> > *Ovilia*
> >
> > Forwarded Conversation
> > Subject: [VOTE] Graduate Apache ECharts (incubating) as a top level
> project
> > 
> >
> > From: Ovilia 
> > Date: Mon, Aug 17, 2020 at 11:36 AM
> > To: dev 
> >
> >
> > Hi all,
> >
> > Hello all,
> > After our discussion about readiness for graduation to TLP on the dev
> > mailing list [8], I would like to call a VOTE for Apache ECharts
> graduating
> > as a top level project.
> >
> > If this vote passes, the next step would be to submit the resolution
> below
> > to the Incubator PMC, who would vote on sending it on to the Apache
> Board.
> >
> > Vote:
> > [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> > [ ]  0 - I don't feel strongly about it, but don't object
> > [ ] -1 - Do not recommend graduation of Apache ECharts because...
> >
> > The VOTE will open for at least 72 hours.
> >
> > -
> >
> > X. Establish the Apache ECharts 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 a charting and data visualization
> > library written in JavaScript.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache ECharts Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache ECharts Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a charting and data visualization
> > library written in JavaScript; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache ECharts" 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 ECharts Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache ECharts 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 ECharts Project:
> >
> > * Houjin Huang  
> > * Deqing Li 
> > * Dong Rui  
> > * Kener Linfeng 
> > * Kevin A. McGrail  
> > * Wenli Zhang   
> > * Shen Yi   
> > * Shuang Su 
> > * Siwen Su  
> > * Junting Wang  
> > * Zhongxiang Wang   
> > * Dave Fisher   
> > * Sheng Wu  
> > * Zak Wu
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> > be appointed to the office of Vice President, Apache ECharts, to
> > serve in accordance with and subject to the direction of the
> > Board of Directors and the Bylaws of the Foundation until
> > death, resignation, retirement, removal or disqualification,
> > or until a successor is appointed; and be it further
> >
> > RESOLVED, that the initial Apache ECharts PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache ECharts Project; and be it further
> >
> > RESOLVED, that the Apache ECharts Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator ECharts podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator ECharts podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
> >
> >
> > -
> >
> > More information:
> >
> > - Assessment of the maturity model is available at [5].
> > - A checklist of graduation is available at [6].
> > - 3 new PPMCs and 6 new committers were elected and joined the community
> > [1]
> > since incubation and now we have committers working for more than 6
> > different
> > companies.
> > - Our mailing list [2] is very active and we have 81 people subscribed to
> > it.
> > - Released 8 versions by 3 release managers [3] (and another version by
> > another release manager is under voting stage); release guide is at [4].
> > - 73 people have contributed to the project during incubation [10].
> > - Branding issues have been solved and name searching has been completed
> > [7].
> > - Website [9] 

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[guo jiwei]

+1 (non-binding)

Regards
Jiwei Guo (Tboy)


On Wed, Aug 19, 2020 at 12:33 PM Ovilia  wrote:

> FYI.
> Apache ECharts (incubating) is running a community graduation vote now.
>
> Thanks
>
> *Ovilia*
>
> Forwarded Conversation
> Subject: [VOTE] Graduate Apache ECharts (incubating) as a top level project
> 
>
> From: Ovilia 
> Date: Mon, Aug 17, 2020 at 11:36 AM
> To: dev 
>
>
> Hi all,
>
> Hello all,
> After our discussion about readiness for graduation to TLP on the dev
> mailing list [8], I would like to call a VOTE for Apache ECharts graduating
> as a top level project.
>
> If this vote passes, the next step would be to submit the resolution below
> to the Incubator PMC, who would vote on sending it on to the Apache Board.
>
> Vote:
> [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> [ ]  0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache ECharts because...
>
> The VOTE will open for at least 72 hours.
>
> -
>
> X. Establish the Apache ECharts 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 a charting and data visualization
> library written in JavaScript.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache ECharts Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache ECharts Project be and hereby is
> responsible for the creation and maintenance of software
> related to a charting and data visualization
> library written in JavaScript; and be it further
>
> RESOLVED, that the office of "Vice President, Apache ECharts" 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 ECharts Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache ECharts 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 ECharts Project:
>
> * Houjin Huang  
> * Deqing Li 
> * Dong Rui  
> * Kener Linfeng 
> * Kevin A. McGrail  
> * Wenli Zhang   
> * Shen Yi   
> * Shuang Su 
> * Siwen Su  
> * Junting Wang  
> * Zhongxiang Wang   
> * Dave Fisher   
> * Sheng Wu  
> * Zak Wu
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> be appointed to the office of Vice President, Apache ECharts, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache ECharts PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache ECharts Project; and be it further
>
> RESOLVED, that the Apache ECharts Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator ECharts podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator ECharts podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
> -
>
> More information:
>
> - Assessment of the maturity model is available at [5].
> - A checklist of graduation is available at [6].
> - 3 new PPMCs and 6 new committers were elected and joined the community
> [1]
> since incubation and now we have committers working for more than 6
> different
> companies.
> - Our mailing list [2] is very active and we have 81 people subscribed to
> it.
> - Released 8 versions by 3 release managers [3] (and another version by
> another release manager is under voting stage); release guide is at [4].
> - 73 people have contributed to the project during incubation [10].
> - Branding issues have been solved and name searching has been completed
> [7].
> - Website [9] has been updated to meet up with Apache regulations.
>
> -
>
>
> [1] https://echarts.apache.org/en/committers.html
> [2] https://lists.apache.org/list.html?d...@echarts.apache.org
> [3] https://dist.apache.org/repos/dist/release/incubator/echarts/
> [4]
>
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
> [5]
>
> 

Fwd: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

FYI.
Apache ECharts (incubating) is running a community graduation vote now.

Thanks

*Ovilia*

Forwarded Conversation
Subject: [VOTE] Graduate Apache ECharts (incubating) as a top level project


From: Ovilia 
Date: Mon, Aug 17, 2020 at 11:36 AM
To: dev 


Hi all,

Hello all,
After our discussion about readiness for graduation to TLP on the dev
mailing list [8], I would like to call a VOTE for Apache ECharts graduating
as a top level project.

If this vote passes, the next step would be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the Apache Board.

Vote:
[ ] +1 - Recommend graduation of Apache ECharts as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache ECharts because...

The VOTE will open for at least 72 hours.

-

X. Establish the Apache ECharts 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 a charting and data visualization
library written in JavaScript.

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

RESOLVED, that the Apache ECharts Project be and hereby is
responsible for the creation and maintenance of software
related to a charting and data visualization
library written in JavaScript; and be it further

RESOLVED, that the office of "Vice President, Apache ECharts" 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 ECharts Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache ECharts 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 ECharts Project:

* Houjin Huang  
* Deqing Li 
* Dong Rui  
* Kener Linfeng 
* Kevin A. McGrail  
* Wenli Zhang   
* Shen Yi   
* Shuang Su 
* Siwen Su  
* Junting Wang  
* Zhongxiang Wang   
* Dave Fisher   
* Sheng Wu  
* Zak Wu

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

RESOLVED, that the initial Apache ECharts PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache ECharts Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator ECharts podling encumbered upon the Apache Incubator
Project are hereafter discharged.


-

More information:

- Assessment of the maturity model is available at [5].
- A checklist of graduation is available at [6].
- 3 new PPMCs and 6 new committers were elected and joined the community [1]
since incubation and now we have committers working for more than 6
different
companies.
- Our mailing list [2] is very active and we have 81 people subscribed to
it.
- Released 8 versions by 3 release managers [3] (and another version by
another release manager is under voting stage); release guide is at [4].
- 73 people have contributed to the project during incubation [10].
- Branding issues have been solved and name searching has been completed
[7].
- Website [9] has been updated to meet up with Apache regulations.

-


[1] https://echarts.apache.org/en/committers.html
[2] https://lists.apache.org/list.html?d...@echarts.apache.org
[3] https://dist.apache.org/repos/dist/release/incubator/echarts/
[4]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
[5]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
[6]
https://cwiki.apache.org/confluence/display/ECHARTS/ECharts+Graduation+Check+List
[7] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
[8]
https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
[9] http://echarts.apache.org/
[10] 

Re: Challenges using Gitbox

[Dave Fisher]

The correct list is either here. 

(1) Have a look at the Incubator website and we can discuss a patch to our 
guidance. 

Or

(2) d...@community.apache.org

Like Ted I gained my first committership by answering user questions in a 
project. IPMC membership by migrating websites, Infra for a podling. Apache 
Membership by mentoring.

When I started with Apache I was managing a developer who was working at my 
direction. They got status well before me.

One can certainly vote on releases without coding. Being able to evaluate and 
vote on releases is something every PMC needs.

Regards,
Dave

Sent from my iPhone

> On Aug 18, 2020, at 8:04 PM, Maxime Beauchemin  
> wrote:
> 
> How can I propose this as a change? What's the proper forum / mailing list?
> 
>> On Tue, Apr 17, 2018, 9:49 AM Ted Dunning  wrote:
>> 
>> On Mon, Apr 16, 2018 at 8:28 PM, Ralph Goers 
>> wrote:
>> 
>>> ...
> such people can earn merit by becoming involved with the community and
 helping out where they can.
 
 In theory, that sounds good, but as a practical matter, how many people
 that have ever been on the ASF board of directors neither know/knew,
>> nor
 use(d) any programming languages in getting there? IOW, they got there
 exclusively on their ability to write documentation, do community
 relations, or utilize other non-coding skills?
>>> 
>>> It has happened many times. When I was a committer on Apache Cocoon we
>>> voted Arje Cahn as a committer for his contributions to the project which
>>> had nothing to do with coding. He was voted in as an ASF member for
>> pretty
>>> much the same reason.
>>> 
>> 
>> 
>> It has happened. I was voted as a committer for simply answering questions
>> (and it stuck). I know of at least one or two others.
>> 
>> But we should be honest here. It isn't all that common. It should be much
>> more common.
>> 


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

Re: Challenges using Gitbox

[Maxime Beauchemin]

How can I propose this as a change? What's the proper forum / mailing list?

On Tue, Apr 17, 2018, 9:49 AM Ted Dunning  wrote:

> On Mon, Apr 16, 2018 at 8:28 PM, Ralph Goers 
> wrote:
>
> > ...
> > >> such people can earn merit by becoming involved with the community and
> > > helping out where they can.
> > >
> > > In theory, that sounds good, but as a practical matter, how many people
> > > that have ever been on the ASF board of directors neither know/knew,
> nor
> > > use(d) any programming languages in getting there? IOW, they got there
> > > exclusively on their ability to write documentation, do community
> > > relations, or utilize other non-coding skills?
> >
> > It has happened many times. When I was a committer on Apache Cocoon we
> > voted Arje Cahn as a committer for his contributions to the project which
> > had nothing to do with coding. He was voted in as an ASF member for
> pretty
> > much the same reason.
> >
>
>
> It has happened. I was voted as a committer for simply answering questions
> (and it stuck). I know of at least one or two others.
>
> But we should be honest here. It isn't all that common. It should be much
> more common.
>

Re: [VOTE] Release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0 (ROUND3)

[JUN GAO]

Hi Furkan KAMACI , Thank you for your vote.

Furkan KAMACI 于2020年8月19日 周三03:07写道：

> Hi,
>
> +1 from me (binding, carrying over my vote).
>
> I checked:
>
> - Incubating in name
> - DISCLAIMER exists
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - Checked PGP signatures
> - Checked checksums
> - Code compiles and tests successfully run
> - Apache rat checks are OK
>
> Kind Regards,
> Furkan KAMACI
>
> On Tue, Aug 18, 2020 at 1:47 PM JUN GAO  wrote:
>
> > Hello everyone, because the Maven 2 staging repository is deleted by
> > mistake. So I Redeployed it, The latest maven 2 staging repository
> address
> > is :
> >
> >
> >
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1045/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> > <
> >
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1045/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> > >
> >
> > And we still need 2 binging votes on this release. I eagerly hope that
> > someone can vote for us.
> >
> >
> > Thank you very much !
> >
> > > 2020年8月14日 下午9:59，JUN GAO  写道：
> > >
> > > Hello IPMC , We still need 2 binding votes on this release. Can anyone
> > help vote?
> > >
> > > Thank you very much!
> > >
> > > GAO JUN mailto:gaojun2...@gmail.com
> >>于2020年8月13日
> > 周四12:07写道：
> > > Hello IPMC and DolphinScheduler Community,
> > >
> > >
> > >
> > > This is a call for a vote to release Apache DolphinScheduler Maven
> > Plugin (Incubating) version 1.0.0.
> > >
> > >
> > >
> > > The Apache DolphinScheduler community has voted on and approved a
> > proposal to release Apache DolphinScheduler Maven Plugin (Incubating)
> 1.0.0
> > >
> > >
> > >
> > > We now kindly request the Incubator IPMC members review and vote on
> this
> > incubator release.
> > >
> > >
> > >
> > > Dolphin Scheduler is a distributed and easy-to-expand visual DAG
> > workflow scheduling system, dedicated to solving the complex dependencies
> > in data processing, making the scheduling system out of the box for data
> > processing.
> > >
> > >
> > >
> > > DolphinScheduler community vote and result threads:
> > >
> > >
> >
> https://lists.apache.org/thread.html/re4d26427e71440ab4dd2cb97d10c4f500e15ea5534836ff0fa54bd78%40%3Cdev.dolphinscheduler.apache.org%3E
> > <
> >
> https://lists.apache.org/thread.html/re4d26427e71440ab4dd2cb97d10c4f500e15ea5534836ff0fa54bd78%40%3Cdev.dolphinscheduler.apache.org%3E
> > >
> > >
> > >
> > >
> >
> https://lists.apache.org/thread.html/r82b2fe70fdf64842a9167e5798a79d00eef70ddcb99e4db0f0d66a09%40%3Cdev.dolphinscheduler.apache.org%3E
> > <
> >
> https://lists.apache.org/thread.html/r82b2fe70fdf64842a9167e5798a79d00eef70ddcb99e4db0f0d66a09%40%3Cdev.dolphinscheduler.apache.org%3E
> > >
> > >
> > >
> > > The release candidates:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> > <
> >
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> > >
> > >
> > >
> > > Maven 2 staging repository:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1039/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> > <
> >
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1039/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> > >
> > >
> > >
> > > Git tag for the release:
> > >
> > >
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0
> > <
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0
> > >
> > >
> > >
> > > Release Commit ID:
> > >
> > >
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/10280f9d52ad5cfaf1256fcf5a7955be23d464c5
> > <
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/10280f9d52ad5cfaf1256fcf5a7955be23d464c5
> > >
> > >
> > >
> > > Keys to verify the Release Candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS
> <
> > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS>
> > >
> > >
> > > Look at here for how to verify this release candidate:
> > >
> > >
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md
> > <
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md
> > >
> > >
> > >
> > > The vote will be open for at least 72 hours or until a necessary number
> > of
> > >
> > > votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > >
> > >
> > > [ ] +1 approveg
> > >
> > >
> > >
> > > [ ] +0 no opinion
> > >
> > >
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > >
> > >
> > > Checklist for reference:
> > >
> > >
> > >
> > > [ ] Download links are valid.
> > >
> > >
> > >
> > > [ ] Checksums and PGP signatures are valid.
> > >
> > >
> > >
> > > [ ] 

Re: [VOTE] Release Apache IoTDB 0.10.1

[Willem Jiang]

+1 （binding）

I just have a quick question about the README files. Why do we put
them into the release directory?

I checked：
Verified the signed the key and hash code.
 Incubating in the release kit name.
License and Notice files  are good to me.
The maven staging repo looks good.
Git repo release tag.
There is no binary in the source kit.
I can build the kit from source.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 14, 2020 at 9:59 AM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.1, which is a bug-fix version of 0.10.0.
>
> The Apache IoTDB community has voted on and approved a proposal to
> release Apache
> IoTDB (Incubating) version 0.10.1 (with 12 +1 votes).
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator
> release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data.
>
> IoTDB community vote and result thread:
>
> Result:
>
> https://lists.apache.org/thread.html/r3d2081bac4aed5217820a4587383150dc7b6471828675d9b6eeacf5e%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
> https://lists.apache.org/thread.html/r94e5dcac19d5f2ba9990a95cc1fb5232074702de9f1c326d27eebfe3%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.1
>
> Hash for the release tag:
> 023fb84e0b76c0ac64b7a9ac098c640f26795a25
>
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key: 2206EF8F64C35889, which can be found
> in the keys file:
>
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> The vote will be passed if there are at least 3 IPMC +1 votes and there is
> no -1 vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)

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

Re: [VOTE] Release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0 (ROUND3)

[Furkan KAMACI]

Hi,

+1 from me (binding, carrying over my vote).

I checked:

- Incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked checksums
- Code compiles and tests successfully run
- Apache rat checks are OK

Kind Regards,
Furkan KAMACI

On Tue, Aug 18, 2020 at 1:47 PM JUN GAO  wrote:

> Hello everyone, because the Maven 2 staging repository is deleted by
> mistake. So I Redeployed it, The latest maven 2 staging repository address
> is :
>
>
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1045/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> <
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1045/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> >
>
> And we still need 2 binging votes on this release. I eagerly hope that
> someone can vote for us.
>
>
> Thank you very much !
>
> > 2020年8月14日 下午9:59，JUN GAO  写道：
> >
> > Hello IPMC , We still need 2 binding votes on this release. Can anyone
> help vote?
> >
> > Thank you very much!
> >
> > GAO JUN mailto:gaojun2...@gmail.com>>于2020年8月13日
> 周四12:07写道：
> > Hello IPMC and DolphinScheduler Community,
> >
> >
> >
> > This is a call for a vote to release Apache DolphinScheduler Maven
> Plugin (Incubating) version 1.0.0.
> >
> >
> >
> > The Apache DolphinScheduler community has voted on and approved a
> proposal to release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0
> >
> >
> >
> > We now kindly request the Incubator IPMC members review and vote on this
> incubator release.
> >
> >
> >
> > Dolphin Scheduler is a distributed and easy-to-expand visual DAG
> workflow scheduling system, dedicated to solving the complex dependencies
> in data processing, making the scheduling system out of the box for data
> processing.
> >
> >
> >
> > DolphinScheduler community vote and result threads:
> >
> >
> https://lists.apache.org/thread.html/re4d26427e71440ab4dd2cb97d10c4f500e15ea5534836ff0fa54bd78%40%3Cdev.dolphinscheduler.apache.org%3E
> <
> https://lists.apache.org/thread.html/re4d26427e71440ab4dd2cb97d10c4f500e15ea5534836ff0fa54bd78%40%3Cdev.dolphinscheduler.apache.org%3E
> >
> >
> >
> >
> https://lists.apache.org/thread.html/r82b2fe70fdf64842a9167e5798a79d00eef70ddcb99e4db0f0d66a09%40%3Cdev.dolphinscheduler.apache.org%3E
> <
> https://lists.apache.org/thread.html/r82b2fe70fdf64842a9167e5798a79d00eef70ddcb99e4db0f0d66a09%40%3Cdev.dolphinscheduler.apache.org%3E
> >
> >
> >
> > The release candidates:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> <
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> >
> >
> >
> > Maven 2 staging repository:
> >
> >
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1039/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> <
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1039/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> >
> >
> >
> > Git tag for the release:
> >
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0
> <
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0
> >
> >
> >
> > Release Commit ID:
> >
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/10280f9d52ad5cfaf1256fcf5a7955be23d464c5
> <
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/10280f9d52ad5cfaf1256fcf5a7955be23d464c5
> >
> >
> >
> > Keys to verify the Release Candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS>
> >
> >
> > Look at here for how to verify this release candidate:
> >
> >
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md
> <
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md
> >
> >
> >
> > The vote will be open for at least 72 hours or until a necessary number
> of
> >
> > votes are reached.
> >
> > Please vote accordingly:
> >
> >
> >
> > [ ] +1 approveg
> >
> >
> >
> > [ ] +0 no opinion
> >
> >
> >
> > [ ] -1 disapprove with the reason
> >
> >
> >
> > Checklist for reference:
> >
> >
> >
> > [ ] Download links are valid.
> >
> >
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> >
> >
> > [ ] Source code artifacts have correct names matching the current
> release.
> >
> >
> >
> > [ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
> >
> >
> >
> > [ ] All files have license headers if necessary.
> >
> >
> >
> > [ ] No compiled archives bundled in source archive.
> >
> >
> >
> > More detail checklist please refer:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> <
> 

Re: [VOTE] Release Apache ECharts (incubating) 4.9.0 (release candidate 1)

[Dave Fisher]

+1 (binding)

Incubating in name
Verified signature and checksum
LICENSE checked
NOTICE checked
DISCLAIMER checked
Rat Check passed

Regards,
Dave

> On Aug 9, 2020, at 8:57 PM, Yi Shen  wrote:
> 
> Dear IPMC
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.9.0 (release candidate 1).
> 
> Apache ECharts community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/r67639d86c9b5944b1804fca86939052978df9594b45bc0d6474b9fb6%40%3Cdev.echarts.apache.org%3E
> 
> Results thread:
> https://lists.apache.org/thread.html/rd9b5170f1f1bdda97c502aa4435650f86ec2ce14cd372ed3d548ce24%40%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.9.0-rc.1/
> 
> 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=90243fc
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.9.0-rc.1/RELEASE_NOTE.txt
> 
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/4.9.0-rc.1/README.md#build
> 
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.9.0 (release candidate 1)
> by "2020-08-13T05:00:00.000Z".
> 
> [ ] +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.
> 
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> Thanks
> 
> -- 
> Yi Shen
> Apache ECharts(incubating) PPMC


-
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.9.0 (release candidate 1)

[Yi Shen]

Hi IPMC,

Please help us vote for the release. We still need 3 binding votes.

Many thanks!

On Fri, Aug 14, 2020 at 10:52 AM Yi Shen  wrote:

> We still need 3 binding votes on this release. Can anyone help vote?
>
> Thanks!
>
> On Mon, Aug 10, 2020 at 11:57 AM Yi Shen  wrote:
>
>> Dear IPMC
>>
>> I am pleased to be calling this vote for the release of Apache ECharts
>> (incubating) 4.9.0 (release candidate 1).
>>
>> Apache ECharts community has voted and approved the release.
>>
>> Vote thread:
>>
>> https://lists.apache.org/thread.html/r67639d86c9b5944b1804fca86939052978df9594b45bc0d6474b9fb6%40%3Cdev.echarts.apache.org%3E
>>
>> Results thread:
>>
>> https://lists.apache.org/thread.html/rd9b5170f1f1bdda97c502aa4435650f86ec2ce14cd372ed3d548ce24%40%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.9.0-rc.1/
>>
>> 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=90243fc
>>
>> The Release Note is available in:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.9.0-rc.1/RELEASE_NOTE.txt
>>
>> Build Guide:
>>
>> https://github.com/apache/incubator-echarts/blob/4.9.0-rc.1/README.md#build
>>
>> Please vote on releasing this package as:
>> Apache ECharts (incubating) 4.9.0 (release candidate 1)
>> by "2020-08-13T05:00:00.000Z".
>>
>> [ ] +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.
>>
>> A checklist for reference:
>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>>
>> Thanks
>>
>> --
>> Yi Shen
>> Apache ECharts(incubating) PPMC
>>
>
>
> --
> Yi Shen
> Apache ECharts(incubating) PPMC
>


-- 
Yi Shen
Apache ECharts(incubating) PPMC

Re: Giving our PMs and contributors triage rights on GitHub

[Matt Sicker]

For what it's worth, new contributors to Ubuntu typically start by doing
bug triaging, though that’s using Launchpad which is sort of designed
around that idea.

On Mon, Aug 17, 2020 at 19:50 Maxime Beauchemin 
wrote:

> Thank you for the comments Julian and Jarek.
>
>
>
> A few related thoughts:
>
>
>
> - the "triage" GitHub role is very limited (labeling, open/closing, assign,
>
> kanban)
>
> <
> https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
> >and
>
> I don't think it can be abused. Ideally it should be easy for us to give
>
> this role to contributors that are not-yet-committers that want to help
>
> with labeling, flagging duplicates, ... Can someone think of any way that
>
> this can be abused? Rogue-labeling? Bulk-closing/opening issues?
>
> - PMs (project, product and program managers) have aligned interests with
>
> contributors towards the success of the project, I don't think of them as
>
> "business people". In our community, they've been the connective tissue
>
> between individuals and across organizations, facilitating collaboration
>
> across boundaries and at scale. They do so much that's invisible to the
>
> ASF's traditional way of thinking, like interviewing users, doing
>
> competitive research, running surveys, analyzing issues, bridging with
>
> designers, ...
>
> - the chicken & egg problem is a thing where it absolutely makes sense for
>
> PMs to build context while triaging. Currently they can comment but they
>
> cannot label, reopen, pin issues, manage milestones, which means it's hard
>
> to add value while ramping up
>
> - voting them in as committers is time consuming, error-prone and slow
>
>
>
> I think it's pretty clear that to build a great project and community, it
>
> takes much more than just software engineers, especially for projects
>
> "up-the-stack"! It takes all sorts of people with diverse skills and roles
>
> to make a project like Superset successful. Diversity is key, and being
>
> welcoming and inclusive to different types of contribution is super
>
> important.
>
>
>
> Last thought: I don't have data on this, but I think the ASF could be doing
>
> better at diversity (see the ApacheCon picture  >
>
> as anecdotal evidence). Being inclusive of a wider range of roles and
>
> offering diverse paths to "committerhood" could really help with this. For
>
> Superset and many other projects, finding ways to involve and empower PMs
>
> and designers to partake in the open source process is vital.
>
>
>
> Max
>
>
>
> On Fri, Aug 14, 2020 at 5:17 AM Jarek Potiuk  wrote:
>
>
>
> > Few comments, needs of the Apache Airflow project.
>
> >
>
> > In short: big +1 on enabling the "triage role".
>
> >
>
> > On 2020/08/13 18:43:06, Julian Hyde  wrote:
>
> > > By PM, I presume that you mean either Product Manager or Program
>
> > Manager. I’ve worked at a few companies that practiced “commercial open
>
> > source”, and there is inherent tension in the relationship with the
>
> > “business” people.
>
> >
>
> > I read that as Project Manager as well. I think when there are many
> issues
>
> > in a project, it is often useful that the teams working on a project also
>
> > have a Project Manager that helps the team to remove obstacles (this is,
> I
>
> > think the main role of great Project Manager). This is the case, where
>
> > several companies have whole teams dedicated to improve the OSS project.
>
> > The developers still act as sole contributors on the OSS project, but
> they
>
> > are paid by another organisation to do so and the Project Manager is
> there
>
> > to make sure the teams work well together as well as individuals. We have
>
> > some great example of that in our company where we have teams of
>
> > contributors (also committers and PMCs) working on Apache Airflow and
>
> > Apache Beam projects (among others) and there are PMs for those projects.
>
> > What's more - those PMs are not there to provide "Business direction" but
>
> > to make people working "well" together and there are some good example of
>
> > people like that who learned how to do it in the
>
> >  open-source cases. Quite recently at the Airflow Summit, our PM Karolina
>
> > - gave (together with our CTO) great talk about it and explained the
>
> > challenges and benefits of having a PM in such team:
>
> >
> https://www.youtube.com/watch?v=KIEMEYM2PEs=PLGudixcDaxY3RGLSlWoN_cEEXhIT1OPmj=37
>
> > . I can heartily recommend the talk to everyone who is interested in the
>
> > subject!
>
> >
>
> > What's more - if you have great PMs who are really part of the team, they
>
> > are super happy to contribute to the whole OSS project - and being able
> to
>
> > help with the teamwork (for example by organixing issues and helping with
>
> > tracking the progress) might be a huge help for both - the teams and the
>
> > project. I think we are really 

Re: [VOTE] Release Apache IoTDB 0.10.1

[Xiangdong Huang]

Hi,

@Chris, thanks for your detailed checking and continuous help to IoTDB.
We will fix all the issues you mentioned in the next release version.

We look forward to more votes from IPMCs for this release. :D.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Christofer Dutz  于2020年8月18日周二 下午2:32写道：

> Hi all,
>
> TL/DR:
> +1 binding
>
> Longer version:
> I started evaluating. As usual the IoTDB release candidate is in very good
> shape.
>
> Here some super minor things I noticed:
>
> - It seems the ".plan" templates in
> server/src/assembly/resources/tools/logVisualize/plans support comments,
> then they should contain the Apache headers.
> - The karaf feature is referencing a SNAPSHOT version and not even the
> version in this release 0.10.0.SNAPSHOT
> - The Dockerfile is also referencing an older SNAPSHOT version
> 0.10.0-SNAPSHOT
> - The mvnw.sh file doesn't seem to be executable
> - In the README perhaps point out that you can a) download the source
> bundle from one of the mirrors or you can clone from gitbox or github ...
> what you're describing in the README is actually not downloading, but
> cloning the repo. I would probably base the documentation on downloading a
> release archive and put the cloning in the developer part of the
> documentation. Reason is: Only for the source-bundles can we really ensure
> this is what was voted on ... tags in Github can be changed.
>
> [OK] Download all staged artifacts under the url specified in the release
> vote email into a directory we’ll now call download-dir.
> [OK] Verify the signature is correct: Additional Apache tutorial on how to
> verify downloads can be found here.
> [OK] Check if the signature references an Apache email address.
> [OK] Verify the SHA512 hashes:
> [OK] Unzip the archive:
> [OK] Verify the existence of DISCLAIMER, LICENSE, NOTICE, README,
> RELEASE_NOTES files in the extracted source bundle.
> [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
> the extracted source bundle.
> [OK] Verify the staged source README, RELEASE_NOTE files correspond to
> those in the extracted source bundle.
> [MINOR] Run RAT externally to ensure there are no surprises.
> [MINOR] Search for SNAPSHOT references:
> [OK] Search for Copyright references, and if they are in headers, make
> sure these files containing them are mentioned in the LICENSE file.
> [MINOR] Build the project according to the information in the README.md
> file.
>
> Great job folks,
>
> Chris
>
>
>
> Am 18.08.20, 05:42 schrieb "Xiangdong Huang" :
>
> Hi IPMCs,
>
> We are still looking forward to getting votes from you...
>
> Many thanks!
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2020年8月14日周五 上午9:59写道：
>
> > Hello all,
> >
> > This is a call for vote to release Apache IoTDB (Incubating) version
> > 0.10.1, which is a bug-fix version of 0.10.0.
> >
> > The Apache IoTDB community has voted on and approved a proposal to
> release Apache
> > IoTDB (Incubating) version 0.10.1 (with 12 +1 votes).
> >
> > We now kindly request the Incubator PMC members review and vote on
> this incubator
> > release.
> >
> > Apache IoTDB (incubating) (Database for Internet of Things) is an
> > integrated data management engine designed for timeseries data.
> >
> > IoTDB community vote and result thread:
> >
> > Result:
> >
> >
> >
> https://lists.apache.org/thread.html/r3d2081bac4aed5217820a4587383150dc7b6471828675d9b6eeacf5e%40%3Cdev.iotdb.apache.org%3E
> >
> >
> > Vote:
> >
> >
> >
> https://lists.apache.org/thread.html/r94e5dcac19d5f2ba9990a95cc1fb5232074702de9f1c326d27eebfe3%40%3Cdev.iotdb.apache.org%3E
> >
> >
> > The release candidates (RC3):
> > https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/
> >
> > Git tag for the release (RC3):
> >
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.1
> >
> > Hash for the release tag:
> > 023fb84e0b76c0ac64b7a9ac098c640f26795a25
> >
> >
> > Release Notes:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/RELEASE_NOTES.md
> >
> >
> > The artifacts have been signed with Key: 2206EF8F64C35889, which can
> be found
> > in the keys file:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
> >
> > Look at here for how to verify this release candidate:
> >
> >
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> >
> > The vote will be open for at least 72 hours.
> >
> >
> > The vote will be passed if there are at least 3 IPMC +1 votes and
> there is
> > no -1 vote.
> >
> > Please vote 

Re: [VOTE] Release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0 (ROUND3)

[JUN GAO]

Hello everyone, because the Maven 2 staging repository is deleted by mistake. 
So I Redeployed it, The latest maven 2 staging repository address is :

https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1045/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
 


And we still need 2 binging votes on this release. I eagerly hope that someone 
can vote for us.


Thank you very much !

> 2020年8月14日 下午9:59，JUN GAO  写道：
> 
> Hello IPMC , We still need 2 binding votes on this release. Can anyone help 
> vote?
> 
> Thank you very much!
> 
> GAO JUN mailto:gaojun2...@gmail.com>>于2020年8月13日 
> 周四12:07写道：
> Hello IPMC and DolphinScheduler Community,
> 
>  
> 
> This is a call for a vote to release Apache DolphinScheduler Maven Plugin 
> (Incubating) version 1.0.0.
> 
>  
> 
> The Apache DolphinScheduler community has voted on and approved a proposal to 
> release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0
> 
>  
> 
> We now kindly request the Incubator IPMC members review and vote on this 
> incubator release.
> 
>  
> 
> Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow 
> scheduling system, dedicated to solving the complex dependencies in data 
> processing, making the scheduling system out of the box for data processing.
> 
>  
> 
> DolphinScheduler community vote and result threads:
> 
> https://lists.apache.org/thread.html/re4d26427e71440ab4dd2cb97d10c4f500e15ea5534836ff0fa54bd78%40%3Cdev.dolphinscheduler.apache.org%3E
>  
> 
>  
> 
> https://lists.apache.org/thread.html/r82b2fe70fdf64842a9167e5798a79d00eef70ddcb99e4db0f0d66a09%40%3Cdev.dolphinscheduler.apache.org%3E
>  
> 
>  
> 
> The release candidates:
> 
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
>  
> 
>  
> 
> Maven 2 staging repository:
> 
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1039/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
>  
> 
>  
> 
> Git tag for the release:
> 
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0
>  
> 
>  
> 
> Release Commit ID:
> 
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/10280f9d52ad5cfaf1256fcf5a7955be23d464c5
>  
> 
>  
> 
> Keys to verify the Release Candidate:
> 
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS 
> 
>  
> 
> Look at here for how to verify this release candidate:
> 
> https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md
>  
> 
>  
> 
> The vote will be open for at least 72 hours or until a necessary number of
> 
> votes are reached.
> 
> Please vote accordingly:
> 
>  
> 
> [ ] +1 approveg
> 
>  
> 
> [ ] +0 no opinion
> 
>  
> 
> [ ] -1 disapprove with the reason
> 
>  
> 
> Checklist for reference:
> 
>  
> 
> [ ] Download links are valid.
> 
>  
> 
> [ ] Checksums and PGP signatures are valid.
> 
>  
> 
> [ ] Source code artifacts have correct names matching the current release.
> 
>  
> 
> [ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
> 
>  
> 
> [ ] All files have license headers if necessary.
> 
>  
> 
> [ ] No compiled archives bundled in source archive.
> 
>  
> 
> More detail checklist please refer:
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>  
> 
>  
> 
> The following votes are carried over from DolphinScheduler dev mailing list:
> 
> +1  Furkan KAMACI
> 
>  
> 
>  
> 
> DolphinScheduler(Incubator)  PPMC
> 
> Jun Gao 高俊
> 
>  
> 
> gaojun2...@gmail.com 
> -- 
> 
>  
> 
> -- 
> DolphinScheduler(Incubator)  PPMC
> Jun Gao 高俊
> 
> gaojun2...@gmail.com 
> 

Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

[Michael Wall]

Thanks for the follow up Ciyong.  You are right, -vv did not enable
verbose. If I had used -VV (with capital V's) I would have gotten
output.

Good luck on the vote.

Mike

On Tue, Aug 18, 2020 at 2:43 AM Chen, Ciyong  wrote:
>
> Hi Michael,
>
> Thank you for your time to review and vote.
>
> Regarding your questions:
> > - Does anything with mshadow need to change now that it has passed 
> > clearance.
> From source code release perspective, I don't think there's anything we need 
> to change as mshadow is already in the code base with the correct license 
> header. CC @Sheng to see if any comments.
>
> > - I tried running tests a couple of ways after the build I build but they 
> > just hung for 15 min before I control-c'd them.  Maybe I didn't wait long 
> > enough, but there was no indication anything was running.
> The test suite contains lots of test cases which will be very time consuming, 
> " ctest -vv" doesn't enable the verbose output thus looks like it hung as no 
> output on the terminal.
> By using "ctest --verbose" which turns on the verbose and will give more 
> details for all the test cases.
> Currently, the entire test suite will run through many different 
> configurations of hardware and docker image via CI pipeline.
>
> Thanks,
> -Ciyong
>
> -Original Message-
> From: Michael Wall 
> Sent: Tuesday, August 18, 2020 9:54 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
>
> +1 from me
>
> Checked
> - signatures
> - incubating in name
> - License, Notice and Disclaimer
> - Compiled from source with CPP bindings using 
> https://mxnet.apache.org/versions/1.6/get_started/build_from_source#install-mxnet-for-python,
> https://mxnet.apache.org/versions/1.6/get_started/cpp_setup and 
> https://github.com/apache/incubator-mxnet/blob/1.7.0.rc1/config/linux.cmake
>
> Couple of questions
> - Does anything with mshadow need to change now that it has passed clearance.
> - I tried running tests a couple of ways after the build I build but they 
> just hung for 15 min before I control-c'd them.  Maybe I didn't wait long 
> enough, but there was no indication anything was running.
>
> Here is the run
>
> ```
> [0/1] Running tests...
> Test project 
> /home/mikewall/Desktop/mxnet-1.7.0/apache-mxnet-src-1.7.0.rc1-incubating/build
> Start 1: AllTestsInmxnetUnitTests
> ^Cninja: build stopped: interrupted by user.
> ```
>
> And here is my history fwiw
>
> ```
> sudo apt-get install -y build-essential git ninja-build ccache 
> libopenblas-dev libopencv-dev cp config/linux.cmake config.cmake rm -rf build 
> cmake -S. -Bbuild -DUSE_CPP_PACKAGE=1 -DCMAKE_BUILD_TYPE=Release -GNinja 
> cmake --build build cmake --build build --target test cd build && ctest -vv 
> ```
>
> On Mon, Aug 17, 2020 at 2:27 PM Sheng Zha  wrote:
> >
> > Hi Justin,
> >
> > Since the blocking issue has been resolved, would you mind changing your 
> > vote? Thanks.
> >
> > Regards,
> > Sheng
> >
> > On 2020/07/26 01:27:39, Justin Mclean  wrote:
> > > Hi,
> > >
> > > -1 (binding) as this release contains code that hasn’t gone though IP 
> > > clearance (mshadow).
> > >
> > > I checked:
> > > - incubating in name
> > > - disclaimer exists
> > > - LICENSE and NOTICE have improved but I did not do an exhaustive
> > > check
> > > -  No unexpected binary file
> > > - ASF files have ASF headers
> > > - unable to compile from source
> > >
> > > It also seems that this code may have been released before the
> > > PPMC/IPMC vote is over see [1][2][3][4] There are also branding and
> > > trademark issue with this site [5] This is in addition to the issues
> > > previously noted with releases, branding and trademarks.[6]
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> > > 1. https://sourceforge.net/projects/apache-mxnet.mirror/
> > > 2.
> > > https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native
> > > -mkl/1.7.0-b/ 3. https://mvnrepository.com/artifact/ai.djl.mxnet
> > > 4.
> > > https://aur.archlinux.org/packages/?O=0=nd=mxnet=v=d=
> > > 50_Search=Go
> > > 5. https://djl.ai
> > > 6. https://jira.apache.org/jira/browse/INCUBATOR-253
> > > 
> > > - 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: 

RE: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

[Chen, Ciyong]

Hi Michael,

Thank you for your time to review and vote.

Regarding your questions:
> - Does anything with mshadow need to change now that it has passed clearance.
From source code release perspective, I don't think there's anything we need to 
change as mshadow is already in the code base with the correct license header. 
CC @Sheng to see if any comments.

> - I tried running tests a couple of ways after the build I build but they 
> just hung for 15 min before I control-c'd them.  Maybe I didn't wait long 
> enough, but there was no indication anything was running.
The test suite contains lots of test cases which will be very time consuming, " 
ctest -vv" doesn't enable the verbose output thus looks like it hung as no 
output on the terminal. 
By using "ctest --verbose" which turns on the verbose and will give more 
details for all the test cases. 
Currently, the entire test suite will run through many different configurations 
of hardware and docker image via CI pipeline.

Thanks,
-Ciyong

-Original Message-
From: Michael Wall  
Sent: Tuesday, August 18, 2020 9:54 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

+1 from me

Checked
- signatures
- incubating in name
- License, Notice and Disclaimer
- Compiled from source with CPP bindings using 
https://mxnet.apache.org/versions/1.6/get_started/build_from_source#install-mxnet-for-python,
https://mxnet.apache.org/versions/1.6/get_started/cpp_setup and 
https://github.com/apache/incubator-mxnet/blob/1.7.0.rc1/config/linux.cmake

Couple of questions
- Does anything with mshadow need to change now that it has passed clearance.
- I tried running tests a couple of ways after the build I build but they just 
hung for 15 min before I control-c'd them.  Maybe I didn't wait long enough, 
but there was no indication anything was running.

Here is the run

```
[0/1] Running tests...
Test project 
/home/mikewall/Desktop/mxnet-1.7.0/apache-mxnet-src-1.7.0.rc1-incubating/build
Start 1: AllTestsInmxnetUnitTests
^Cninja: build stopped: interrupted by user.
```

And here is my history fwiw

```
sudo apt-get install -y build-essential git ninja-build ccache libopenblas-dev 
libopencv-dev cp config/linux.cmake config.cmake rm -rf build cmake -S. -Bbuild 
-DUSE_CPP_PACKAGE=1 -DCMAKE_BUILD_TYPE=Release -GNinja cmake --build build 
cmake --build build --target test cd build && ctest -vv ```

On Mon, Aug 17, 2020 at 2:27 PM Sheng Zha  wrote:
>
> Hi Justin,
>
> Since the blocking issue has been resolved, would you mind changing your 
> vote? Thanks.
>
> Regards,
> Sheng
>
> On 2020/07/26 01:27:39, Justin Mclean  wrote:
> > Hi,
> >
> > -1 (binding) as this release contains code that hasn’t gone though IP 
> > clearance (mshadow).
> >
> > I checked:
> > - incubating in name
> > - disclaimer exists
> > - LICENSE and NOTICE have improved but I did not do an exhaustive 
> > check
> > -  No unexpected binary file
> > - ASF files have ASF headers
> > - unable to compile from source
> >
> > It also seems that this code may have been released before the 
> > PPMC/IPMC vote is over see [1][2][3][4] There are also branding and 
> > trademark issue with this site [5] This is in addition to the issues 
> > previously noted with releases, branding and trademarks.[6]
> >
> > Thanks,
> > Justin
> >
> >
> > 1. https://sourceforge.net/projects/apache-mxnet.mirror/
> > 2. 
> > https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native
> > -mkl/1.7.0-b/ 3. https://mvnrepository.com/artifact/ai.djl.mxnet
> > 4. 
> > https://aur.archlinux.org/packages/?O=0=nd=mxnet=v=d=
> > 50_Search=Go
> > 5. https://djl.ai
> > 6. https://jira.apache.org/jira/browse/INCUBATOR-253
> > 
> > - 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

Re: [VOTE] Release Apache IoTDB 0.10.1

[Christofer Dutz]

Hi all,

TL/DR:
+1 binding

Longer version:
I started evaluating. As usual the IoTDB release candidate is in very good 
shape. 

Here some super minor things I noticed:

- It seems the ".plan" templates in 
server/src/assembly/resources/tools/logVisualize/plans support comments, then 
they should contain the Apache headers.
- The karaf feature is referencing a SNAPSHOT version and not even the version 
in this release 0.10.0.SNAPSHOT
- The Dockerfile is also referencing an older SNAPSHOT version 0.10.0-SNAPSHOT
- The mvnw.sh file doesn't seem to be executable
- In the README perhaps point out that you can a) download the source bundle 
from one of the mirrors or you can clone from gitbox or github ... what you're 
describing in the README is actually not downloading, but cloning the repo. I 
would probably base the documentation on downloading a release archive and put 
the cloning in the developer part of the documentation. Reason is: Only for the 
source-bundles can we really ensure this is what was voted on ... tags in 
Github can be changed.

[OK] Download all staged artifacts under the url specified in the release vote 
email into a directory we’ll now call download-dir. 
[OK] Verify the signature is correct: Additional Apache tutorial on how to 
verify downloads can be found here. 
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes:
[OK] Unzip the archive:
[OK] Verify the existence of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES 
files in the extracted source bundle.
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the 
extracted source bundle.
[OK] Verify the staged source README, RELEASE_NOTE files correspond to those in 
the extracted source bundle.
[MINOR] Run RAT externally to ensure there are no surprises.
[MINOR] Search for SNAPSHOT references:
[OK] Search for Copyright references, and if they are in headers, make sure 
these files containing them are mentioned in the LICENSE file.
[MINOR] Build the project according to the information in the README.md file.

Great job folks,

Chris



Am 18.08.20, 05:42 schrieb "Xiangdong Huang" :

Hi IPMCs,

We are still looking forward to getting votes from you...

Many thanks!

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2020年8月14日周五 上午9:59写道：

> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.1, which is a bug-fix version of 0.10.0.
>
> The Apache IoTDB community has voted on and approved a proposal to 
release Apache
> IoTDB (Incubating) version 0.10.1 (with 12 +1 votes).
>
> We now kindly request the Incubator PMC members review and vote on this 
incubator
> release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data.
>
> IoTDB community vote and result thread:
>
> Result:
>
>
> 
https://lists.apache.org/thread.html/r3d2081bac4aed5217820a4587383150dc7b6471828675d9b6eeacf5e%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
>
> 
https://lists.apache.org/thread.html/r94e5dcac19d5f2ba9990a95cc1fb5232074702de9f1c326d27eebfe3%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.1
>
> Hash for the release tag:
> 023fb84e0b76c0ac64b7a9ac098c640f26795a25
>
>
> Release Notes:
>
> 
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key: 2206EF8F64C35889, which can be 
found
> in the keys file:
>
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
>
> 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> The vote will be passed if there are at least 3 IPMC +1 votes and there is
> no -1 vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)
>
>
>


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

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.9.0

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

- didn't try - compile from source


On Mon, Aug 17, 2020 at 9:12 PM Wilfred Spiegelenburg 
wrote:

> Hello IPMC
>
>
>
> The Apache YuniKorn community has voted and approved the release Apache
>
> YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members review
>
> and vote in this release.
>
>
>
> YuniKorn is a standalone, universal resource scheduler that can support
>
> both long-running and batch workloads. The current release provides a fully
>
> functional resource scheduler for K8s.
>
>
>
> YuniKorn community vote thread:
>
>
> https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E
>
>
>
> Vote result thread:
>
>
> https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E
>
>
>
> Issues included in this release:
>
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799
>
>
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/
>
>
>
> This release has been signed with a PGP available here:
>
> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
>
>
>
> Git tag for the release:
>
>   - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0
>
>   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0
>
>   -
>
>
>
>
> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0
>
>   - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0
>
>
>
> The vote will be open for at least 72 hours or until the necessary number
>
> of votes is reached.
>
>
>
> Please vote accordingly:
>
>
>
> [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0
>
> [ ] +0
>
> [ ] -1 Do not approve (please specify the reason)
>
>
>
> Thanks,
>
> Wilfred Spiegelenburg
>
> Apache YuniKorn (Incubating)
>
>