Re: Retired podlings not being cleaned up

[sebb]

Still no action as far as I can tell.

On Mon, 30 Oct 2023 at 14:53, sebb  wrote:
>
> Tuweni and Datalab retired some while ago, but nothing much seems to
> have been done to close them down.
>
> Sebb

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

[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-280:


The Incubator PMC is ultimately responsible. Some parts have to be done by 
Infra on request from the IPMC.

> Datalab retired, but cleanup is incomplete
> --
>
> Key: INCUBATOR-280
> URL: https://issues.apache.org/jira/browse/INCUBATOR-280
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> As the subject says



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-280:


AFAIK, nothing has been done on this.
For example, the LDAP group still exists
https://dist.apache.org/repos/dist/dev/incubator/datalab/ still exists
Various resources such as Git, Website, Wiki appear to be still active (they 
should have comments to say the podling is retired)
etc.

> Datalab retired, but cleanup is incomplete
> --
>
> Key: INCUBATOR-280
> URL: https://issues.apache.org/jira/browse/INCUBATOR-280
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> As the subject says



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Retired podlings not being cleaned up

[sebb]

Tuweni and Datalab retired some while ago, but nothing much seems to
have been done to close them down.

Sebb

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

[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-279:


Ping

> Tuweni retired, but cleanup is incomplete
> -
>
> Key: INCUBATOR-279
> URL: https://issues.apache.org/jira/browse/INCUBATOR-279
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The LDAP project list still needs to be removed.
> Also podlings.xml and tuweni.xml need to be updated, and the website site 
> redirect needs to be set up.
> Maybe the retirement instructions need to be reviewed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

[Sebb (Jira)]

Sebb created INCUBATOR-280:
--

 Summary: Datalab retired, but cleanup is incomplete
 Key: INCUBATOR-280
 URL: https://issues.apache.org/jira/browse/INCUBATOR-280
 Project: Incubator
  Issue Type: Task
Reporter: Sebb


As the subject says



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: [VOTE] Release Apache Pekko(incubating) gRPC 1.0.1-RC1

[sebb]

On Tue, 17 Oct 2023 at 23:09, PJ Fanning  wrote:
>
> Thanks Sebb. I'll update future emails to use
> https://downloads.apache.org/incubator/pekko/KEYS

Great

> That file works for this RC - the KEYS file has the same contents as
> https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Agreed, but the two are not automatically synched, and have been known
to diverge.

> On Tue, 17 Oct 2023 at 22:57, sebb  wrote:
> >
> > On Thu, 12 Oct 2023 at 12:45, Matthew de Detrich
> >  wrote:
> > >
> > > Carrying over +1 vote from
> > > https://lists.apache.org/thread/s53trdc7prq3406jx64wo1rq4nbbkv63
> > >
> > > On Thu, Oct 12, 2023 at 6:15 AM PJ Fanning  wrote:
> > >
> > > > Hello Incubator Community,
> > > >
> > > > This is a call for a vote to release Apache Pekko(incubating)
> > > > gRPC version 1.0.1-RC1.
> > > >
> > > > The discussion thread:
> > > > https://lists.apache.org/thread/tlmk742qvm0tlfmk3o24cch41mtpwnx7
> > > >
> > > > The Pekko PPMC vote result:
> > > > https://lists.apache.org/thread/jsntxyy7wo5om0tqlp7rxzmz8oodt8pt
> > > >
> > > > The Pekko PPMC vote thread:
> > > > https://lists.apache.org/thread/ly3q9kfsovtnk6l5m8y8s8kgfs739g9x
> > > >
> > > > The release candidate:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/GRPC-1.0.1-RC1/
> > > >
> > > > This release has been signed with a *recently updated* PGP key, 
> > > > available
> > > > here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
> >
> > Please don't use the staging site for the KEYS URL.
> >
> > It needs to be the release site, i.e.
> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > or perhaps better the URL to which users are directed, i.e.
> > https://downloads.apache.org/incubator/pekko/KEYS
> > (this is served from the release site)
> >
> > > >
> > > > Release Notes:
> > > >
> > > > https://pekko.apache.org/docs/pekko-grpc/current/release-notes/index.html
> > > >
> > > > Git branch for the release:
> > > >
> > > > https://github.com/apache/incubator-pekko-grpc/tree/v1.0.1-RC1
> > > > Git commit ID: 53f91e8efb0416831483c34ad9ee9c211d8d
> > > >
> > > > Please download, verify, and test.
> > > >
> > > > We have also staged jars in the Apache Nexus Repository. These were
> > > > built with the same code
> > > > as appears in this Source Release Candidate. We would appreciate if
> > > > users could test with these too.
> > > > If anyone finds any serious problems with these jars, please also
> > > > notify us on this thread.
> > > >
> > > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > > >
> > > > In sbt, you can add this resolver.
> > > >
> > > > resolvers += "Apache Pekko Staging" at
> > > > "https://repository.apache.org/content/groups/staging";
> > > >
> > > >
> > > > The vote will be left open for at least 72 hours.
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > > >
> > > > Checklist for reference:
> > > >
> > > > [ ] Download links are valid.
> > > > [ ] Checksums and signatures.
> > > > [ ] LICENSE/NOTICE files exist
> > > > [ ] No unexpected binary files
> > > > [ ] Source files have ASF headers
> > > > [ ] Can compile from source
> > > >
> > > > To compile from the source, please refer to:
> > > >
> > > >
> > > > https://github.com/apache/incubator-pekko-grpc/blob/main/README.md#building-from-source
> > > >
> > > > Some notes about verifying downloads can be found at:
> > > >
> > > > https://pekko.apache.org/download.html#verifying-downloads
> > > >
> > > >
> > > > Here is my +1 (binding).
> > > > Matthew de Detrich has already voted +1 (binding) on the initial Pekko
> > > > team vote.
> > > >
> > > > Thanks,
> > > >
> >

Re: [VOTE] Release Apache Pekko(incubating) gRPC 1.0.1-RC1

[sebb]

On Thu, 12 Oct 2023 at 12:45, Matthew de Detrich
 wrote:
>
> Carrying over +1 vote from
> https://lists.apache.org/thread/s53trdc7prq3406jx64wo1rq4nbbkv63
>
> On Thu, Oct 12, 2023 at 6:15 AM PJ Fanning  wrote:
>
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Pekko(incubating)
> > gRPC version 1.0.1-RC1.
> >
> > The discussion thread:
> > https://lists.apache.org/thread/tlmk742qvm0tlfmk3o24cch41mtpwnx7
> >
> > The Pekko PPMC vote result:
> > https://lists.apache.org/thread/jsntxyy7wo5om0tqlp7rxzmz8oodt8pt
> >
> > The Pekko PPMC vote thread:
> > https://lists.apache.org/thread/ly3q9kfsovtnk6l5m8y8s8kgfs739g9x
> >
> > The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/GRPC-1.0.1-RC1/
> >
> > This release has been signed with a *recently updated* PGP key, available
> > here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Please don't use the staging site for the KEYS URL.

It needs to be the release site, i.e.
https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
or perhaps better the URL to which users are directed, i.e.
https://downloads.apache.org/incubator/pekko/KEYS
(this is served from the release site)

> >
> > Release Notes:
> >
> > https://pekko.apache.org/docs/pekko-grpc/current/release-notes/index.html
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko-grpc/tree/v1.0.1-RC1
> > Git commit ID: 53f91e8efb0416831483c34ad9ee9c211d8d
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code
> > as appears in this Source Release Candidate. We would appreciate if
> > users could test with these too.
> > If anyone finds any serious problems with these jars, please also
> > notify us on this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at
> > "https://repository.apache.org/content/groups/staging";
> >
> >
> > The vote will be left open for at least 72 hours.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] Source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> >
> > https://github.com/apache/incubator-pekko-grpc/blob/main/README.md#building-from-source
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> > Matthew de Detrich has already voted +1 (binding) on the initial Pekko
> > team vote.
> >
> > Thanks,
> >
> > PJ Fanning
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io

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

Re: Jira issues largely being ignored

[sebb]

On Tue, 3 Oct 2023 at 16:34, John Gemignani  wrote:
>
> Hi,
>
> I'll just give my 2 cents on this for the Apache AGE project, from my
> perspective,...
>
> In the early stages of Apache AGE we tried to use Jira. For a while, we
> actually were using it for day to day activities. However, the constant
> spam we had to remove daily, along with also having issues coming in
> through Github, coupled with our limited resources, forced us to make a
> choice between the two of them.
>
> I also recall it taking months to get permissions just to remove the spam
> that came in. While, I understand the delays involved with an open source
> projects' infrastructure, being nearly everyone is a volunteer, all of
> these items soured us on Jira. Github was just better suited to our needs,
> integrated better, and didn't have spam.
>
> We still do have discussions about using both, btw. However, for the size
> of our team, it would cause us to spend more time on "paperwork" than on
> design, research, issues, or code.
>
> I would surmise that we aren't the only project that has had similar
> internal discussions.

AFAIK, the INCUBATOR Jira has not had a problem with spam.
It does not have GitHub issues.
The problem is not volume (there have been fewer than 300 issues in 20 years).

I suspect the AGE project suffered more than most because of its name
being near the start of any alpha listing (and maybe because it is
short).

Also JIra logins now have to be authorised by projects; spam is much reduced.

> Hope this is helpful,
>
> John
>
> On Tue, Oct 3, 2023 at 8:04 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > Like any project, we are all volunteers here and this may mean that
> > sometimes issues may go unaddressed or unclosed. If something needs
> > attention you could bring it up on the mailing list.
> >
> > Kind Regards,
> > Justin
> > -
> > 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: Jira issues largely being ignored

[sebb]

On Tue, 3 Oct 2023 at 16:04, Justin Mclean  wrote:
>
> Hi,
>
> Like any project, we are all volunteers here and this may mean that sometimes 
> issues may go unaddressed or unclosed.

Yes, but there are hundreds of PMC members.
That should mean more help available.

> If something needs attention you could bring it up on the mailing list.

I thought I already did ... Jira notifications are sent to this list.

But to re-iterate:
- closing issues marked as CanBeClosed [1]
- https://issues.apache.org/jira/browse/INCUBATOR-279

[1] 
https://issues.apache.org/jira/browse/INCUBATOR-278?jql=project%20%3D%20INCUBATOR%20AND%20labels%20%3D%20CanBeClosed

> Kind Regards,
> Justin
> -
> 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: Jira issues largely being ignored

[sebb]

Anyone?

There's not much point having the Jira tracker if issues are ignored.

On Thu, 21 Sept 2023 at 23:31, sebb  wrote:
>
> There does not seem to be much attention given to Jira issues by
> Incubator members.
>
> There also are quite a few Jira issues that can be closed.
>
> Sebb

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

Jira issues largely being ignored

[sebb]

There does not seem to be much attention given to Jira issues by
Incubator members.

There also are quite a few Jira issues that can be closed.

Sebb

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

[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-253:
---
Labels: CanBeClosed  (was: )

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>  Labels: CanBeClosed
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-253:


MXNet graduated in 2022, so this issue can be closed

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-265:


PR has been applied

> Maybe incorrect clarification in Graduation Guide
> -
>
> Key: INCUBATOR-265
> URL: https://issues.apache.org/jira/browse/INCUBATOR-265
> Project: Incubator
>  Issue Type: Improvement
>  Components: guides
>Reporter: Yonglun Zhang
>Priority: Major
>  Labels: CanBeClosed
>
> The second section of 
> [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project]
>  
> Graduation *as a project* requires the formation of the new project by the 
> [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board].
>  
> I think change *as a project* to *as a top level project* makes sense.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-265:
---
Labels: CanBeClosed  (was: )

> Maybe incorrect clarification in Graduation Guide
> -
>
> Key: INCUBATOR-265
> URL: https://issues.apache.org/jira/browse/INCUBATOR-265
> Project: Incubator
>  Issue Type: Improvement
>  Components: guides
>Reporter: Yonglun Zhang
>Priority: Major
>  Labels: CanBeClosed
>
> The second section of 
> [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project]
>  
> Graduation *as a project* requires the formation of the new project by the 
> [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board].
>  
> I think change *as a project* to *as a top level project* makes sense.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (INCUBATOR-278) Outdated link to Apachecon 2022 on website

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-278:
---
Labels: CanBeClosed  (was: )

> Outdated link to Apachecon 2022 on website
> --
>
> Key: INCUBATOR-278
> URL: https://issues.apache.org/jira/browse/INCUBATOR-278
> Project: Incubator
>  Issue Type: Bug
>    Reporter: Sebb
>Priority: Major
>  Labels: CanBeClosed
>
> The Incubator home page has a prominent link to
> [https://www.apachecon.com/acna2022/]
>  
> This is very out of date.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (INCUBATOR-278) Outdated link to Apachecon 2022 on website

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-278:


Seems to have been fixed; this issue can be closed

> Outdated link to Apachecon 2022 on website
> --
>
> Key: INCUBATOR-278
> URL: https://issues.apache.org/jira/browse/INCUBATOR-278
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The Incubator home page has a prominent link to
> [https://www.apachecon.com/acna2022/]
>  
> This is very out of date.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Incubator release announcements should have disclaimer?

[sebb]

For example:

https://lists.apache.org/list?general@incubator.apache.org:lte=1M:Announce%20release

shows several recent announce emails, including:

https://lists.apache.org/thread/mod3g7fw695zbsl5cwgtl5okqj8khbvw
https://lists.apache.org/thread/9w6cj7lh217tpt04s8lng55b5n4spg1b
https://lists.apache.org/thread/rt4txnhvolm94r3hmrp0029p9mt5chsr

There are also some examples of emails with disclaimers:
https://lists.apache.org/thread/hb8gwp39rctm083xjp9dqyx2qlybdnno
https://lists.apache.org/thread/pkr1yn8hqxys6kl0qow038jczsfy3x70

Sebb

On Thu, 21 Sept 2023 at 17:54, sebb  wrote:
>
> As the subject implies: surely announcements of Incubator releases
> should include a prominent Incubation disclaimer?
>
> There have been some recent ones without:
> OpenDAL
> Wayang
> Devlake
> Paimon
> Pekko
>
> The releases are tagged with Incubating, but that is unlikely to mean
> much to 3rd parties.
>
> Sebb

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

Incubator release announcements should have disclaimer?

[sebb]

As the subject implies: surely announcements of Incubator releases
should include a prominent Incubation disclaimer?

There have been some recent ones without:
OpenDAL
Wayang
Devlake
Paimon
Pekko

The releases are tagged with Incubating, but that is unlikely to mean
much to 3rd parties.

Sebb

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

[jira] [Updated] (INCUBATOR-270) Install osschat GitHub app

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-270:
---
Labels: TOBECLOSED  (was: )

> Install osschat GitHub app
> --
>
> Key: INCUBATOR-270
> URL: https://issues.apache.org/jira/browse/INCUBATOR-270
> Project: Incubator
>  Issue Type: Task
>  Components: git
>Reporter: Heping Wang
>Priority: Major
>  Labels: TOBECLOSED
>
> Dear Infra team,
> Can you please install GitHub osschat([https://github.com/apps/osschat]) 
> application for our apache/incubator-linkis GitHub repo ?
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (INCUBATOR-273) remove jul...@apache.org from moderators of heron and toree podlings mailing lists

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-273:
---
Labels: TOBECLOSED  (was: )

> remove jul...@apache.org from moderators of heron and toree podlings mailing 
> lists
> --
>
> Key: INCUBATOR-273
> URL: https://issues.apache.org/jira/browse/INCUBATOR-273
> Project: Incubator
>  Issue Type: Task
>Reporter: Julien Le Dem
>Priority: Major
>  Labels: TOBECLOSED
>
> * 
> [comm...@heron.apache.org|https://lists.apache.org/list.html?comm...@heron.apache.org]
>  as jul...@apache.org
>  * 
> [d...@heron.apache.org|https://lists.apache.org/list.html?d...@heron.apache.org]
>  as jul...@apache.org
>  * 
> [iss...@heron.apache.org|https://lists.apache.org/list.html?iss...@heron.apache.org]
>  as jul...@apache.org
>  * 
> [priv...@heron.apache.org|https://lists.apache.org/list.html?priv...@heron.apache.org]
>  as jul...@apache.org
>  * 
> [u...@heron.apache.org|https://lists.apache.org/list.html?u...@heron.apache.org]
>  as jul...@apache.org
>  * 
> [comm...@toree.apache.org|https://lists.apache.org/list.html?comm...@toree.apache.org]
>  as jul...@apache.org
>  * 
> [d...@toree.apache.org|https://lists.apache.org/list.html?d...@toree.apache.org]
>  as jul...@apache.org
>  * 
> [priv...@toree.apache.org|https://lists.apache.org/list.html?priv...@toree.apache.org]
>  as jul...@apache.org



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (INCUBATOR-277) Allow GitHub Actions to create PRs

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-277:
---
Labels: TOBECLOSED  (was: )

> Allow GitHub Actions to create PRs
> --
>
> Key: INCUBATOR-277
> URL: https://issues.apache.org/jira/browse/INCUBATOR-277
> Project: Incubator
>  Issue Type: Wish
>Reporter: Junren Yu
>Priority: Major
>  Labels: TOBECLOSED
>
> I am a committer of [DevLake|https://github.com/apache/incubator-devlake]. 
> Since we are still in the initial iteration, we need to cherry-pick the 
> previous version after submitting the pr repair. I created a GitHub action 
> named "Auto Cherry Pick" in our repository. Currently, this action cannot be 
> used because the repository has not enabled the permission to allow the 
> action to submit pr. We want to be able to enable this permission in the 
> repository.
>  
> !https://user-images.githubusercontent.com/37237996/240861206-65885923-830e-47a3-866c-472f381267d6.jpeg!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated INCUBATOR-274:
---
Labels: TOBECLOSED  (was: )

> Gives Orbit (orbit.love) access to GitHub repos
> ---
>
> Key: INCUBATOR-274
> URL: https://issues.apache.org/jira/browse/INCUBATOR-274
> Project: Incubator
>  Issue Type: Task
>  Components: git
>Reporter: Hezheng Yin
>Priority: Major
>  Labels: TOBECLOSED
>
> *Update:* I just realized that I should open this issue at 
> [https://issues.apache.org/jira/projects/INFRA.] Please feel free to close 
> this issue. Sorry for the trouble.
>  
> Dear Infra Team,
>  
> I'm looking to set up Orbit (orbit.love, a community growth platform) for 
> DevLake. I ran into a permission issue when I tried to give Orbit access to 
> DevLake's repos as shown in this 
> [screenshot|https://user-images.githubusercontent.com/2908155/206342490-32d84f00-15df-49d3-b3d4-0b758c4ed3ac.png].
>  
> Is there any workaround that may get this integration working? Thanks in 
> advance for your guidance!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete

[Sebb (Jira)]

Sebb created INCUBATOR-279:
--

 Summary: Tuweni retired, but cleanup is incomplete
 Key: INCUBATOR-279
 URL: https://issues.apache.org/jira/browse/INCUBATOR-279
 Project: Incubator
  Issue Type: Bug
Reporter: Sebb


The LDAP project list still needs to be removed.

Also podlings.xml and tuweni.xml need to be updated, and the website site 
redirect needs to be set up.

Maybe the retirement instructions need to be reviewed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (INCUBATOR-278) Outdated link to Apachecon 2022 on website

[Sebb (Jira)]

Sebb created INCUBATOR-278:
--

 Summary: Outdated link to Apachecon 2022 on website
 Key: INCUBATOR-278
 URL: https://issues.apache.org/jira/browse/INCUBATOR-278
 Project: Incubator
  Issue Type: Bug
Reporter: Sebb


The Incubator home page has a prominent link to

[https://www.apachecon.com/acna2022/]

 

This is very out of date.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[sebb]

On Thu, 9 Feb 2023 at 12:21, Eason Chen  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) is a fully serverless platform used to
> build distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh 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 fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to EventMesh is a
> fully serverless platform used to build distributed event-driven
> applications; and be it further

The above sentence does not make sense; need to drop ' EventMesh is'

> RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> 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 EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuw

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[sebb]

On Thu, 9 Feb 2023 at 09:44, Eason Chen  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) is a fully serverless platform used to
> build distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh 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 EventMesh is a fully serverless platform used to build
> distributed event-driven applications.

The last phrase does not make sense; need to drop the words 'EventMesh is"

> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to EventMesh is a
> fully serverless platform used to build distributed event-driven
> applications; and be it further

The last phrase does not make sense; need to drop the words 'EventMesh is"

> RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> 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 EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   

Re: package names (pekko related)

[sebb]

On Wed, 12 Oct 2022 at 16:46, John D. Ament  wrote:
>
> We should keep in mind that the trademarks requirements and the release
> requirements are two different sets of requirements.  They're often
> conflated.  The main thing to remember with trademarks and naming is that
> the first time a project is referenced in documentation, websites, etc, it
> must be referred to as "Apache " and subsequent calls can just be
> "".  This would mean that README files in the source repo refer to the
> project this way, descriptions on github repos etc are all named this way
> as well.  Likewise, our release process indicates the source tarball for a
> release is named "apache-...tar.gz" or similar.  The foundation has
> always had a waving stance on binary releases, e.g. the JAR files you might
> download from Maven Central.  The convention (not requirement) is that
> those JAR files are packaged under "org.apache.".  Unless there's a
> good reason not to, projects should follow this if they publish to maven.
> By similar convention, we have applied this to the package names used by a
> project.  The existing projects I was able to look at within the ASF all
> used scala in a hybrid format with java code, meaning they had a mix of the
> two and within a JAR file had both java and scala sourced files.  They're
> not the best of examples as a result, but did all align to the
> "org.apache." naming convention.
>
> there is no requirement to have your package name start with
> org.apache.pekko, but by convention this is what is seen.

There are good reasons for this.
The ASF 'owns' the org.apache prefix, and can therefore ensure
uniqueness of names within that.

Who owns pekko? What's to stop two different projects using pekko.somename?

Furthermore, if there is any code already using pekko.*, we should not
release code that uses the same prefix.

>  A source release
> with source code starting with "pekko.*" would just as easily get a +1 to
> release from me as "org.apache.pekko.*" as long as any documentation in the
> source release said Apache Pekko (Incubating).
>
> On Tue, Oct 11, 2022 at 2:37 PM Matthew Benedict de Detrich
>  wrote:
>
> > I can’t speak for maven but since Akka works with sbt its more likely to
> > use sbt-assembly to perform any shading which handles cases like this (i.e.
> > see https://github.com/sbt/sbt-assembly#merge-strategy and
> > https://github.com/sbt/sbt-assembly#shading).
> >
> > --
> > Matthew de Detrich
> > Aiven Deutschland GmbH
> > Immanuelkirchstraße 26, 10405 Berlin
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > m: +491603708037
> > w: aiven.io e: matthew.dedetr...@aiven.io
> > On 11. Oct 2022, 07:37 -0500, tison , wrote:
> > > One point from the technical perspective:
> > >
> > > I remember that akka's config use akka. prefix and it causes several
> > issues
> > > prevent you shaded it. That is, Maven Shaded Plugin cannot distinguish a
> > > string literal starts with akka. a config key or package name.
> > >
> > > From this perspective, if possible, I tend to use org.apache.pekko in
> > > package name and use pekko. in the config name (or even akka? lol).
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Sheng Wu  于2022年10月11日周二 20:22写道：
> > >
> > > > Hi
> > > >
> > > > I am not sure about Kafka and Netbeans cases, as I was not working
> > > > inside the foundation back there.
> > > > For the recent years' new podlings, `org.apache.*` is preferred by the
> > > > incubator.
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > > PJ Fanning  于2022年10月11日周二 20:14写道：
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > I'm creating a new thread to avoid filling the Pekko thread with
> > emails
> > > > that are only partially related to the proposal.
> > > > >
> > > > > The current Akka code uses packages that start with 'akka.' and a
> > lot of
> > > > the people involved with Pekko seem to prefer to keep the use 'pekko.'
> > > > instead of 'org.apache.pekko.' when we rename the Akka packages.
> > > > >
> > > > > Kafka and Netbeans are examples of Apache projects that don't use
> > > > 'org.apache' prefix in their package names.
> > > > >
> > > > > Is 'pekko.' a viable option or is there a strong preference within
> > the
> > > > ASF and the Incubator PMC for 'org.apache.pekko.'?
> > > > >
> > > > > Regards,
> > > > > PJ
> > > > >
> > > > > -
> > > > > 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:

Re: [ALL] links to KEYS file in VOTE threads and download pages

[sebb]

Please note, this still applies, but several podlings don't seem to
have got the message.

Thanks!

On Mon, 22 Nov 2021 at 11:03, sebb  wrote:
>
> It is vital that the KEYS file is only referred to using a URL of the form
>
> https://downloads.apache.org/incubator//KEYS [1]
>
> This applies to VOTE emails as well as download pages.
>
> Why is this?
>
> KEYS files must remain available long for as long as a release is
> still available from the ASF archives.
>
> It is also important for the files used in a VOTE to correspond as far
> as possible with the ones that will be used by downloaders.
> (Obviously, that is not possible for the artifacts themselves as they
> cannot be published until after the vote). Furthermore, it is
> important that the KEYS file remain available after the vote has
> completed, in case there is a need to check any aspects of the vote.
>
> ==
>
> If your podling uses a template to create the vote email, please check
> that it uses the correct URL for the KEYS file, and fix it if not.
> Also check any developer docs to ensure the correct URL is used.
>
> Note: for a podling's first release, it is possible that the relevant
> directory under https://dist.apache.org/repos/dist/release/incubator/
> has yet to be created. This will need to be created, and the KEYS file
> populated, *before* the vote can begin. [It will be needed anyway once
> the vote succeeds]
>
> Thanks,
> Sebb
> [1] Some older pages may use
> https://www.apache.org/dist/incubator//KEYS
> This now redirects to https://downloads.apache.org/incubator//KEYS

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc2

[sebb]

On Mon, 4 Jul 2022 at 17:27, Liang Zhang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.11.0-rc2
>
> The Apache DevLake community has voted on and approved a proposal to release
> Apache DevLake (Incubating) version v0.11.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/8bnm8v1zvc97rxtd5yfsx53p27wjwtyh
>
> Vote result thread:
> https://lists.apache.org/thread/0n0t1mdcs2qkx6w2qlydojj4ptwp0h35
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.11.0-incubating-rc2/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.11.0-rc2
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/devlake/KEYS

Sorry, but this is not suitable as the KEYS link.
The dist/dev tree is ephemeral, and is not what is used by the download page.

Please ONLY use
https://downloads.apache.org/incubator/devlake/KEYS

Also, keys should only be maintained under
https://dist.apache.org/repos/dist/release/incubator/devlake/KEYS
which is the source of downloads.a.o

>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache DevLake(Incubating) community
>
>
> -
> 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 ShenYu(Incubating) as a TLP

[sebb]

On Sun, 19 Jun 2022 at 14:46, XiaoYu  wrote:
>
> Hi sebb,
>
> Thank you for your careful feedback.
>
> I will refactor the resolution and reflect it in the final submission
> to the apache board.
>
> 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 full lifecycle JAVA API gateway.
> Apache ShenYu provides dynamic, easy scalability and hot-pluggable features.
>
> RESOLVED, that the Apache ShenYu Project be and hereby is responsible
> for the creation and maintenance of software related to a full
> lifecycle JAVA API gateway.
> Apache ShenYu provides dynamic,easy scalability and hot-pluggable
> features; and be it further

Sorry, but that does not follow the standard template either.
The bit about "dynamic,easy scalability and hot-pluggable features" is
not relevant for the resolution.

It does not relate to the scope of the software.

> sebb  于2022年6月19日周日 20:40写道：
> >
> > On Sat, 18 Jun 2022 at 02:10, XiaoYu  wrote:
> > >
> > > Dear Apache Incubator Community,
> > >
> > > The Apache ShenYu community has a discussion thread [1],
> > > passed the community vote[2], and the vote result is published [3].
> > > We have discussed the graduation for ShenYu in the Incubator Community 
> > > [4],
> > > where no issues were raised and lots of positive responses were received.
> > >
> > > I would like to start this voting thread to request graduating Apache
> > > ShenYu (incubating) from the incubator as a TLP. Please provide your vote
> > > as one of the following options:
> > >
> > > [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator.
> > >
> > > [ ] +0 No opinion.
> > >
> > > [ ] -1 No, the ShenYu project is not ready to graduate, because ...
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > >
> > > ** Community **
> > >
> > > - 6 new PPMC members were added, bringing the total number of PPMC
> > > members to 30 from at least 15+ different organizations.
> > >
> > > - 7 new Committers were added, bringing the total number of 
> > > Committers 37.
> > >
> > > - 110+ new contributors participate in the community. The number
> > > of contributors is now 274 and growing.
> > >
> > > - The dev@shenyu.a.o mailing list currently has 357 subscribers,
> > > and all major project discussions are happening in the dev@shenyu.a.o.
> > >
> > > - 26 Bi-weekly online meetings were held between committers,
> > > contributors and users. The meeting minutes are recorded on the
> > > mailing list [5].
> > >
> > > - 1100+ pull requests merged [6], and 700+ issues closed [7] after
> > > into the apache incubator.
> > >
> > > ** Project **
> > >
> > > - 4 releases by 4 release managers.
> > >
> > > - ShenYu official website [8] is compliant with Apache Foundation
> > > requirements [9].
> > >
> > > - Project maturity model is detailed in [10].
> > >
> > > - See ShenYu Project Incubation Status [11] for more info.
> > >
> > > ** Brands ,License, and Copyright **
> > >
> > > - We submitted an application for the brand[12] and it has been
> > > reviewed and approved.
> > > - Apache ShenYu community maintains project code on GitHub, and all 
> > > modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [13]. All
> > > the status files, license headers, and copyright are up to date.
> > >
> > > ** PMC members **
> > >
> > >- Please see the proposed board resolution below and let us know what 
> > > you
> > > think. The initial PMC members were passed by the discussion and 
> > > invitation
> > > [14].
> > >
> > > [1] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> > > [2] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog
> > > [3] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7
> > > [4] https://lists.apache.org/thread/cc2myvs

Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP

[sebb]

On Sat, 18 Jun 2022 at 02:10, XiaoYu  wrote:
>
> Dear Apache Incubator Community,
>
> The Apache ShenYu community has a discussion thread [1],
> passed the community vote[2], and the vote result is published [3].
> We have discussed the graduation for ShenYu in the Incubator Community [4],
> where no issues were raised and lots of positive responses were received.
>
> I would like to start this voting thread to request graduating Apache
> ShenYu (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
>
> [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the ShenYu project is not ready to graduate, because ...
>
> The VOTE will remain open for at least 72 hours.
>
>
> ** Community **
>
> - 6 new PPMC members were added, bringing the total number of PPMC
> members to 30 from at least 15+ different organizations.
>
> - 7 new Committers were added, bringing the total number of Committers 37.
>
> - 110+ new contributors participate in the community. The number
> of contributors is now 274 and growing.
>
> - The dev@shenyu.a.o mailing list currently has 357 subscribers,
> and all major project discussions are happening in the dev@shenyu.a.o.
>
> - 26 Bi-weekly online meetings were held between committers,
> contributors and users. The meeting minutes are recorded on the
> mailing list [5].
>
> - 1100+ pull requests merged [6], and 700+ issues closed [7] after
> into the apache incubator.
>
> ** Project **
>
> - 4 releases by 4 release managers.
>
> - ShenYu official website [8] is compliant with Apache Foundation
> requirements [9].
>
> - Project maturity model is detailed in [10].
>
> - See ShenYu Project Incubation Status [11] for more info.
>
> ** Brands ,License, and Copyright **
>
> - We submitted an application for the brand[12] and it has been
> reviewed and approved.
> - Apache ShenYu community maintains project code on GitHub, and all 
> modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [13]. All
> the status files, license headers, and copyright are up to date.
>
> ** PMC members **
>
>- Please see the proposed board resolution below and let us know what you
> think. The initial PMC members were passed by the discussion and invitation
> [14].
>
> [1] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> [2] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog
> [3] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7
> [4] https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2
> [5] https://lists.apache.org/list.html?d...@shenyu.apache.org
> [6] 
> https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+
> [7] 
> https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03
> [8] https://shenyu.incubator.apache.org/
> [9] https://whimsy.apache.org/pods/project/shenyu
> [10] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md
> [11] https://incubator.apache.org/projects/shenyu.html
> [12] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197
> [13] https://github.com/apache/incubator-shenyu/blob/master/LICENSE
> [14] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko
>
> --
>
> Establish the Apache ShenYu 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 Apache ShenYu is a dynamic full lifecycle JAVA API gateway with 
> easy
> scalability and hot-pluggable features.

The phrase starting 'related to' does not make sense.

> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache ShenYu Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache ShenYu is a dynamic full lifecycle JAVA API gateway
> with easy scalability and hot-pluggable features; and be it further

The above paragraph does not make sense.

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

mxnet.apache.org very slow to load; uses 3rd party resources

[sebb]

I noticed that the Mxnet website is very slow to load (nearly 16 secs).

This seems to be due to trying to load widget.js from a 3rd party website.

Apart from the slow loading, I'm not sure this is allowed under the
new Privacy policy. [1]

There are also a couple of CSS files that are loaded remotely.

I think such 3rd party content should be downloaded to the Mxnet
website and served from there, as is required for Google fonts [2].
That should also fix the slow page loading.

Sebb
[1] https://privacy.apache.org/policies/privacy-policy-public.html
[2] https://privacy.apache.org/faq/committers.html#can-i-use-google-fonts

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

Re: [VOTE] Apache Toree 0.5.0-incubating RC5

[sebb]

On Wed, 6 Apr 2022 at 17:45, Luciano Resende  wrote:
>
> On Wed, Apr 6, 2022 at 7:30 AM sebb  wrote:
>
> > Where is the KEYS link?
>
> The checksums or revision number for the distribution packages?
> >
> > Without these, it would be nigh on impossible to prove that the
> > release is what was actually voted on.
> >
>
> Thanks for the feedback @sebb  , the link for keys is
> https://dist.apache.org/repos/dist/release/incubator/toree/KEYS

Sorry, but that is not the correct URL; votes should use the public
location, i.e.

https://downloads.apache.org/incubator/toree/KEYS

> As for the other questions, I am not sure I get what exactly you are
> looking for. All the artifacts have been generated from the tag mentioned
> in the vote document below, also, each of the artifacts has proper
> signatures (asc and sha512 ) see for example
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.5.0-incubating-rc5/toree/,
> maybe this was a little confusing because the artifacts are inside
> subdirectories?
>
> Please let me know if I misunderstood your questions.

Tags are mutable, but you have provided the hash, so that is fine.

However SVN directories are mutable, so the URL
https://dist.apache.org/repos/dist/dev/incubator/toree/0.5.0-incubating-rc5/toree/
may not be sufficient to identify the artifacts that are being voted on.

Either supply the revision, or better the hashes of the artifacts, as
they are independent of any changes to SVN.

>
> >
> > On Sat, 2 Apr 2022 at 03:53, Luciano Resende  wrote:
> > >
> > > Please vote to approve the release of Apache Toree 0.5.0-incubating
> > > (RC5) which brings support for Spark 3.0.
> > >
> > >
> > > The podling dev vote thread:
> > > https://www.mail-archive.com/dev@toree.apache.org/msg00112.html
> > >
> > > And the result:
> > > https://www.mail-archive.com/dev@toree.apache.org/msg00123.html
> > >
> > > Tag: v0.5.0-incubating-rc5 (a803d295d90b39881ccc3de93467a2af199e2dcd)
> > >
> > > https://github.com/apache/incubator-toree/tree/v0.5.0-incubating-rc5
> > >
> > > All distribution packages, including signatures, digests, etc. can be
> > found
> > > at:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/toree/0.5.0-incubating-rc5/
> > >
> > > Staging artifacts can be found at:
> > >
> > > https://repository.apache.org/content/repositories/orgapachetoree-1020
> > >
> > > The vote is open for at least 72 hours and passes if a majority of at
> > least
> > > 3 +1 PMC votes are cast.
> > >
> > > [ ] +1 Release this package as Apache Toree 0.5.0-incubating
> > > [ ] -1 Do not release this package because ...
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

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

Re: [VOTE] Apache Toree 0.5.0-incubating RC5

[sebb]

Where is the KEYS link?
The checksums or revision number for the distribution packages?

Without these, it would be nigh on impossible to prove that the
release is what was actually voted on.

On Sat, 2 Apr 2022 at 03:53, Luciano Resende  wrote:
>
> Please vote to approve the release of Apache Toree 0.5.0-incubating
> (RC5) which brings support for Spark 3.0.
>
>
> The podling dev vote thread:
> https://www.mail-archive.com/dev@toree.apache.org/msg00112.html
>
> And the result:
> https://www.mail-archive.com/dev@toree.apache.org/msg00123.html
>
> Tag: v0.5.0-incubating-rc5 (a803d295d90b39881ccc3de93467a2af199e2dcd)
>
> https://github.com/apache/incubator-toree/tree/v0.5.0-incubating-rc5
>
> All distribution packages, including signatures, digests, etc. can be found
> at:
>
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.5.0-incubating-rc5/
>
> Staging artifacts can be found at:
>
> https://repository.apache.org/content/repositories/orgapachetoree-1020
>
> The vote is open for at least 72 hours and passes if a majority of at least
> 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Toree 0.5.0-incubating
> [ ] -1 Do not release this package because ...
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

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

Re: [VOTE] Release Apache brpc (Incubating) 1.1.0

[sebb]

On Wed, 6 Apr 2022 at 06:49, Wang,Weibing  wrote:
>
> Hello IPMC,
>
> The Apache brpc community has voted and approved the release of Apache
> brpc (Incubating) 1.1.0. We now kindly request the IPMC members
> review and vote for this release.
>
> brpc is an industrial-grade RPC framework with extremely high performance,
> and it supports multiple protocols, full rpc features, and has many
> convenient tools. The current release provides some new features
> such as ipv6 and uds support, and fixes many bugs.
>
> brpc community vote thread:
> https://lists.apache.org/thread/6p7lqprok26r3ko456mpwb77vq4lx0qf
>
> Vote result thread:
> https://lists.apache.org/thread/o9k0prhdrpg975mr8prnrf3ghnmzvl3d
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.1.0/
>
> This release has been signed with a PGP available here:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS

Sorry, but that URL is not suitable for KEYS.
Please only use:
https://downloads.apache.org/incubator/brpc/KEYS

> Git tag for the release:
> https://github.com/apache/incubator-brpc/releases/tag/1.1.0
>
> Build guide and get started instructions can be found at:
> https://github.com/apache/incubator-brpc/blob/master/docs/en/getting_started.md
>
> 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 brpc (Incubating) 1.1.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Regards,
> Weibing Wang
> Apache brpc (Incubating)

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

Re: Is Livy podling still active?

[sebb]

On Tue, 5 Apr 2022 at 13:27, Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> AFAIR, a report has been submitted since. Report on cwiki doesn't mean
> it's the last send, we should check in the incubator board report.
>
> It's true that Livy is a "stable" project and kind of "mature"
> podling. IMHO, it should have graduated to TLP.

Huh?
That would require an active PMC, for which there is little evidence.

> As said, I tried to restart podling activity, but I didn't get a lot
> of updates: most people are Livy users but they don't seem to want to
> become contributors.

Nor does anyone seem to want to deal with issues.

> Regards
> JB
>
> On Tue, Apr 5, 2022 at 8:56 AM Javi Roman  wrote:
> >
> > Hi community!
> >
> > I see that the project is losing interest from the community, however it is
> > a project widely used by companies (I know personally). It is a pity that
> > the project may die.
> >
> > In my opinion one of the first actions to take is to recreate the reports
> > correctly (Podling reports). I have seen that the last one sent was in
> > August last year [1].
> >
> > Personally I would like to get involved in this project and help in
> > restarting it. If you like, I could be in charge of the next report, if
> > there is no inconvenience.
> >
> > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/August2021
> >
> >
> > On Mon, Apr 4, 2022 at 9:44 AM Jean-Baptiste Onofré  
> > wrote:
> >
> > > Hi,
> > >
> > > You are right, I tried to bring Livy podling back to active. We had
> > > few PRs/contributions and I also worked on reload4j switch and so on.
> > >
> > > If the activity around the code is low, there are few. Unfortunately,
> > > the mailing list is pretty quiet.
> > >
> > > Regards
> > > JB
> > >
> > > On Sun, Apr 3, 2022 at 11:46 PM Luciano Resende 
> > > wrote:
> > > >
> > > > There seem to have been a couple of initiatives to reboot the podling 
> > > > and
> > > > make it healthy again but without much success.
> > > >
> > > > What are other mentors' thoughts?
> > > >
> > > > On Sun, Apr 3, 2022 at 12:59 PM sebb  wrote:
> > > >
> > > > > There doesn't seem to be any recent activity on the mailing lists, and
> > > > > no recent commits.
> > > > >
> > > > > Sebb
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > http://twitter.com/lresende1975
> > > > http://lresende.blogspot.com/
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Is Livy podling still active?

[sebb]

There doesn't seem to be any recent activity on the mailing lists, and
no recent commits.

Sebb

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

Re: [MENTORS] Old releases in release area

[sebb]

On Mon, 13 Sept 2021 at 01:05, sebb  wrote:
>
> FTR, livy and nlpcraft need to clear up their release directories please:
>
> https://dist.apache.org/repos/dist/release/incubator/livy/
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/

Also
https://dist.apache.org/repos/dist/release/incubator/nlpcraft/java-client/

Still need to tidy the release area please.

> On Mon, 3 May 2021 at 01:43, Justin Mclean  wrote:
> >
> > Hi,
> >
> > Thanks to those who all responded and cleaned up their repo areas.
> >
> > Still to go are:
> > Crail [1]
> > DataLab [2]
> > Livy [3]
> > Milagro [4]
> > MXnet [5]
> > Nemo [6]
> > NLPCraft [7]
> > Pinot [8]
> >
> > Thanks,
> > Justin
> >
> >
> > 1. https://dist.apache.org/repos/dist/release/incubator/crail/ 
> > <https://dist.apache.org/repos/dist/release/incubator/crail/>
> > 2. https://dist.apache.org/repos/dist/release/incubator/datalab/ 
> > <https://dist.apache.org/repos/dist/release/incubator/datalab/>
> > 3. https://dist.apache.org/repos/dist/release/incubator/livy/ 
> > <https://dist.apache.org/repos/dist/release/incubator/livy/>
> > 4. https://dist.apache.org/repos/dist/release/incubator/milagro/ 
> > <https://dist.apache.org/repos/dist/release/incubator/milagro/>
> > 5. https://dist.apache.org/repos/dist/release/incubator/mxnet/ 
> > <https://dist.apache.org/repos/dist/release/incubator/mxnet/>
> > 6 https://dist.apache.org/repos/dist/release/incubator/nemo/ 
> > <https://dist.apache.org/repos/dist/release/incubator/nemo/>
> > 7. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/ 
> > <https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/>
> > 8. https://dist.apache.org/repos/dist/release/incubator/pinot/ 
> > <https://dist.apache.org/repos/dist/release/incubator/pinot/>
> >

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

Re: [ANNOUNCE] Spark Connectors v1.0.1 for Apache Doris(Incubating) Release

[sebb]

Please note that links to signatures and checksums MUST use https:

This applies to versions 0.12.0 and before on the download page

Thanks!

On Sat, 19 Mar 2022 at 14:11, 陈明雨  wrote:
>
> Hi All,
>
>
>
>
> We are pleased to announce the release of Spark Connectors v1.0.1 for Apache 
> Doris(Incubating).
>
> This is the first release of spark-doirs-connector. See:
> http://doris.incubator.apache.org/extending-doris/spark-doris-connector.html
> for more information
>
>
>
> The release is available at:
>
> http://doris.apache.org/downloads/downloads.html
>
>
>
>
> Thanks to everyone who has contributed to this release
>
>
>
>
> Best Regards,
>
>
>
>
> On behalf of the Doris team,
>
> morningman
>
> ---
>
> DISCLAIMER:
>
> Apache Doris (incubating) is an effort undergoing incubation at The
>
> Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
>
>
>
>
> Incubation is required of all newly accepted
>
> projects until a further review indicates that the
>
> infrastructure, communications, and decision making process have
>
> stabilized in a manner consistent with other successful ASF
>
> projects.
>
>
>
>
> While incubation status is not necessarily a reflection
>
> of the completeness or stability of the code, it does indicate
>
> that the project has yet to be fully endorsed by the ASF.
>
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org

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

Please remove superseded releases from dist areas

[sebb]

Several podlings have multiple releases under the dist/release area.
Old versions should please be removed shortly after the next version
has been released.

The policy can be found at [1] under the "Current and older releases" heading.

The podlings with multiple releases include:
AGE
Annotator
Brpc
Kyuubi
Liminal
Livy
Milagro
Mxnet
NLPCraft
Nuttx
Pegasus
Sedona
Teaclave
Tuweni

Please check your release area under [2], and remove any old versions.
Also please make sure that any release documentation mentions the need
to tidy up the release area.

Thanks,
Sebb
[1]  https://infra.apache.org/release-download-pages.html
[2]  https://dist.apache.org/repos/dist/release/incubator

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

Re: [VOTE] Apache StreamPipes 0.69.0 (incubating) RC1 release

[sebb]

On Fri, 11 Mar 2022 at 08:53, Philipp Zehnder  wrote:
>
> Hi all,
>
> this is a call for a vote to release Apache StreamPipes (incubating) 0.69.0.
> Apache StreamPipes (incubating) is self-service Industrial IoT toolbox to 
> enable non-technical users to connect, analyze and explore IIoT data streams.
> The Apache StreamPipes community has voted on and approved a proposal to 
> release Apache StreamPipes (incubating) 0.69.0.
>
> We now kindly request the Incubator PMC members to review and vote on this 
> release.
>
> Vote and result threads from the StreamPipes community:
> Result: https://lists.apache.org/thread/hmx9wtyjw6tqbx70gpvnr8tqcg0xxlcc
> Vote: https://lists.apache.org/thread/b58pym522yqn4qbdym549xh440boy52p
>
> From the PPMC vote, we carry over 1 binding IPMC votes:
> Christofer Dutz
>
> The vote will be open for at least 72 hours.
>
> Please vote accordingly:
>
> [] +1 approve (indicate what you validated - e.g., performed the checklist at 
> [6])
> [] +0 no opinion
> [] -1 reject (explanation required)
>
> One artifact is relevant for this vote:
>
> incubator-streampipes, staged at [1], available in Nexus at [2], release tag: 
> release/0.69.0, hash for the release tag: 
> 6893604222cb9c3efc4bf66dc0c21e3223c2c84e
>
>
> Per [3] "Before voting +1, [P]PMC members are required to download the signed 
> source code package,
> compile it as provided, and test the resulting executable on their own 
> platform,
> along with also verifying that the package meets the requirements of the ASF 
> policy on releases."
>
> A release validation guide is available at [4]. The KEYS file is available at 
> [5]

Sorry, but that URL is wrong; see below.

>
>
> Thanks for taking your time for validating this release!
>
> Philipp
>
>
> [1] https://dist.apache.org/repos/dist/dev/incubator/streampipes/0.69.0/rc1/
> [2] 
> https://repository.apache.org/content/repositories/orgapachestreampipes-1016
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4] 
> https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release
> [5] https://dist.apache.org/repos/dist/dev/incubator/streampipes/KEYS

That URL is not suitable.

Please use the public URL, i.e.

https://downloads.apache.org/incubator/streampipes/KEYS


>
>
> -
> 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 Liminal (incubating) 0.0.4rc2-incubating

[sebb]

On Tue, 15 Feb 2022 at 16:28, Lior Schachter  wrote:
>
> Hi All,
>
> We would like to vote on RC2 of version 0.0.4. The main purpose of V
> 0.0.4 is to provide a clear extensibility API for developers to add
> their own implementations of liminal abstractions - executor, task,
> image builder. In addition this version supports Apache Airflow 2.0.
>
> Liminal community vote and result threads:
> Vote:
> https://lists.apache.org/thread/1sw1zvyq45ozml09l7g2lhbdcd995lqw
>
> Result:
> https://lists.apache.org/thread/tcn3bmkc76hjx1f39p06xsq8jz9b2hgs
>
> Installation and testing instructions can be found in the README included.
>
> The release files, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/0.0.4rc2-INCUBATING/
>
> The tag to be voted on:
>
> https://github.com/apache/incubator-liminal/releases/tag/0.0.4rc2-incubating
>
> The SHA512 Checksum for these artifacts is:
>
> apache-liminal-0.0.4rc2-incubating-source.tar.gz:
> BEC25A76 9E5C12BD F262FF95 3AE3E26D 8F19294C 16E45605 49F027F1
> 6A31ECC5 62BD7001 2E63D66B BEBBE319 D829FA04 B1051C1A DFC9A13D
> 6C861E62 5796B396
>
> Release artifacts are signed with the following key:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS

Please don't use the above URL for KEYS in vote emails or download pages.

Use https://downloads.apache.org/incubator/liminal/KEYS instead.

The copy of KEYS at
https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS is
redundant.

It should be maintained instead at:
https://dist.apache.org/repos/dist/release/incubator/liminal/KEYS
(this is the source for downloads.apache.org)

> For more information about the contents of this release,
> see:https://issues.apache.org/jira/projects/LIMINAL/versions/12350079
>
> Please vote on releasing this package as Apache Liminal
> 0.0.4-INCUBATING. A majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Liminal 0.0.4
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Regards,
> Lior Schachter

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

Re: [VOTE] Graduate Apache AGE (Incubating) as a Top Level Project

[sebb]

On Thu, 13 Jan 2022 at 23:37, Eya Badal  wrote:
>
> Dear everyone,
>
> We are closing this vote, for now, to address and fix the feedbacks that we 
> received for Apache AGE TLP graduation. We will reopen the vote once we 
> address all the feedback.

Just noticed that the mailing lists only have one moderator each (the
same person).

Remember that moderation requests expire after a few days so it is
important to have several moderators to provide proper coverage for
absences. Generally a minimum of 3 is recommended.

> Thank you very much,
> Eya
>
> On 2022/01/06 02:15:18 Eya Badal wrote:
> > Dear Incubator Community,
> >
> > Having passed the Community Graduation Vote [1] by the AGE community with a 
> > vote result to graduate the incubation [2], we have discussed Apache AGE's 
> > graduation in the general@incubator [DISCUSS] thread [3].
> >
> > Here is the official request to vote to graduate the Apache AGE project as a
> > Top Level Project.
> >
> > Please provide your vote as one of the following options:
> >
> > [ ] +1 - Recommend graduation of Apache AGE as a Top Level
> > [ ] 0   - I don't feel strongly about it, but don't object
> > [ ] -1  - Do not recommend the graduation of Apache AGE because …
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > In addition to building and releasing software the Apache way, the AGE
> > project community has grown in the following areas:
> >
> > - Close to 900 commits
> > - 4 new committers and 1 expected to accept the invitation
> > - 3 new PPMC from 3 different companies/institutions
> > - Gathered > 500 GitHub stars
> > - 4 Apache releases (0.3.0, 0.4.0, 0.5.0, 0.6.0) [4]
> > - 6 mentors, 8 PPMC members (mentors excluded), and 2 committers (mentors
> > and PPMC members excluded)
> > - Contributions span more than 20 countries across the globe including
> > Australia, Belarus, Belgium, China, France, Germany, Ireland, Israel,
> > Italy, Luxembourg, The Netherlands, Nigeria, The Philippines, Russia, South
> > Korea, Thailand, UK, Ukraine, USA and Vietnam
> > - Developed and maintained Apache AGE website [5]
> > - Created and automated documentation to support multiple versions of
> > AGE. [6]
> > - Developer conversations at d...@age.apache.org
> > - Assessed ourselves against the Apache Project maturity matrix [7] and
> > didn't find any issues
> >
> > [1] https://lists.apache.org/thread/q2cgbnhvpzk2k0m8yfh89lzc75qym9k9
> > [2] https://lists.apache.org/thread/lr3x9bm8jyv6o5kvyh7cf3tyxrpp2kwm
> > [3] https://lists.apache.org/thread/jvrtvcw1zb8gf286css7tvol94r3qd68
> > [4] Release notes at Apache AGE website  under the
> > Releases menu.
> > [5] https://age.apache.org/
> > [6] Documentation at Apache AGE website  under the
> > Documentation menu.
> > [7] Apache Project maturity matrix at Apache AGE website
> >  under the COMMUNITY menu.
> >
> >
> > 
> > Establish the Apache AGE 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 implementing openCypher Graph query processing engine on
> > PostgreSQL, one of the most advanced open source relational database
> > management systems.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache AGE Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache AGE Project be and hereby is responsible for
> > the creation and maintenance of software related to implementing
> > openCypher Graph query processing engine on PostgreSQL, one of the most
> > advanced open source relational database management systems; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache AGE" 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 AGE Project, and to
> > have primary responsibility for management of the projects within the
> > scope of responsibility of the Apache AGE 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 AGE Project:
> >
> >  * Dehowe Feng 
> >  * Eya Badal   
> >  * Felix Cheung
> >  * Jasper Blues
> >  * John Gemignani  
> >  * Josh Innis  
> >  * Juan Pan
> >  * Kevin Ratnasekera   
> >  * Mason Sharp 
> >  * Nick Sorrell
> >  * Pieterjan De Potter 
> >  * Raphael Bircher 
> >  * Suneel Marthi   
> >  * Von Gosling

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

[sebb]

On Sat, 8 Jan 2022 at 04:17, Craig Russell  wrote:
>
> Hi,
>
> It looks like the project whimsy page shows some concerns highlighted below.
> https://whimsy.apache.org/roster/ppmc/age
>
> > On Dec 17, 2021, at 10:28 AM, Dave Fisher  wrote:
> >
> > Four more concerns:
> >
> > (1) Three of the PPMC members are not subscribed to the private mailing 
> > list.
> >
> Jasper Blues?
> Mason Sharp?
> Raphael Bircher?

Also Nick Sorrell does not appear to be subscribed.

>
> > (2) Four of the Committers including some of the PPMC members have not 
> > mapped their apache id to their GitHub id. How can they contribute?
> >
> • eya.abdi...@bitnine.net (not recognised)
> • john.gemign...@bitnine.net (not recognised)
>
> > (3) No one has been added to the PPMC.
> >
> > (4) Are all of the License Headers taken care of? I’m seeing a PR that 
> > indicates they are not. [1]
> >
> > Regards,
> > Dave
> >
> > [1] https://github.com/apache/incubator-age/pull/150
> >
> >> On Dec 16, 2021, at 6:11 PM, John D. Ament  wrote:
> >>
> >> Hi
> >>
> >> Putting aside this subproject for a moment I am concerned with your
> >> contributor vs committer counts. If you’ve had 68 contributors why are the
> >> numbers for new committers and PPMC so low?
> >>
> >> John
> >>
> >>
> >> On Thu, Dec 16, 2021 at 21:08 Eya Badal  wrote:
> >>
> >>> Hello Willem,
> >>>
> >>> Thank you very much for your feedback. There have been four official
> >>> Apache releases for the Apache AGE (incubating) project. AGE Viewer is a
> >>> sub-project of Apache AGE. As I know, the AGE viewer sub-project will 
> >>> start
> >>> the process for the first Apache release today or tomorrow.
> >>>
> >>> Best regards,
> >>> Eya
> >>>
> >>> On 2021/12/17 01:12:55 Willem Jiang wrote:
>  Hi,
> 
>  I just found out that we don't have the Apache release of AGE viewer,
>  even though there are a bunch of tags in github[1].
>  I also found the recent change[1] in master. It looks like we just
>  addressed the License issue during the release of 0.6.0.
>  The release process documentation[1] should be hosted on the website
>  of age.apache.org instead of using a good drive[3] to host.
> 
>  It's quite important that we learn to follow the Apache release
>  policies during the incubation process.
> 
>  Please double check with the mentors for the release of AGE viewer.
> 
>  [1]https://github.com/apache/incubator-age-viewer/tags
>  [2]https://github.com/apache/incubator-age/pull/157/files
>  [3]
> >>> https://drive.google.com/file/d/1zvAESVg7fRdSsxUuuOc3rHMkHcaOF28j/view?usp=sharing
> 
>  Willem Jiang
> 
>  Twitter: willemjiang
>  Weibo: 姜宁willem
> 
>  On Tue, Dec 14, 2021 at 5:04 AM Eya Badal  wrote:
> >
> > Dear Everyone,
> >
> >
> > Having passed the Community Graduation Vote [1] by the AGE community
> >>> with a
> > vote result to graduate the incubation [2], our assessment is that
> >>> Apache
> > AGE (Incubating) is ready to graduate as a TLP.
> >
> > We would like to raise the topic for discussion with the IPMC.
> >
> > In addition to building and releasing software the Apache way, the AGE
> > project community has grown in the following areas:
> >
> >
> >  -
> >
> >  Close to 900 commits
> >  -
> >
> >  68 unique contributors
> >  -
> >
> >  4 new committers and 1 new PPMC from 3 different
> >>> companies/institutions
> >  -
> >
> >  Gathered > 500 GitHub stars
> >  -
> >
> >  4 Apache releases (0.3.0, 0.4.0, 0.5.0, 0.6.0) [3]
> >  -
> >
> >  6 mentors, 6 PPMC members (mentors excluded) and 4 committers
> >>> (mentors
> >  and PPMC members excluded)
> >
> >
> >  -
> >
> >  Contributions span more than 20 countries across the globe including
> >  Australia, Belarus, Belgium, China, France, Germany, Ireland,
> >>> Israel,
> >  Italy, Luxembourg, The Netherlands, Nigeria, The Philippines,
> >>> Russia, South
> >  Korea, Thailand, UK, Ukraine, USA, and Vietnam
> >  -
> >
> >  Developed and maintained Apache AGE website [4]
> >  -
> >
> >  Created and automated documentation to support multiple versions of
> >>> AGE.
> >  [5]
> >  -
> >
> >  Developer conversations at d...@age.apache.org
> >  -
> >
> >  Assessed ourselves against the Apache Project maturity matrix [6]
> >>> and
> >  didn't find any issues
> >
> >
> >
> > [1] https://lists.apache.org/thread/q2cgbnhvpzk2k0m8yfh89lzc75qym9k9
> >
> > [2] https://lists.apache.org/thread/lr3x9bm8jyv6o5kvyh7cf3tyxrpp2kwm
> >
> > [3] Release at Apache AGE website  under the
> > Releases menu.
> >
> > [4] https://age.apache.org/
> >
> > [5] Documentation at Apache AGE website 
> >>> under
> > the Documen

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

[sebb]

On Sat, 8 Jan 2022 at 20:46, Craig Russell  wrote:
>
> Hi Josh,
>
> > On Jan 8, 2022, at 7:45 AM, Josh Innis  wrote:
> >
> > Hi Craig,
> >
> > John Gemingnani (john.gemign...@bitnine.net) is mapped to the github
> > address jrgemignani. If John isn't getting credit for his work: we need to
> > fix this immediately.
>
> The problem here is that John is subscribed to the private list as 
> john.gemign...@bitnine.net but his profile at id.apache.org only shows his 
> gmail email address.
> He can fix this at id.apache.org.

Or using Whimsy

> > Same with Eya (Eya is mapped to: eyab
> > eya.abdi...@bitnine.net).
>
> It looks like Eya's profile at id.apache.org has a typo in her email 
> "btinine" address.
>
> > I don't understand how they are not mapped. John
> > and Eya have been here from the beginning and if they are not getting
> > credit for their years of work on Apache AGE: please let us know. I am
> > confused to see their names on the list of PPMC members who have not linked
> > their apache id to their Github id, because I remember all of us doing so
> > and all of us have had a multi-year long influence on the project.
>
> The problem is not that they are not getting credit for their contributions 
> but that the email addresses subscribed to the private list are not in their 
> profile at id.apache.org.

AFAICT they are both subscribed twice - once with an address that is
in their LDAP record, and once with an address that is not registered.

> This is trivial for them to fix.

Indeed, using id.apache.org or Whimsy.

John needs to add his address and Eya needs to correct the typo.

> Warm regards,
> Craig
> >
> > Everyone else: please subscribe to the private mailing list. Otherwise I
> > will create an email discussion to have you removed from the project.
> >
> > On Sat, Jan 8, 2022 at 12:17 PM Craig Russell  wrote:
> >
> >> Hi,
> >>
> >> It looks like the project whimsy page shows some concerns highlighted
> >> below.
> >> https://whimsy.apache.org/roster/ppmc/age
> >>
> >>> On Dec 17, 2021, at 10:28 AM, Dave Fisher  wrote:
> >>>
> >>> Four more concerns:
> >>>
> >>> (1) Three of the PPMC members are not subscribed to the private mailing
> >> list.
> >>>
> >> Jasper Blues?
> >> Mason Sharp?
> >> Raphael Bircher?
> >>
> >>
> >>> (2) Four of the Committers including some of the PPMC members have not
> >> mapped their apache id to their GitHub id. How can they contribute?
> >>>
> >>• eya.abdi...@bitnine.net (not recognised)
> >>• john.gemign...@bitnine.net (not recognised)
> >>
> >>> (3) No one has been added to the PPMC.
> >>>
> >>> (4) Are all of the License Headers taken care of? I’m seeing a PR that
> >> indicates they are not. [1]
> >>>
> >>> Regards,
> >>> Dave
> >>>
> >>> [1] https://github.com/apache/incubator-age/pull/150
> >>>
>  On Dec 16, 2021, at 6:11 PM, John D. Ament 
> >> wrote:
> 
>  Hi
> 
>  Putting aside this subproject for a moment I am concerned with your
>  contributor vs committer counts. If you’ve had 68 contributors why are
> >> the
>  numbers for new committers and PPMC so low?
> 
>  John
> 
> 
>  On Thu, Dec 16, 2021 at 21:08 Eya Badal  wrote:
> 
> > Hello Willem,
> >
> > Thank you very much for your feedback. There have been four official
> > Apache releases for the Apache AGE (incubating) project. AGE Viewer is
> >> a
> > sub-project of Apache AGE. As I know, the AGE viewer sub-project will
> >> start
> > the process for the first Apache release today or tomorrow.
> >
> > Best regards,
> > Eya
> >
> > On 2021/12/17 01:12:55 Willem Jiang wrote:
> >> Hi,
> >>
> >> I just found out that we don't have the Apache release of AGE viewer,
> >> even though there are a bunch of tags in github[1].
> >> I also found the recent change[1] in master. It looks like we just
> >> addressed the License issue during the release of 0.6.0.
> >> The release process documentation[1] should be hosted on the website
> >> of age.apache.org instead of using a good drive[3] to host.
> >>
> >> It's quite important that we learn to follow the Apache release
> >> policies during the incubation process.
> >>
> >> Please double check with the mentors for the release of AGE viewer.
> >>
> >> [1]https://github.com/apache/incubator-age-viewer/tags
> >> [2]https://github.com/apache/incubator-age/pull/157/files
> >> [3]
> >
> >> https://drive.google.com/file/d/1zvAESVg7fRdSsxUuuOc3rHMkHcaOF28j/view?usp=sharing
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Tue, Dec 14, 2021 at 5:04 AM Eya Badal  wrote:
> >>>
> >>> Dear Everyone,
> >>>
> >>>
> >>> Having passed the Community Graduation Vote [1] by the AGE community
> > with a
> >>> vote result to graduate the incubation [2], our assessment is that
> > Apache
> >>> AGE (Incuba

Re: [VOTE] Graduate Apache AGE (Incubating) as a Top Level Project

[sebb]

On Thu, 6 Jan 2022 at 22:58, Dave Fisher  wrote:
>
> Hi -
>
> Have a look at https://whimsy.apache.org/roster/ppmc/age and see that 4 PPMC 
> members are not subscribed to private.
>
> Also there are two of your mentors who are not subscribed. Those two probably 
> have not done anything for the AGE podling.

There are also two unrecognised email addresses subscribed to the private list.
These could well belong to existing PPMC members.
If so, please ask them to add them to their LDAP records using Whimsy:
Goto https://whimsy.apache.org/roster/committer/__self__ and add to
the 'Email addresses (alt)' field

> > On Jan 6, 2022, at 2:30 PM, Felix Cheung  wrote:
> >
> > I am definitely in private@ and in a bunch of dev@ discussion. Not sure if
> > that was mis reported.
> >
> >
> > On Wed, Jan 5, 2022 at 11:15 PM Justin Mclean 
> > wrote:
> >
> >> Hi,
> >>
> >>> * Dehowe Feng 
> >>> * Eya Badal   
> >>> * Felix Cheung
> >>> * Jasper Blues
> >>> * John Gemignani  
> >>> * Josh Innis  
> >>> * Juan Pan
> >>> * Kevin Ratnasekera   
> >>> * Mason Sharp 
> >>> * Nick Sorrell
> >>> * Pieterjan De Potter 
> >>> * Raphael Bircher 
> >>> * Suneel Marthi   
> >>> * Von Gosling 
> >>
> >> Looking at this list there are several people who:
> >> a) Are not subscribed to the private list
> >> b) Have not taken part in discussions on the mailing list (that I can find)
> >>
> >> When putting together a graduation proposal, it's a good idea to find out
> >> if the proposed PMC are willing to be PMC members. While there is no real
> >> harm in having inactive PMC members, during graduation is a good time to
> >> trim the PMC to those who will actually do the work.
> >>
> >> Kind Regards,
> >> Justin
> >> -
> >> 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: [ANNOUNCE] Apache EventMesh (incubating) 1.3.0 available

[sebb]

It would be helpful to send a corrected announce.

Also ideally set up a redirect for the incorrect link

On Tue, 4 Jan 2022 at 02:15, Eason Chen  wrote:
>
> Thanks, Willem, we already updated it.
>
> On Tue, Jan 4, 2022 at 9:56 AM Willem Jiang  wrote:
>
> > The download link should be
> >
> > https://eventmesh.apache.org/download/
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, Dec 30, 2021 at 6:49 PM sebb  wrote:
> > >
> > > On Thu, 30 Dec 2021 at 06:43, mikexue  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Apache EventMesh (incubating) Team is glad to announce the new release
> > > > of Apache EventMesh (incubating) 1.3.0.
> > > >
> > > > Apache EventMesh (incubating) is a dynamic cloud-native eventing
> > > > infrastructure used to decouple the application and backend middleware
> > > > layer, which supports a wide range of use cases that encompass complex
> > > > multi-cloud, widely distributed topologies using diverse technology
> > > > stacks.
> > > >
> > > > Download Links:
> > https://eventmesh.apache.org/projects/eventmesh/download/
> > >
> > > Link does not work.
> > >
> > > > Release Notes:
> > https://eventmesh.apache.org/events/release-notes/v1.3.0/
> > > >
> > > > Website: https://eventmesh.apache.org/
> > > >
> > > > EventMesh Resources:
> > > > - Issue: https://github.com/apache/incubator-eventmesh/issues
> > > > - Mailing list: d...@eventmesh.apache.org
> > > >
> > > > Apache EventMesh (incubating) Team
> > > >
> > > > -
> > > > 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: dev-unsubscr...@eventmesh.apache.org
> > For additional commands, e-mail: dev-h...@eventmesh.apache.org
> >
> >

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

Re: [ANNOUNCE] Apache EventMesh (incubating) 1.3.0 available

[sebb]

On Thu, 30 Dec 2021 at 06:43, mikexue  wrote:
>
> Hi all,
>
> Apache EventMesh (incubating) Team is glad to announce the new release
> of Apache EventMesh (incubating) 1.3.0.
>
> Apache EventMesh (incubating) is a dynamic cloud-native eventing
> infrastructure used to decouple the application and backend middleware
> layer, which supports a wide range of use cases that encompass complex
> multi-cloud, widely distributed topologies using diverse technology
> stacks.
>
> Download Links: https://eventmesh.apache.org/projects/eventmesh/download/

Link does not work.

> Release Notes: https://eventmesh.apache.org/events/release-notes/v1.3.0/
>
> Website: https://eventmesh.apache.org/
>
> EventMesh Resources:
> - Issue: https://github.com/apache/incubator-eventmesh/issues
> - Mailing list: d...@eventmesh.apache.org
>
> Apache EventMesh (incubating) Team
>
> -
> 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 InLong 0.12.0-incubating RC0

[sebb]

On Sat, 25 Dec 2021 at 14:29, Goson zhang  wrote:
>
> Today is Christmas, and Merry Christmas, everyone!
>
> If Santa Claus is still giving gifts, I hope he will pay attention to our
> chimney😀
>
> Goson zhang  于2021年12月25日周六 22:22写道：
>
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache InLong(Incubating) version
> > 0.12.0-incubating RC0
> >
> > The Apache InLong community has voted on and approved a proposal to
> > release
> > Apache InLong(Incubating) version 0.12.0-incubating RC0
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > InLong community vote thread:
> > • https://lists.apache.org/thread/yrvt1mso9khk44wjjornjqrbv25bngjj
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/9qvtq0szkh2k6gyr2f5fvvkcfcxkmnh0
> >
> > The release candidate:
> > •
> > https://dist.apache.org/repos/dist/dev/incubator/inlong/0.12.0-incubating-RC0/
> >
> > Git tag for the release:
> > •
> > https://github.com/apache/incubator-inlong/tree/0.12.0-incubating-RC0
> >
> > Release notes:
> > •
> > https://github.com/apache/incubator-inlong/releases/tag/0.12.0-incubating-RC0
> >
> > The artifacts signed with PGP key A4D4D578, corresponding to
> > dockerzh...@apache.org, that can be found in keys file:
> > • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS

-1

Sorry, but that is not a suitable URL for VOTE emails.
As explained in numerous recent email threads on this very list.

Please resend the email using the URL

https://downloads.apache.org/incubator/inlong/KEYS

> >
> > The vote will be open for at least 72 hours or until necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache InLong(Incubating) community
> >

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

Re: [ANNOUNCE] Release Apache MXNet (incubating) version 1.9.0

[sebb]

On Thu, 23 Dec 2021 at 02:49, Serge Panev  wrote:
>
> Dear all,
>
> The Apache MXNet (incubating) community is happy to announce Apache MXNet 
> (incubating) version 1.9.0!
>
> Apache MXNet (incubating) is a deep learning framework designed for both 
> efficiency and flexibility. It allows you to mix symbolic and imperative 
> programming to maximize efficiency and productivity.
>
> A full list of the changes in this release can be found in the release notes:
> https://github.com/apache/incubator-mxnet/releases/tag/1.9.0
>
> A link to the download page can be found here:
> https://mxnet.apache.org/versions/1.9.0/get_started/download.html

The download page has a broken link for version 1.8.0. Typo in the source URL.

Also, it's not very user-friendly to use 'Download' for all the link text.

Normally the link text is the base name of the file, or in the case of
hashes and sigs it is the extension.

For example one might put:

1.9.0  apache-mxnet-src-1.9.0-incubating.tar.gz ascsha512

Using text such as the above makes it clearer to the user what they are getting.

> If you prefer to build from source and experiment with various compile-time 
> configuration options, use this link to get the instructions:
> https://mxnet.apache.org/get_started/build_from_source
>
> Or you can download and play with MXNet easily using one of the options below:
>
> 1. The pip packages can be found here:
> https://pypi.python.org/pypi/mxnet
>
> 2. The Docker Images can be found here:
> https://hub.docker.com/r/mxnet/python/
>
> The release tag:
> https://github.com/apache/incubator-mxnet/tree/1.9.0
>
> MXNet Resources
>
> - Our discussion forum (https://github.com/apache/incubator-mxnet/discussions)
> - MXNet dev mailing list 
> (https://lists.apache.org/list.html?d...@mxnet.apache.org)
> - StackOverflow mxnet tag (https://stackoverflow.com/questions/tagged/mxnet)
> - MXNet website (https://mxnet.incubator.apache.org)
> - Follow MXNet Development on Github 
> (https://github.com/apache/incubator-mxnet/issues)
> - MXNet Confluence Wiki for Developers 
> (https://cwiki.apache.org/confluence/display/MXNET)
> - Apache Slack #mxnet Channel (https://the-asf.slack.com/archives/C7FN4FCP9)
>
> Social Media
>
> - Apache MXNet on Twitter (https://twitter.com/apachemxnet)
> - Contributor and user blogs about MXNet (https://medium.com/apache-mxnet)
> - Discuss MXNet on r/mxnet (https://www.reddit.com/r/mxnet)
> - Apache MXNet YouTube channel (https://www.youtube.com/apachemxnet)
> - Apache MXNet on LinkedIn (https://www.linkedin.com/company/apache-mxnet)
>
>
>
> For more information on Apache MXNet (incubating), please see:
> https://mxnet.incubator.apache.org/
>
> Best regards,
> Apache MXNet (incubating) Team
>
> ___
>
> DISCLAIMER:
>
> Apache MXNet (incubating) is an effort undergoing incubation at The Apache 
> Software Foundation (ASF), sponsored by the name of Apache Incubator PMC. 
> Incubation is required of all newly accepted projects until a further review 
> indicates that the infrastructure, communications, and decision making 
> process have stabilized in a manner consistent with other successful ASF 
> projects. While incubation status is not necessarily a reflection of the 
> completeness or stability of the code, it does indicate that the project has 
> yet to be fully endorsed by the ASF.

-
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.12.1 (RC1)

[sebb]

On Mon, 20 Dec 2021 at 17:43, Chaoran Yu  wrote:
>
> Hi Sebb,
>
> Thanks for the pointer. We have removed the keys from the dev location. Now 
> my key is only present at 
> https://downloads.apache.org/incubator/yunikorn/KEYS.

Please re-issue the VOTE thread with the correct URL.

>
> On 2021/12/20 11:29:36 sebb wrote:
> > On Mon, 20 Dec 2021 at 04:29, Chaoran Yu  wrote:
> > >
> > > Hello IPMC,
> > >
> > > The Apache YuniKorn community has voted and approved the release of 
> > > Apache YuniKorn (incubating) 0.12.1 (RC1). We now kindly request IPMC 
> > > members review and vote for this release.
> > >
> > > YuniKorn is a standalone, universal resource scheduler that can support 
> > > both long-running and batch workloads. The current release offers 
> > > enhancements and improvements in a number of areas: node sorting 
> > > performance, gang scheduling, logging and observability, and scheduler 
> > > interface. It also contains an upgraded Kubernetes dependency (v1.20) and 
> > > now supports running on Kubernetes versions 1.19, 1.20 and 1.21.
> > >
> > > YuniKorn community vote thread: 
> > > https://lists.apache.org/thread/1yr4y7tftth5bfxlxfy4l8gmo3ypk4d2 
> > > <https://lists.apache.org/thread/1yr4y7tftth5bfxlxfy4l8gmo3ypk4d2>
> > >
> > > Vote result thread: 
> > > https://lists.apache.org/thread/z1f8wzx3t1n07qr8s4nfw224n74zryrs 
> > > <https://lists.apache.org/thread/z1f8wzx3t1n07qr8s4nfw224n74zryrs>
> > >
> > > Issues included in this release: 
> > > https://issues.apache.org/jira/projects/YUNIKORN/versions/12350843 
> > > <https://issues.apache.org/jira/projects/YUNIKORN/versions/12350843>
> > >
> > > The release candidate: 
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.1/ 
> > > <https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.1/>
> > >
> > > This release has been signed with a PGP available here: 
> > > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS 
> > > <https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS>
> >
> > -1
> >
> > Please do NOT use the above URL for KEYS.
> >
> > Only use
> >
> > https://downloads.apache.org/incubator/yunikorn/KEYS
> >
> > For the reasons why, please read recent emails to this list.
> > There have been several about the same issue.
> >
> > > Git tag for the release:
> > > - https://github.com/apache/incubator-yunikorn-core/tree/v0.12.1 
> > > <https://github.com/apache/incubator-yunikorn-core/tree/v0.12.1>
> > > - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.12.1 
> > > <https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.12.1>
> > > - 
> > > https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.12.1
> > >  
> > > <https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.12.1>
> > > - https://github.com/apache/incubator-yunikorn-web/tree/v0.12.1 
> > > <https://github.com/apache/incubator-yunikorn-web/tree/v0.12.1>
> > >
> > > 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.12.1
> > > [ ] +0
> > > [ ] -1 Do not approve (please specify the reason)
> > >
> > > Thanks,
> > > Chaoran Yu
> > > Apache YuniKorn (Incubating)
> > >
> > >
> >
> > -
> > 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 YuniKorn (Incubating) 0.12.1 (RC1)

[sebb]

On Mon, 20 Dec 2021 at 04:29, Chaoran Yu  wrote:
>
> Hello IPMC,
>
> The Apache YuniKorn community has voted and approved the release of Apache 
> YuniKorn (incubating) 0.12.1 (RC1). We now kindly request IPMC members review 
> and vote for this release.
>
> YuniKorn is a standalone, universal resource scheduler that can support both 
> long-running and batch workloads. The current release offers enhancements and 
> improvements in a number of areas: node sorting performance, gang scheduling, 
> logging and observability, and scheduler interface. It also contains an 
> upgraded Kubernetes dependency (v1.20) and now supports running on Kubernetes 
> versions 1.19, 1.20 and 1.21.
>
> YuniKorn community vote thread: 
> https://lists.apache.org/thread/1yr4y7tftth5bfxlxfy4l8gmo3ypk4d2 
> 
>
> Vote result thread: 
> https://lists.apache.org/thread/z1f8wzx3t1n07qr8s4nfw224n74zryrs 
> 
>
> Issues included in this release: 
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12350843 
> 
>
> The release candidate: 
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.1/ 
> 
>
> This release has been signed with a PGP available here: 
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS 
> 

-1

Please do NOT use the above URL for KEYS.

Only use

https://downloads.apache.org/incubator/yunikorn/KEYS

For the reasons why, please read recent emails to this list.
There have been several about the same issue.

> Git tag for the release:
> - https://github.com/apache/incubator-yunikorn-core/tree/v0.12.1 
> 
> - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.12.1 
> 
> - 
> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.12.1 
> 
> - https://github.com/apache/incubator-yunikorn-web/tree/v0.12.1 
> 
>
> 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.12.1
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Thanks,
> Chaoran Yu
> Apache YuniKorn (Incubating)
>
>

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

Re: [VOTE] Release Apache DataLab (incubating) 2.5.1

[sebb]

On Tue, 14 Dec 2021 at 09:37, Леонід Фролов  wrote:
>
> Hello Incubator Community, The Apache DataLab community has voted on and
> approved a proposal to release Apache DataLab (incubating) version 2.5.1.
> We now kindly request the Incubator PMC members review and vote in this
> release. DataLab is a platform for creating self-service, exploratory data
> science environments in the cloud using best-of-breed data science tools.
> DataLab includes a self-service web console, used to create and manage
> exploratory environments. It allows teams to spin up analytical
> environments with just a single click of a mouse. Once established, the
> environment can be managed by an analytical team itself, leveraging simple
> and easy-to-use web-based interface. DataLab community vote thread: •
> https://lists.apache.org/thread/6w9grmsq5pcx3jx9452dsdron3dkv877
>   Vote result thread: •
> https://lists.apache.org/thread/whdtt37k3g90kcb2pkh88rrwcmb0ygb2
> The release candidate: •
> https://dist.apache.org/repos/dist/dev/incubator/datalab/2.5.1/ Git tag for
> the release: •  https://github.com/apache/incubator-datalab/tree/2.5.1
>Release notes: •
> https://github.com/apache/incubator-datalab/blob/v2.5.1/RELEASE_NOTES.md
>
> The artifacts signed with PGP key 0399DE2A, corresponding to
> frolovl...@gmail.com. KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/datalab/KEYS

-1

Sorry, but this URL is not OK.
Please only use the following URL in votes:

https://downloads.apache.org/incubator/datalab/KEYS

For the reasons why, please review recent threads on this mailing list.

Please re-issue the vote with the correct URL and ensure any
documentation or templates that mention the KEYS file are suitably
updated.
Thanks.

>The vote will be open for at least 72 hours or until the necessary
> number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0
> no opinion [ ] -1 disapprove with the reason Thanks, The Apache DataLab
> (Incubating) Team

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

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.4.0-incubating (RC2)

[sebb]

 On Thu, 2 Dec 2021 at 15:13, Fei Wang  wrote:
>
> Hello Incubator Community,
>
> The Apache Kyuubi community has voted on and approved a proposal to release
> Apache Kyuubi(Incubating) version v1.4.0-incubating RC2.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Kyuubi community vote thread:
> https://www.mail-archive.com/dev@kyuubi.apache.org/msg01458.html
>
> Vote result thread:
> https://www.mail-archive.com/dev@kyuubi.apache.org/msg01492.html
>
> [ ] +1 Release this package as Apache Kyuubi {release_version}
> [ ] +0
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Kyuubi (Incubating), please see
> https://kyuubi.apache.org/
>
> The tag to be voted on is v1.4.0-incubating-rc2 (commit e6a7f54):
> https://github.com/apache/incubator-kyuubi/tree/v1.4.0-incubating-rc2
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.4.0-incubating-rc2/
>
> Signatures used for Kyuubi RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS

-1

Sorry, but as already mentioned several times recently, including in
relation to the Kyuubi vote for 1.3.0, this is NOT a suitable URL for
the KEYS file.

Please re-issue the VOTE with the correct URL.

> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachekyuubi-1014/
>
> Release Notes:
> https://github.com/apache/incubator-kyuubi/discussions/1450
>
> Thanks,
> On behalf of Apache Kyuubi(Incubating) community

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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc8

[sebb]

On Wed, 1 Dec 2021 at 16:18, Sheng Zha  wrote:
>
> > As such, it's best to have only a single KEYS file, which should be at
> https://dist.apache.org/repos/dist/release/incubator/mxnet/KEYS
>
> Makes sense. This should also simplify our release process. By the
> way, do we need to attach the KEYS inside the release archive? While I

No.

> don't see it on the release checklist, I just want to be sure we
> capture the right requirements.
>
> On Wed, Dec 1, 2021 at 10:53 AM sebb  wrote:
> >
> > On Wed, 1 Dec 2021 at 15:00, Sheng Zha  wrote:
> > >
> > > Thanks, Sebb. The correct KEYS file link should be
> > > https://downloads.apache.org/incubator/mxnet/KEYS, which comes from
> > > the release repo in dist.apache.org. @Serge let's restart the vote on
> > > general@ with the correct KEYS link.
> > >
> > > By the way, the KEYS file on release repo looks to be old and to have
> > > diverged from other KEYS files we have in the github repo, so I went
> > > ahead and updated the release repo with the union of all keys in our
> > > version control systems, and also updated the KEYS in other branches
> > > in github [1] [2]. I also updated the release process document in
> > > cwiki [3] with the instructions to update the KEYS in all repos and
> > > branches, and to include the downloads.apache.org link for KEYS on
> > > general@ vote.
> >
> > Thanks.
> >
> > Remember that KEYS are also required for archived releases, so should
> > never be dropped from the file once used for a release.
> >
> > As such, it's best to have only a single KEYS file, which should be at
> > https://dist.apache.org/repos/dist/release/incubator/mxnet/KEYS
> > as this is the official source for
> >  https://downloads.apache.org/incubator/mxnet/KEYS
> >
> > I don't think there is any need to have KEYS elsewhere, e,g, in GitHub.
> > If no copies exist, they cannot get out of date.
> >
> > The copy in downloads.a.o is the one that should be used as the source
> > for all signature checks.
> >
> > > Thanks,
> > > Sheng
> > >
> > > [1] https://github.com/apache/incubator-mxnet/pull/20764
> > > [2] https://github.com/apache/incubator-mxnet/pull/20765
> > > [3] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > >
> > > On Wed, Dec 1, 2021 at 5:05 AM sebb  wrote:
> > > >
> > > > On Wed, 1 Dec 2021 at 09:35, Serge Panev  
> > > > wrote:
> > > > >
> > > > > Dear community,
> > > > >
> > > > > This is a call for a releasing Apache MXNet (incubating) 1.9.0, 
> > > > > release
> > > > > candidate 8.
> > > > >
> > > > > Apache MXNet (incubating) community has voted and approved the 
> > > > > release.
> > > > >
> > > > > Vote thread:
> > > > > https://lists.apache.org/thread/cb8xjt38s7j78htzd174hyd0yogcwpr8
> > > > >
> > > > > Result thread:
> > > > > https://lists.apache.org/thread/rwpk1rzdyxmb6vv18d3lb96gqz4nvkdx
> > > > >
> > > > > The source tarball, including signatures, digests, etc. can be found 
> > > > > at:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.9.0.rc8/
> > > > >
> > > > > The tag to be voted upon is 1.9.0.rc8:
> > > > > https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc8
> > > > >
> > > > > The release hash is 8173b858dd1bff6be465bca2e2bbfc4eabd189b4:
> > > > > https://github.com/apache/incubator-mxnet/commit/8173b858dd1bff6be465bca2e2bbfc4eabd189b4
> > > > >
> > > > > KEYS file available:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> > > >
> > > > Sorry, but this is not valid as a KEYS link.
> > > > Please see various other recent discussions on this list.
> > > >
> > > > > For information about the contents of this release, see:
> > > > > https://cwiki.apache.org/confluence/display/MXNET/1.9.0+Release+Notes
> > > > >
> > > > > The vote will be open for 7 days.
> > > > >
> > > > > [ ] +1 release this package as 1.9.0.rc8
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 do not release this package because...
> > > > >
> > > > > Best regards,
> >

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc8

[sebb]

On Wed, 1 Dec 2021 at 15:00, Sheng Zha  wrote:
>
> Thanks, Sebb. The correct KEYS file link should be
> https://downloads.apache.org/incubator/mxnet/KEYS, which comes from
> the release repo in dist.apache.org. @Serge let's restart the vote on
> general@ with the correct KEYS link.
>
> By the way, the KEYS file on release repo looks to be old and to have
> diverged from other KEYS files we have in the github repo, so I went
> ahead and updated the release repo with the union of all keys in our
> version control systems, and also updated the KEYS in other branches
> in github [1] [2]. I also updated the release process document in
> cwiki [3] with the instructions to update the KEYS in all repos and
> branches, and to include the downloads.apache.org link for KEYS on
> general@ vote.

Thanks.

Remember that KEYS are also required for archived releases, so should
never be dropped from the file once used for a release.

As such, it's best to have only a single KEYS file, which should be at
https://dist.apache.org/repos/dist/release/incubator/mxnet/KEYS
as this is the official source for
 https://downloads.apache.org/incubator/mxnet/KEYS

I don't think there is any need to have KEYS elsewhere, e,g, in GitHub.
If no copies exist, they cannot get out of date.

The copy in downloads.a.o is the one that should be used as the source
for all signature checks.

> Thanks,
> Sheng
>
> [1] https://github.com/apache/incubator-mxnet/pull/20764
> [2] https://github.com/apache/incubator-mxnet/pull/20765
> [3] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
>
> On Wed, Dec 1, 2021 at 5:05 AM sebb  wrote:
> >
> > On Wed, 1 Dec 2021 at 09:35, Serge Panev  wrote:
> > >
> > > Dear community,
> > >
> > > This is a call for a releasing Apache MXNet (incubating) 1.9.0, release
> > > candidate 8.
> > >
> > > Apache MXNet (incubating) community has voted and approved the release.
> > >
> > > Vote thread:
> > > https://lists.apache.org/thread/cb8xjt38s7j78htzd174hyd0yogcwpr8
> > >
> > > Result thread:
> > > https://lists.apache.org/thread/rwpk1rzdyxmb6vv18d3lb96gqz4nvkdx
> > >
> > > The source tarball, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.9.0.rc8/
> > >
> > > The tag to be voted upon is 1.9.0.rc8:
> > > https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc8
> > >
> > > The release hash is 8173b858dd1bff6be465bca2e2bbfc4eabd189b4:
> > > https://github.com/apache/incubator-mxnet/commit/8173b858dd1bff6be465bca2e2bbfc4eabd189b4
> > >
> > > KEYS file available:
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> >
> > Sorry, but this is not valid as a KEYS link.
> > Please see various other recent discussions on this list.
> >
> > > For information about the contents of this release, see:
> > > https://cwiki.apache.org/confluence/display/MXNET/1.9.0+Release+Notes
> > >
> > > The vote will be open for 7 days.
> > >
> > > [ ] +1 release this package as 1.9.0.rc8
> > > [ ] +0 no opinion
> > > [ ] -1 do not release this package because...
> > >
> > > Best regards,
> > > Serge Panev
> > >
> >
> > -
> > 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 MXNet (incubating) version 1.9.0.rc8

[sebb]

On Wed, 1 Dec 2021 at 09:35, Serge Panev  wrote:
>
> Dear community,
>
> This is a call for a releasing Apache MXNet (incubating) 1.9.0, release
> candidate 8.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread/cb8xjt38s7j78htzd174hyd0yogcwpr8
>
> Result thread:
> https://lists.apache.org/thread/rwpk1rzdyxmb6vv18d3lb96gqz4nvkdx
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.9.0.rc8/
>
> The tag to be voted upon is 1.9.0.rc8:
> https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc8
>
> The release hash is 8173b858dd1bff6be465bca2e2bbfc4eabd189b4:
> https://github.com/apache/incubator-mxnet/commit/8173b858dd1bff6be465bca2e2bbfc4eabd189b4
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS

Sorry, but this is not valid as a KEYS link.
Please see various other recent discussions on this list.

> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/1.9.0+Release+Notes
>
> The vote will be open for 7 days.
>
> [ ] +1 release this package as 1.9.0.rc8
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
> Best regards,
> Serge Panev
>

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

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

On Mon, 29 Nov 2021 at 04:58, Julian Hyde  wrote:
>
>
>
> > On Nov 26, 2021, at 6:05 AM, sebb  wrote:
> >
> > On Fri, 26 Nov 2021 at 12:06, Matt Casters
> > mailto:matt.cast...@neo4j.com.invalid>> 
> > wrote:
> >
> >> As for Ricardo: he is indeed not a committer (yet) but an advisor to the
> >> project.  His insights as an educator have been very valuable and is in the
> >> process of becoming a committer.  Our mentor Julian informed us that (and I
> >> quote) "There’s no rule that the initial PMC can consist only of people who
> >> were committers in the podling".
> >
> > That is rather different from including people who are not yet ASF 
> > committers.
> >
> > AFAIK, most of the Infra and Whimsy tooling assumes that PMC members
> > have ASF ids.
>
> Yes, I gave them that advice. It seemed rather pointless to vote someone in 
> as a committer, just so that they could get an Apache ID, just so that they 
> could be could be included in the graduation resolution. And then to have to 
> repeat the vote for the graduation resolution because the email address has 
> changed.
>
> Is it possible to give someone an Apache id even if though are not a 
> committer or PMC member of any project? Maybe that would solve some of the 
> tooling issues.

You will have to ask Infra about that.

> Julian
>
>

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

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1

[sebb]

On Sun, 28 Nov 2021 at 06:08, Mingshen Sun  wrote:
>
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
> release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
> Rundong Zhou, Tongxin Li).
>
> Vote/result threads:
> - https://lists.apache.org/thread/41mpj6r4xo6h49mh5kj0npx6l3o2n2ct
> - https://lists.apache.org/thread/66kbrq8rq8f54pq46g6b1wzlmx70jttt
>
> The release candidate to be voted over is available at:
>   - 
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/
>
> The release candidate is signed with a GPG key available at:
>   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

Please do NOT use dist.apache.org for referencing KEYS.

See
https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04

> The Git commit for this release is:
>   - 
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=3984789a59fdfe58757a7a60e490a414ca918478
>
> The release note is available in:
>   - 
> https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.1
>
> Build guide and get started instructions can be found at:
>   - 
> https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/release-v0.2.0/docs/getting-started-with-optee-for-qemu-armv8.md
>
> The short version of building Teaclave from the source tarball:
>
> ```
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz
>
> $ # Instructions to verify the source tar: \
> https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
>
> $ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz && cd \
>   apache-teaclave-trustzone-sdk-0.2.0-incubating
>
> $ # Build the SDK and TAs
> $ docker run -v`pwd`:/teaclave -w /teaclave -it
> teaclave/teaclave-trustzone-sdk-build:0.3.0 \
>bash -c "source environment && make"
>
> $ # Test all examples with QEMU
> $ docker run -v`pwd`:/teaclave -w /teaclave -it
> teaclave/teaclave-trustzone-sdk-build:0.3.0 \
>bash -c "cd ci && ./ci.sh"
> ```
>
> The vote will be open for at least 72 hours. Everyone is welcome to
> vote. Please vote by replying to this thread explicitly.
>
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
>
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes. Please also reply with things you have checked.
>
> A checklist for reference:
>   - 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Best,
>
> Mingshen Sun
> Apache Teaclave (incubating) PPMC
> https://mssun.me
>
> -
> 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: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

On Fri, 26 Nov 2021 at 14:35, Matt Casters
 wrote:
>
> We're simply following the advice given here and by our mentors.  We didn't
> send an announcement mail in the beginning and then we did based on your
> valuable feedback.   If we need to copy the announcement of our releases to
> other mailing lists we can easily do so.

It is important to let users and developers know as well.
They may not be subscribed to the general announce list.
BTW, for the developer Hop list, a more detailed email may be appropriate.

Also you have not addressed the issue of the non-ASF committer.
I suspect there will be some issues with setting up the PMC if this is
not fixed.

>
>
>
> On Fri, Nov 26, 2021 at 3:05 PM sebb  wrote:
>
> > On Fri, 26 Nov 2021 at 12:06, Matt Casters
> >  wrote:
> > >
> > > Hi Sebb,
> > >
> > > Google found the announcement mails, for example [1] and [2].
> >
> > Not sure how I missed those.
> > However, AFAICT they were not announced on general@incubator nor on
> > any of the podling lists.
> >
> > > As for Ricardo: he is indeed not a committer (yet) but an advisor to the
> > > project.  His insights as an educator have been very valuable and is in
> > the
> > > process of becoming a committer.  Our mentor Julian informed us that
> > (and I
> > > quote) "There’s no rule that the initial PMC can consist only of people
> > who
> > > were committers in the podling".
> >
> > That is rather different from including people who are not yet ASF
> > committers.
> >
> > AFAIK, most of the Infra and Whimsy tooling assumes that PMC members
> > have ASF ids.
> >
> > > All the best,
> > > Matt
> > >
> > > [1]
> > >
> > http://mail-archives.apache.org/mod_mbox/www-announce/202108.mbox/%3cpony-5f4f7c3ea0e95da19b9d17390cc7ff00d42fdf75-9ff3db74f16d3e6f41d2f3ab4f35ecde94c43...@announce.apache.org%3E
> > > [2]
> > >
> > http://mail-archives.apache.org/mod_mbox/www-announce/202110.mbox/%3cpony-5f4f7c3ea0e95da19b9d17390cc7ff00d42fdf75-03d88d76819f10519156908b4369a9b7e1979...@announce.apache.org%3E
> > >
> > >
> > > On Fri, Nov 26, 2021 at 12:41 PM sebb  wrote:
> > >
> > > > On Fri, 26 Nov 2021 at 07:15, Bart Maertens 
> > wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > After a discussion[1] with and vote by[2] the Hop community, we
> > believe
> > > > > Apache Hop (Incubating) is ready
> > > > > to graduate as a TLP, and we'd like to bring it up in discussion
> > with the
> > > > > IPMC.
> > > > >
> > > > > The Hop community achievements since Hop joined the Incubator in
> > > > September
> > > > > 2020:
> > > > > - close to 3200 commits by 28 contributors
> > > > > - 4 releases(0.60, 0.70, 0.99, 1.0)
> > > >
> > > > However, it looks like none of these releases was ever announced.
> > > >
> > > > I could not find announce emails on:
> > > > general@incubator.a.o
> > > > *@hop.a.o
> > > > announce@apache.o
> > > >
> > > > Announcements are an important part of releases, so I would expect to
> > > > find some examples.
> > > >
> > > > > - 5 mentors, 6 PPMC members(mentors excluded) and 8
> > committers(mentors
> > > > and
> > > > > PPMC members excluded)
> > > > > - diverse committers and PPMC, with regular contributions from at
> > least 5
> > > > > different companies/institutes
> > > > > - Apache Hop website[3]
> > > > > - dev conversations at d...@hop.apache.org
> > > > > - assessed ourselves against the Apache Project maturity matrix[4]
> > and
> > > > > didn't find any issues.
> > > > >
> > > > > The topics that were discussed in the earlier [DISCUSS] thread[5]
> > have
> > > > been
> > > > > resolved:
> > > > > - old releases have been cleaned up
> > > > > - self-assessment is available[4]
> > > > > - Whimsy licensing issue is WiP (licensing is ok, the missing yaml
> > file
> > > > was
> > > > > added)
> > > > > - project description in the resolution was rewritten
> > > > > - an old pre-incubator website was removed[6]
> > > > >
> > > > > [1]
> > > > >

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

On Fri, 26 Nov 2021 at 12:06, Matt Casters
 wrote:
>
> Hi Sebb,
>
> Google found the announcement mails, for example [1] and [2].

Not sure how I missed those.
However, AFAICT they were not announced on general@incubator nor on
any of the podling lists.

> As for Ricardo: he is indeed not a committer (yet) but an advisor to the
> project.  His insights as an educator have been very valuable and is in the
> process of becoming a committer.  Our mentor Julian informed us that (and I
> quote) "There’s no rule that the initial PMC can consist only of people who
> were committers in the podling".

That is rather different from including people who are not yet ASF committers.

AFAIK, most of the Infra and Whimsy tooling assumes that PMC members
have ASF ids.

> All the best,
> Matt
>
> [1]
> http://mail-archives.apache.org/mod_mbox/www-announce/202108.mbox/%3cpony-5f4f7c3ea0e95da19b9d17390cc7ff00d42fdf75-9ff3db74f16d3e6f41d2f3ab4f35ecde94c43...@announce.apache.org%3E
> [2]
> http://mail-archives.apache.org/mod_mbox/www-announce/202110.mbox/%3cpony-5f4f7c3ea0e95da19b9d17390cc7ff00d42fdf75-03d88d76819f10519156908b4369a9b7e1979...@announce.apache.org%3E
>
>
> On Fri, Nov 26, 2021 at 12:41 PM sebb  wrote:
>
> > On Fri, 26 Nov 2021 at 07:15, Bart Maertens  wrote:
> > >
> > > Hi All,
> > >
> > > After a discussion[1] with and vote by[2] the Hop community, we believe
> > > Apache Hop (Incubating) is ready
> > > to graduate as a TLP, and we'd like to bring it up in discussion with the
> > > IPMC.
> > >
> > > The Hop community achievements since Hop joined the Incubator in
> > September
> > > 2020:
> > > - close to 3200 commits by 28 contributors
> > > - 4 releases(0.60, 0.70, 0.99, 1.0)
> >
> > However, it looks like none of these releases was ever announced.
> >
> > I could not find announce emails on:
> > general@incubator.a.o
> > *@hop.a.o
> > announce@apache.o
> >
> > Announcements are an important part of releases, so I would expect to
> > find some examples.
> >
> > > - 5 mentors, 6 PPMC members(mentors excluded) and 8 committers(mentors
> > and
> > > PPMC members excluded)
> > > - diverse committers and PPMC, with regular contributions from at least 5
> > > different companies/institutes
> > > - Apache Hop website[3]
> > > - dev conversations at d...@hop.apache.org
> > > - assessed ourselves against the Apache Project maturity matrix[4] and
> > > didn't find any issues.
> > >
> > > The topics that were discussed in the earlier [DISCUSS] thread[5] have
> > been
> > > resolved:
> > > - old releases have been cleaned up
> > > - self-assessment is available[4]
> > > - Whimsy licensing issue is WiP (licensing is ok, the missing yaml file
> > was
> > > added)
> > > - project description in the resolution was rewritten
> > > - an old pre-incubator website was removed[6]
> > >
> > > [1]
> > >
> > https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
> > > [2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
> > > [3] https://hop.incubator.apache.org/
> > > [4] https://hop.apache.org/community/incubator/
> > > [5] https://lists.apache.org/thread/jj46blkwrhf0l31srtzo5j5dcv7zsqz3
> > > [6] http://52.214.20.244
> > >
> > > Please see the proposed board resolution below and let us know what you
> > > think.
> > >
> > > The discussion will remain open for at least 72 hours.
> > >
> > > --
> > >
> > > Establish the Apache Hop 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 platform for data orchestration.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Hop Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Hop Project be and hereby is responsible for
> > > the creation and maintenance of software related to A platform for data
> >
> > s/A/a/ ?
> >
> > &

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

On Fri, 26 Nov 2021 at 07:15, Bart Maertens  wrote:
>
> Hi All,
>
> After a discussion[1] with and vote by[2] the Hop community, we believe
> Apache Hop (Incubating) is ready
> to graduate as a TLP, and we'd like to bring it up in discussion with the
> IPMC.
>
> The Hop community achievements since Hop joined the Incubator in September
> 2020:
> - close to 3200 commits by 28 contributors
> - 4 releases(0.60, 0.70, 0.99, 1.0)

However, it looks like none of these releases was ever announced.

I could not find announce emails on:
general@incubator.a.o
*@hop.a.o
announce@apache.o

Announcements are an important part of releases, so I would expect to
find some examples.

> - 5 mentors, 6 PPMC members(mentors excluded) and 8 committers(mentors and
> PPMC members excluded)
> - diverse committers and PPMC, with regular contributions from at least 5
> different companies/institutes
> - Apache Hop website[3]
> - dev conversations at d...@hop.apache.org
> - assessed ourselves against the Apache Project maturity matrix[4] and
> didn't find any issues.
>
> The topics that were discussed in the earlier [DISCUSS] thread[5] have been
> resolved:
> - old releases have been cleaned up
> - self-assessment is available[4]
> - Whimsy licensing issue is WiP (licensing is ok, the missing yaml file was
> added)
> - project description in the resolution was rewritten
> - an old pre-incubator website was removed[6]
>
> [1]
> https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
> [2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
> [3] https://hop.incubator.apache.org/
> [4] https://hop.apache.org/community/incubator/
> [5] https://lists.apache.org/thread/jj46blkwrhf0l31srtzo5j5dcv7zsqz3
> [6] http://52.214.20.244
>
> Please see the proposed board resolution below and let us know what you
> think.
>
> The discussion will remain open for at least 72 hours.
>
> --
>
> Establish the Apache Hop 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 platform for data orchestration.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Hop Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Hop Project be and hereby is responsible for
> the creation and maintenance of software related to A platform for data

s/A/a/ ?

> orchestration.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Hop 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 Hop Project:
>
> * Bart Maertens 
> * Brandon Jackson 
> * Dave Campen 
> * Francois Papon 
> * Hans Van Akelyen 
> * Julian Hyde 
> * Kevin Ratnasekera 
> * Matt Casters 
> * Nicolas Adment 
> * Ricardo Gouvea 

Only apache.org addresses are normally allowed here.

> * Sergio Ramazzina 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
> appointed to the office of Vice President, Apache Hop, 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 Hop Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Hop podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Hop podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

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

Re: [VOTE] Apache AGE (incubating) Release 0.6.0

[sebb]

On Thu, 25 Nov 2021 at 00:50, Josh Innis  wrote:
>
> Hi Sebb,
>
> Thank you for reminding us. After reading the threads for Kyuubi and
> ShenYu. It appears they decided to move the KEYS file after the voting
> process is successful.

The problem here is that people who download the release will use the
KEYS at [1]
So the VOTE also needs to use the same URL.
Also the URL [2] is not permanent.

Separately, there is no need to move the KEYS file.
It should be maintained only in the dist/release in which case it will
also be present at [1]

> Kyuubi
> https://lists.apache.org/thread/o5r9wb2dynprp5dfyhrmsjy3qcg3rfbn
> ShenYu
> https://lists.apache.org/thread/rxof3mxofgmd4fcc4wq4hbmmos78b4ko
>
> For now, the KEYS is temporarily saved in [2] for the vote process.
> When the VOTE is successful, we will move the KEYS file to the release
> directory [3] and then automatically sync it to [1] .
> You can find the right link in the download page [4] .
>
>
> [1] https://downloads.apache.org/incubator/age/KEYS
> [2] https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> [3] https://dist.apache.org/repos/dist/release/incubator/age/
> [4] https://age.apache.org/#
>
>
>
> On Wed, Nov 24, 2021 at 4:29 PM sebb  wrote:
>
> > On Wed, 24 Nov 2021 at 22:53, Josh Innis  wrote:
> > >
> > > Dear Apache Community,
> > >
> > > This is a call for releasing Apache AGE (Incubating) 0.6.0.
> > >
> > > The community vote thread can be found here:
> > https://lists.apache.org/thread/d98jsr73jydh1grkbl4160569jyjh9s8
> > >
> > > The results of the community vote can be found here:
> > https://lists.apache.org/thread/6dspyw70hp4553fwrdcv90vj7p60m0hw
> > >
> > > To learn more about Apache AGE (Incubating), please see
> > http://age.apache.org/
> > >
> > > *
> > > Apache AGE (incubating) community has voted and approved the release.
> > >
> > > This vote passed with 8 +1 votes (3 bindings and 5 non bindings) and no
> > 0 or -1 votes.
> > >
> > > +3 (Bindings)
> > > --
> > > * Juan Pan
> > > * Kevin Ratnasekera
> > > * Felix Cheung
> > >
> > > *
> > > The git tag to be discussed and voted upon:
> > > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> > >
> > > The git commit hash:
> > > commit 9786fc32d52c577cf67e9e89409246b9e7a3a063
> > >
> > > The release files for 0.6.0, can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> > >
> > > The signatures, files, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/age/
> > >
> > > Signatures used for AGE RCs can be found in this file:
> > > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> > Please do NOT use the above URL for referencing the keys file.
> > See several recent threads about this.
> >
> > > The fingerprint of key to sign release artifices:
> > > 4D57 8595 934A 64F4 8DD9 B39C 7FAD 0CDD C278 09E8
> > >
> > > For information about the contents of this release, see:
> > > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> > >
> > > The vote will be open for 72 hours.
> > > [ ] +1 release this package
> > > [ ] +0 no opinion
> > > [ ] -1 do not release this package because...
> > >
> > > Thank you for all your time,
> > > Josh Innis
> > >
> > > -
> > > 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] Apache AGE (incubating) Release 0.6.0

[sebb]

On Wed, 24 Nov 2021 at 22:53, Josh Innis  wrote:
>
> Dear Apache Community,
>
> This is a call for releasing Apache AGE (Incubating) 0.6.0.
>
> The community vote thread can be found here: 
> https://lists.apache.org/thread/d98jsr73jydh1grkbl4160569jyjh9s8
>
> The results of the community vote can be found here: 
> https://lists.apache.org/thread/6dspyw70hp4553fwrdcv90vj7p60m0hw
>
> To learn more about Apache AGE (Incubating), please see http://age.apache.org/
>
> *
> Apache AGE (incubating) community has voted and approved the release.
>
> This vote passed with 8 +1 votes (3 bindings and 5 non bindings) and no 0 or 
> -1 votes.
>
> +3 (Bindings)
> --
> * Juan Pan
> * Kevin Ratnasekera
> * Felix Cheung
>
> *
> The git tag to be discussed and voted upon:
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
> The git commit hash:
> commit 9786fc32d52c577cf67e9e89409246b9e7a3a063
>
> The release files for 0.6.0, can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
>
> The signatures, files, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/
>
> Signatures used for AGE RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS

Please do NOT use the above URL for referencing the keys file.
See several recent threads about this.

> The fingerprint of key to sign release artifices:
> 4D57 8595 934A 64F4 8DD9 B39C 7FAD 0CDD C278 09E8
>
> For information about the contents of this release, see:
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
> The vote will be open for 72 hours.
> [ ] +1 release this package
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
> Thank you for all your time,
> Josh Innis
>
> -
> 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 Sedona 1.1.1-incubating-rc1

[sebb]

On Tue, 23 Nov 2021 at 07:09, Jia Yu  wrote:
>
> Hi Justin,
>
> 1. Sorry for the confusion on the download page. I just fixed Sedona's
> website. Now the download page is at an obvious place:
> https://sedona.apache.org/download/

Looks good.

However the hash and sig display names are a bit unusual: normally
these are denoted by just 'sha512' or 'asc' rather than 'src.sha512'
and 'src.asc'.

Personally, I think it would be clearer to drop the 'src.' and 'bin.' prefix.



> 2. The reason why we put 2015 - 2021 in the NOTICE is because our project
> open-sourced in 2015 and joined the incubator in 2020. Do you think I
> should change it to 2020 - 2021?
>
> Since your -1 binding vote is mainly about the website and NOTICE instead
> of source code, do you think I should restart the voting process with a new
> release candidate RC2?
>
> Thanks,
> Jia
>
>
> On Sun, Nov 21, 2021 at 4:02 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > I’m -1 (binding) on this release as the project website doesn’t have an
> > obvious download page and they have made previous releases. This has been
> > brought up on this list before and there was no response from the project.
> >
> > For this release:
> > - incubating in name
> > - signatures and hashes are fine
> > - disclaimer exists
> > - LICENSE and NOTICE look OK but I didn’t do a detailed check
> > - The year in NOTICE looks incorrect as Sedona only started in the
> > incubator in 2020?
> > - ASF files have headers
> > - No unexpected binary files
> > - Can compile from source
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > 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

[ALL] links to KEYS file in VOTE threads and download pages

[sebb]

It is vital that the KEYS file is only referred to using a URL of the form

https://downloads.apache.org/incubator//KEYS [1]

This applies to VOTE emails as well as download pages.

Why is this?

KEYS files must remain available long for as long as a release is
still available from the ASF archives.

It is also important for the files used in a VOTE to correspond as far
as possible with the ones that will be used by downloaders.
(Obviously, that is not possible for the artifacts themselves as they
cannot be published until after the vote). Furthermore, it is
important that the KEYS file remain available after the vote has
completed, in case there is a need to check any aspects of the vote.

==

If your podling uses a template to create the vote email, please check
that it uses the correct URL for the KEYS file, and fix it if not.
Also check any developer docs to ensure the correct URL is used.

Note: for a podling's first release, it is possible that the relevant
directory under https://dist.apache.org/repos/dist/release/incubator/
has yet to be created. This will need to be created, and the KEYS file
populated, *before* the vote can begin. [It will be needed anyway once
the vote succeeds]

Thanks,
Sebb
[1] Some older pages may use
https://www.apache.org/dist/incubator//KEYS
This now redirects to https://downloads.apache.org/incubator//KEYS

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

Re: [VOTE] Release Apache Doris 0.15.0-incubating-rc04

[sebb]

On Mon, 22 Nov 2021 at 09:25, 陈明雨  wrote:
>
> Hi all,
>
>
>
>
> Please review and vote on Apache Doris 0.15.0-incubating-rc04 release.
>
>
>
>
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting 
> and analysis. The official website is:
> http://doris.incubator.apache.org/
>
>
>
>
> The Apache Doris community has voted on and approved this release:
>
> https://lists.apache.org/thread.html/d70f7c8a8ae448bf6680a15914646005c6483564464cfa15f4ddc2fc@%3Cdev.doris.apache.org%3E
>
>
>
>
> The vote result email thread:
>
> https://lists.apache.org/thread/lhnp6fnfddzc44hm1wmo2x5sqpp2by4k
>
>
>
>
> The release candidate has been tagged in GitHub as 0.15.0-rc04, available 
> here:
>
> https://github.com/apache/incubator-doris/tree/0.15.0-rc04
>
>
>
>
> Thanks to everyone who has contributed to this release, and the CHANGE LOG 
> can be found here:
>
> https://github.com/apache/incubator-doris/issues/6806
>
>
>
>
> The artifacts (source, signature and checksum) corresponding to this release 
> candidate can be found here:
>
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.15/0.15.0-rc04/
>
>
>
>
> This has been signed with PGP key 7C392A1E9C66C9CCCF388618F10626E3624583CB, 
> corresponding to chenmin...@apache.org.
>
> KEYS file is available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS

Please ONLY use downloads for KEYS, i.e.

https://downloads.apache.org/incubator/doris/KEYS

See recent Shenyu and Kyuubi threads for reasons why.

> It is also listed here:
>
> https://people.apache.org/keys/committer/morningman.asc

That is also not suitable as a link, as it may disappear at any time.
Only download KEYS are suitable.

>
>
>
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Approve the release
>
> [ ] +0 No opinion
>
> [ ] -1 Do not release this package because ...
>
>
>
>
> To verify and build, you can refer to following instruction:
>
>
>
>
> Firstly, you must be install and start docker service, and then you could 
> build Doris as following steps:
>
>
>
>
> Step1: Pull the docker image with Doris building environment
>
> $ docker pull apache/incubator-doris:build-env-1.4.1
>
> You can check it by listing images, its size is about 3.28GB.
>
>
>
>
> Step2: Run the Docker image
>
> You can run image directly:
>
> $ docker run -it apache/incubator-doris:build-env-1.4.1
>
>
>
>
> Step3: Download Doris source
>
> Now you should in docker environment, and you can download Doris source 
> package.
>
> (If you have downloaded source and it is not in image, you can map its path 
> to image in Step2.)
>
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.15/0.15.0-rc04/apache-doris-0.15.0.rc04-incubating-src.tar.gz
>
>
>
>
> Step4: Build Doris
>
> Now you can decompress and enter Doris source path and build Doris.
>
> $ tar zxvf apache-doris-0.15.0.rc04-incubating-src.tar.gz
>
> $ cd apache-doris-0.15.0.rc04-incubating-src
>
> $ sh build.sh
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@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 Sedona 1.1.1-incubating-rc1

[sebb]

On Sat, 20 Nov 2021 at 03:14, Jia Yu  wrote:
>
> Thank you Sebb. I will fix the KEY link on our website!

Actually, I was referring to the way the KEYS link is referred to in
VOTE emails etc, though of course it is important to use the correct
one on the website as well.

> On Thu, Nov 18, 2021 at 1:19 PM sebb  wrote:
>
> > On Thu, 18 Nov 2021 at 18:12, Jia Yu  wrote:
> > >
> > > Hi all, This is a call for vote on Apache Sedona 1.1.1-incubating-rc1.
> > > Please refer to the changes listed at the bottom of this email.
> > > Sedona Community Vote Result Thread:
> > > https://lists.apache.org/thread/fqhvwlgflgytlv0czoomb2nqn9n81scw
> > > Release notes:
> > >
> > https://github.com/apache/incubator-sedona/blob/sedona-1.1.1-incubating-rc1/docs/download/release-notes.md
> > > Build instructions:
> > >
> > https://github.com/apache/incubator-sedona/blob/sedona-1.1.1-incubating-rc1/docs/download/compile.md
> > > GitHub tag:
> > >
> > https://github.com/apache/incubator-sedona/releases/tag/sedona-1.1.1-incubating-rc1
> > > GPG public key to verify the Release:
> > > https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS Source code
> >
> > Please see the recent Shenyu and Kyuubi release vote threads for why
> > the KEYS file should be referenced from the public download location
> > instead:
> >
> > https://downloads.apache.org/incubator/sedona/KEYS
> >
> > > and binaries:
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/sedona/1.1.1-incubating-rc1/
> > > The vote will be open for at least 72 hours or until a majority of at
> > least
> > > 3 "approve" PMC votes are cast Please vote accordingly: [ ] +1 approve [
> > ]
> > > +0 no opinion [ ] -1 disapprove with the reason Checklist for reference
> > > (because of DISCLAIMER-WIP, other checklist items are not blockers): [ ]
> > > Download links are valid. [ ] Checksums and PGP signatures are valid. [ ]
> > > DISCLAIMER is included. [ ] Source code artifacts have correct names
> > > matching the current release. For a detailed checklist please refer to:
> > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > > Thanks,
> > > Jia Yu
> >
> > -
> > 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 Sedona 1.1.1-incubating-rc1

[sebb]

On Thu, 18 Nov 2021 at 18:12, Jia Yu  wrote:
>
> Hi all, This is a call for vote on Apache Sedona 1.1.1-incubating-rc1.
> Please refer to the changes listed at the bottom of this email.
> Sedona Community Vote Result Thread:
> https://lists.apache.org/thread/fqhvwlgflgytlv0czoomb2nqn9n81scw
> Release notes:
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.1-incubating-rc1/docs/download/release-notes.md
> Build instructions:
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.1-incubating-rc1/docs/download/compile.md
> GitHub tag:
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.1.1-incubating-rc1
> GPG public key to verify the Release:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS Source code

Please see the recent Shenyu and Kyuubi release vote threads for why
the KEYS file should be referenced from the public download location
instead:

https://downloads.apache.org/incubator/sedona/KEYS

> and binaries:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.1.1-incubating-rc1/
> The vote will be open for at least 72 hours or until a majority of at least
> 3 "approve" PMC votes are cast Please vote accordingly: [ ] +1 approve [ ]
> +0 no opinion [ ] -1 disapprove with the reason Checklist for reference
> (because of DISCLAIMER-WIP, other checklist items are not blockers): [ ]
> Download links are valid. [ ] Checksums and PGP signatures are valid. [ ]
> DISCLAIMER is included. [ ] Source code artifacts have correct names
> matching the current release. For a detailed checklist please refer to:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> Thanks,
> Jia Yu

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

Re: [VOTE] Release Apache Pegasus (Incubating) 2.3.0-RC2

[sebb]

On Tue, 16 Nov 2021 at 02:28, Yuchen He  wrote:
>
> Hi, all
>
> This is a call for a vote to release Apache Pegasus (Incubating) version
> 2.3.0-RC2.
>
> Pegasus is a distributed key-value storage system that is designed to be
> simple, horizontally scalable, strongly consistent, and high-performance.
>
> The Apache Pegasus community has voted on and approved a proposal to
> release Apache Pegasus 2.3.0-RC2.
> Apache Pegasus community vote thread:
> https://lists.apache.org/thread/jg4pmklx28xm9qm2sz8vv8lv8oo5omyo
> Result thread:
> https://lists.apache.org/thread/12voclmk4q5z6h5tm7bbmywd5rdl7pd8
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.3.0-RC2
>
> It is tagged in Git as v2.3.0-RC2 and the corresponding hash is the
> following:
> https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=2b0c6c7e4683f0d40e6a9d53ec065398b12cc69a
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/KEYS

Please see the recent Shenyu and Kyuubi release vote threads for why
the KEYS file should be referenced from the public download location
instead:

https://downloads.apache.org/incubator/pegasus/KEYS

> For information about the contents of this release, see:
> https://docs.google.com/document/d/1fzNi-aZ0b4VSvUYmXYl--JfaAYyfSm8OO24jE_JvqBw
>
> As the DISCLAIMER-WIP shows, this release still left some license problems,
> which will be gradually resolved during incubation.
>
> The vote will be open for 72 hours.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Expecting your votes.
> Thanks,
> Yuchen He

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

Re: [VOTE] Release Apache InLong(Incubating) 0.11.0-incubating Candidate 0

[sebb]

On Mon, 1 Nov 2021 at 07:08, Aloys Zhang  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache InLong(Incubating) version
> 0.11.0-incubating candidate 0.
>
> The Apache InLong community has voted on and approved a proposal to release
> Apache InLong(Incubating) version 0.11.0-incubating candidate 0  with 5 +1
> votes (3 bindings and 2 non bindings) and no 0 or -1 votes.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> InLong community vote thread:
> •
> https://lists.apache.org/thread.html/re3b12cc7ee1b831069ecc2e14c67aa5ed3b22fb659f493eee4cf910f%40%3Cdev.inlong.apache.org%3E
>
> Vote result thread:
> •
> https://lists.apache.org/thread.html/r94b5362b44d7020316b30917f21a2fe16a8a6f0d6fd668c87a257c9a%40%3Cdev.inlong.apache.org%3E
>
> The release candidate:
> •
> https://dist.apache.org/repos/dist/dev/incubator/inlong/0.11.0-incubating-RC0/
>
> Git tag for the release:
> •
> https://github.com/apache/incubator-inlong/releases/tag/0.11.0-incubating-RC0
>
> Release notes:
> • https://github.com/apache/incubator-inlong/blob/master/CHANGES.md
>
> The artifacts signed with PGP key A4D4D578 which can be found in keys file:
> • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS

Please only use the official KEYS URL, i.e.

https://downloads.apache.org/incubator/inlong/KEYS

For rationale, see the recent Kyuubi and ShenYu Release threads.

>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> On behalf of Apache InLong(Incubating) community

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

Re: [ANNOUNCE] Apache ShenYu (incubating) 2.4.1 available

[sebb]

On Mon, 25 Oct 2021 at 04:36, XiaoYu  wrote:

> Hi,
>
> Apache ShenYu (incubating) Team is glad to announce the new release of
> Apache ShenYu (incubating) 2.4.1.
>
> Apache ShenYu (incubating) is an asynchronous, high-performance,
> cross-language, responsive API gateway.
> Support various languages (http protocol), support Dubbo, Spring-Cloud,
> Grpc, Motan, Sofa, Tars and other protocols.
> Plugin design idea, plugin hot swap, easy to expand.
> Flexible flow filtering to meet various flow control.
> Built-in rich plugin support, authentication, limiting, fuse, firewall,
> etc.
> Dynamic flow configuration, high performance.
> Support cluster deployment, A/B Test, blue-green release.
>
> Download Links: https://shenyu.apache.org/download/
>
>
Looks like this page needs Javascript for the Download button to work.

Is that really necessary?

Makes it difficult to automate checking links, and may confuse some
assistive readers.

JavaScript should only be used to enhance a page (e.g. the Copy buttons are
fine), not to provide essential content.

At the very least the page should warn users without Javascript that it is
required.


> Release Notes:
> https://github.com/apache/incubator-shenyu/blob/master/RELEASE-NOTES.md
>
> Website: https://shenyu.apache.org/
>
> ShenYu Resources:
> - Issue: https://github.com/apache/incubator-shenyu/issues
> - Mailing list: d...@shenyu.apache.org
> - Documents: https://shenyu.apache.org/docs/index
>
>
> - Apache ShenYu (incubating) Team
>
> --
>
> DISCLAIMER
>
> Apache ShenYu (incubating) is an effort undergoing incubation at The Apache
> Software Foundation (ASF), sponsored by the Apache Incubator PMC.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure,
> communications, and decision making process have stabilized in a manner
> consistent with other successful ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code,
> it does indicate that the project has yet to be fully endorsed by the ASF.
>

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0

[sebb]

On Sat, 23 Oct 2021 at 16:20, bertty contreras
 wrote:
>
> Hi Sebb,
>
> The directory was created :D
>
> The KEYS file got updated at [1] and synced on [2]. From now we will use
> just the canonical link [2] for the KEYS file

Excellent!
That was quick.

Remember that the same file is used for archived releases, so an entry
should never be removed
if it has been used to sign a release

> Best regards,
> Bertty
>
> [1]https://dist.apache.org/repos/dist/release/incubator/wayang
> [2]http://downloads.apache.org/incubator/wayang/KEYS
>
> El sáb, 23 oct 2021 a las 16:58, sebb () escribió:
>
> > On Sat, 23 Oct 2021 at 12:52, Bertty Contreras 
> > wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > The Apache Wayang community has voted on and approved a proposal to
> > release
> > > Apache Wayang(Incubating) version v0.6.0-RC4.
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Wayang community vote thread:
> > > https://www.mail-archive.com/dev@wayang.apache.org/msg00446.html
> > >
> > > Vote result thread:
> > > https://www.mail-archive.com/dev@wayang.apache.org/msg00458.html
> > >
> > > [ ] +1 Release this package as Apache Wayang v0.6.0
> > > [ ] +0
> > > [ ] -1 Do not release this package because ...
> > >
> > > To learn more about Apache Wayang (Incubating), please see
> > > https://wayang.apache.org/
> > >
> > > Release notes:
> > > https://github.com/apache/incubator-wayang/blob/rel/0.6.0/RELEASE_NOTES
> > >
> > > The tag to be voted on is wayang-0.6.0 (commit 9fe19a1):
> > > https://github.com/apache/incubator-wayang/tree/rel/0.6.0
> > >
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/wayang/0.6.0/rc4
> > >
> > > Signatures used for Wayang RC's can be found in this file:
> > > https://dist.apache.org/repos/dist/dev/incubator/wayang/KEYS
> >
> > In future, please always link the KEYS file from
> > http://downloads.apache.org/incubator/wayang/KEYS
> > For reasons, please see the recent Kyuubi and Shenyu votes.
> >
> > In your case, there is no dist/release directory yet.
> > This needs to be set up before a release can be made:
> >
> > https://dist.apache.org/repos/dist/release/incubator/wayang
> >
> > Ask one of your mentors to get this done.
> >
> > > The staging repository for this release can be found at:
> > >
> > https://repository.apache.org/content/repositories/orgapachewayang-1005/org/apache/wayang
> > >
> > > Build instructions:
> > >
> > https://github.com/apache/incubator-wayang/blob/rel/0.6.0/README.md#how-to-use-wayang
> > >
> > > Thanks,
> > > Bertty Contreras Rojas
> >
> > -
> > 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 Wayang (Incubating) 0.6.0

[sebb]

On Sat, 23 Oct 2021 at 12:52, Bertty Contreras  wrote:
>
> Hello Incubator Community,
>
> The Apache Wayang community has voted on and approved a proposal to release
> Apache Wayang(Incubating) version v0.6.0-RC4.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Wayang community vote thread:
> https://www.mail-archive.com/dev@wayang.apache.org/msg00446.html
>
> Vote result thread:
> https://www.mail-archive.com/dev@wayang.apache.org/msg00458.html
>
> [ ] +1 Release this package as Apache Wayang v0.6.0
> [ ] +0
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Wayang (Incubating), please see
> https://wayang.apache.org/
>
> Release notes:
> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/RELEASE_NOTES
>
> The tag to be voted on is wayang-0.6.0 (commit 9fe19a1):
> https://github.com/apache/incubator-wayang/tree/rel/0.6.0
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.6.0/rc4
>
> Signatures used for Wayang RC's can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/wayang/KEYS

In future, please always link the KEYS file from
http://downloads.apache.org/incubator/wayang/KEYS
For reasons, please see the recent Kyuubi and Shenyu votes.

In your case, there is no dist/release directory yet.
This needs to be set up before a release can be made:

https://dist.apache.org/repos/dist/release/incubator/wayang

Ask one of your mentors to get this done.

> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachewayang-1005/org/apache/wayang
>
> Build instructions:
> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/README.md#how-to-use-wayang
>
> Thanks,
> Bertty Contreras Rojas

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

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

[sebb]

On Sat, 23 Oct 2021 at 02:00, Josh Innis  wrote:
>
> Dear Apache Community,
>
> This is a call for releasing Apache AGE (Incubating) 0.6.0.
> To learn more about Apache AGE (Incubating), please see http://age.apache.org/
>
> *
> Apache AGE (incubating) community has voted and approved the release.
> This vote passed with 7 +1 votes (2 bindings and 5 non bindings) and no 0 or 
> -1 votes.
>
> +2 (Bindings)
> --
> * Juan Pan
> * Kevin Ratnasekera
>
> *
> *The git tag to be discussed and voted upon:*
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
> *The git commit hash:*
> commit 3681c90da68353507001db89eb429755d34857f7
>
> *The release files for 0.6.0, can be found at:*
> https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
>
> *The signatures, files, etc. can be found at:*
> https://dist.apache.org/repos/dist/dev/incubator/age/
>
> *Signatures used for AGE RCs can be found in this file:*
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS

Please see the recent Shenyu and Kyuubi release vote threads for why
the KEYS file should be referenced from the public download location
instead:

https://downloads.apache.org/incubator/age/KEYS

> *The fingerprint of key to sign release artifacts:*
> 2245 1CFA 0521 1612 A4EA 9F05 6EF7 BD28 B870 8B05
>
> *For information about the contents of this release, see:*
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
>
> Vote thread can be found here [1].
>
> [1]https://lists.apache.org/thread.html/r7152a52ca973bc72282ff9a1591e49ec1662e69914aa2c9784c256a6%40%3Cdev.age.apache.org%3E
>
> The vote will be open for 72 hours.
> [ ] +1 release this package
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
> Thank you for all your time.
>
> Best regards,
> Josh Innis
>
> -
> 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 Kyuubi(Incubating) v1.3.1-incubating RC0

[sebb]

On Tue, 19 Oct 2021 at 08:49, XiDuo You  wrote:
>
> Hello Incubator Community,
>
> The Apache Kyuubi community has voted on and approved a proposal to release
> Apache Kyuubi(Incubating) version v1.3.1-incubating RC0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Kyuubi community vote thread:
> https://www.mail-archive.com/dev@kyuubi.apache.org/msg01139.html
>
> Kyuubi community vote result thread:
> https://www.mail-archive.com/dev@kyuubi.apache.org/msg01156.html
>
> [ ] +1 Release this package as Apache Kyuubi v1.3.0-incubating
> [ ] +0
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Kyuubi (Incubating), please see
> https://kyuubi.apache.org/
>
> The tag to be voted on is v1.3.1-incubating-rc0 (commit ff9bab6):
> https://github.com/apache/incubator-kyuubi/tree/v1.3.1-incubating-rc0
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.3.1-incubating-rc0/
>
> Signatures used for Kyuubi RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS

Please see comments on Shenyu release vote regarding the location of
the KEYS file

https://lists.apache.org/thread.html/rb2c64e0e640db116747c84a0a69457bc5ab9e8fb7130030e17e1a175%40%3Cgeneral.incubator.apache.org%3E

> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachekyuubi-1012/
>
> The commit list since the RC0:
> https://github.com/apache/incubator-kyuubi/compare/v1.3.0-incubating...v1.3.1-incubating-rc0
>
> Thanks,
> Xiduo You

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

Re: [VOTE] Release Apache ShenYu (incubating) 2.4.1

[sebb]

On Thu, 21 Oct 2021 at 06:10, Zhang Yonglun  wrote:
>
> Hi Sebb,
>
> Thanks for the kind reminder.
>
> > It would be better to link to the canonical KEYS file at:
> > https://downloads.apache.org/incubator/shenyu/KEYS
> > as that is what downloaders need to use.
>
> I agree with you. It's true that the downloaders need to use the canonical
> KEYS from [1].
> For now, the KEKS is temporarily saved in [2] for the vote process.

Why? You are not voting on the KEYS.

> When the VOTE is successful, we will move the KEYS file to the release
> directory [3] and then automatically sync it to [1] .
> You can find the right link in the download page [4] .

Note that the KEYS file must contain the keys for ALL historic
releases, so it can be used to validate archived versions.
So keys should only be added to the file, never removed (except
perhaps if a key was revoked).

This is probably easier to do if the KEYS file is maintained under the
dist/release directory, and not present under dist/dev

>
> [1] https://downloads.apache.org/incubator/shenyu/KEYS
> [2] https://dist.apache.org/repos/dist/dev/incubator/shenyu/KEYS
> [3] https://dist.apache.org/repos/dist/release/incubator/shenyu/
> [4] https://shenyu.apache.org/download/
>
>
> --
>
> Zhang Yonglun
> Apache ShenYu (Incubating)
> Apache ShardingSphere
>
>
> sebb  于2021年10月20日周三 下午8:54写道：
>
> > On Wed, 20 Oct 2021 at 12:46, XiaoYu  wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > This is a call for vote to release Apache ShenYu (incubating) version
> > 2.4.1
> > >
> > > The Apache ShenYu community has voted on and approved a proposal to
> > release
> > > Apache ShenYu (incubating) version 2.4.1.
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > ShenYu community vote thread:
> > >
> > https://lists.apache.org/thread.html/rfd9fae5be635f8c3f6307400040542f39585dadc7920a02f6c97c0ee%40%3Cdev.shenyu.apache.org%3E
> > >
> > > Vote result thread:
> > >
> > https://lists.apache.org/thread.html/r088e47f7d25d8c05725b42b77cc569d3145a6a73b3eb80072c4ab431%40%3Cdev.shenyu.apache.org%3E
> > >
> > > Release notes:
> > > https://github.com/apache/incubator-shenyu/blob/master/RELEASE-NOTES.md
> > >
> > > The release candidates:
> > > https://dist.apache.org/repos/dist/dev/incubator/shenyu/2.4.1/
> > >
> > > Maven 2 staging repository:
> > >
> > https://repository.apache.org/content/repositories/orgapacheshenyu-1014/org/apache/shenyu/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-shenyu/tree/v2.4.1/
> > >
> > > Release Commit ID:
> > >
> > https://github.com/apache/incubator-shenyu/commit/3c6e3a0a3134e59dc200cd68c85576d5bafc2f3b
> > >
> > > Keys to verify the Release Candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/shenyu/KEYS
> >
> > It would be better to link to the canonical KEYS file at:
> > https://downloads.apache.org/incubator/shenyu/KEYS
> > as that is what downloaders need to use.
> >
> > >
> > > Look at here for how to verify this release candidate:
> > > https://shenyu.apache.org/community/release-guide/#check-release
> > >
> > > GPG user ID:
> > > xiaoyu
> > >
> > > The vote will be open for at least 72 hours or until the necessary number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > >
> > > [ ] Checksums and PGP signatures are valid.
> > >
> > > [ ] Source code distributions have correct names matching the current
> > > release.
> > >
> > > [ ] LICENSE and NOTICE files are correct for each ShenYu repo.
> > >
> > > [ ] All files have license headers if necessary.
> > >
> > > [ ] No compiled archives bundled in source archive.
> >
> > -
> > 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 ShenYu (incubating) 2.4.1

[sebb]

On Wed, 20 Oct 2021 at 12:46, XiaoYu  wrote:
>
> Hello Incubator Community,
>
> This is a call for vote to release Apache ShenYu (incubating) version 2.4.1
>
> The Apache ShenYu community has voted on and approved a proposal to release
> Apache ShenYu (incubating) version 2.4.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> ShenYu community vote thread:
> https://lists.apache.org/thread.html/rfd9fae5be635f8c3f6307400040542f39585dadc7920a02f6c97c0ee%40%3Cdev.shenyu.apache.org%3E
>
> Vote result thread:
> https://lists.apache.org/thread.html/r088e47f7d25d8c05725b42b77cc569d3145a6a73b3eb80072c4ab431%40%3Cdev.shenyu.apache.org%3E
>
> Release notes:
> https://github.com/apache/incubator-shenyu/blob/master/RELEASE-NOTES.md
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/shenyu/2.4.1/
>
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheshenyu-1014/org/apache/shenyu/
>
> Git tag for the release:
> https://github.com/apache/incubator-shenyu/tree/v2.4.1/
>
> Release Commit ID:
> https://github.com/apache/incubator-shenyu/commit/3c6e3a0a3134e59dc200cd68c85576d5bafc2f3b
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/shenyu/KEYS

It would be better to link to the canonical KEYS file at:
https://downloads.apache.org/incubator/shenyu/KEYS
as that is what downloaders need to use.

>
> Look at here for how to verify this release candidate:
> https://shenyu.apache.org/community/release-guide/#check-release
>
> GPG user ID:
> xiaoyu
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] Source code distributions have correct names matching the current
> release.
>
> [ ] LICENSE and NOTICE files are correct for each ShenYu repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives bundled in source archive.

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

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

On Fri, 15 Oct 2021 at 12:51, sebb  wrote:

> There is a minor issue with the website:
> https://whimsy.apache.org/pods/project/hop
> Whimsy reports some Licensing issues:
> https://whimsy.apache.org/roster/ppmc/hop#podlingStatus
>
>
This is presumably caused by a missing yml file at:

https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/


> On Fri, 15 Oct 2021 at 12:44, Calvin Kirs  wrote:
>
>> Hi,
>>
>> Is there a self-assessment for Hop Graduation Maturity Assessment？ help
>> the
>> decision (of the mentors, community, Incubator PMC, and ASF Board of
>> Directors) discussion to graduate it as a top-level Apache project.
>>
>> sebb  于2021年10月15日周五 下午6:34写道：
>>
>> > The download area has several old releases; these should be removed and
>> the
>> > download page updated.
>> >
>> > https://dist.apache.org/repos/dist/release/incubator/hop/
>> >
>> > Although there are release Announce emails on the general announce@a.o
>> > list, I could not find any such announcements on the Hop dev or user
>> lists,
>> > nor on general@incubator. This seems odd.
>> >
>> >
>> > On Fri, 15 Oct 2021 at 11:02, Bart Maertens 
>> wrote:
>> >
>> > > Hi All,
>> > >
>> > > After a discussion with the community[1], we believe Apache Hop
>> > > (Incubating) is ready for graduation to a TLP, and we'd like to bring
>> it
>> > up
>> > > in discussion with the IPMC.
>> > >
>> > > The Hop community achievements since Hop joined the Incubator in
>> > September
>> > > 2020:
>> > >
>> > > - over 3000 commits by 27 contributors
>> > > - 4 releases (0.60, 0.70, 0.99, 1.0)
>> > > - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers
>> (mentors
>> > > and PPMC members excluded)
>> > > - diverse committers and PPMC, with regular contributions from at
>> least 4
>> > > different companies/institutes
>> > > - Apache Hop website[2]
>> > > - dev conversations at d...@hop.apache.org
>> > > - assessed ourselves against the Apache Project maturity matrix[3] and
>> > > didn't find any issues.
>> > >
>> > > [1]
>> > >
>> >
>> https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
>> > > [2] https://hop.incubator.apache.org/
>> > > [3]
>> > >
>> >
>> https://community.apache.org/apache-way/apache-project-maturity-model.html
>> > >
>> > > Please see the proposed board resolution below and let us know what
>> you
>> > > think.
>> > >
>> > > The discussion will remain open for at least 72 hours.
>> > >
>> > >
>> > >
>> >
>> -
>> > >
>> > > Establish the Apache Hop 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 short for the Hop Orchestration Platform. Written
>> completely
>> > > in Java it aims to provide a wide range of data orchestration tools,
>> > > including a visual development environment, servers, metadata
>> analysis,
>> > > auditing services and so on. As a platform, Hop also wants to be a
>> > > reusable library so that it can be easily reused by other software.
>> > >
>> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> > > (PMC), to be known as the "Apache Hop Project", be and hereby is
>> > > established pursuant to Bylaws of the Foundation; and be it further
>> > >
>> > > RESOLVED, that the Apache Hop Project be and hereby is responsible for
>> > > the creation and maintenance of software related to short for the Hop
>> > > Orchestration Platform. Written completely in Java it aims to provide
>> a
>> > > wide range of data orchestration tools, including a visual development
>> > > environment, servers, metadata analysis, auditing services an

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

There is a minor issue with the website:
https://whimsy.apache.org/pods/project/hop
Whimsy reports some Licensing issues:
https://whimsy.apache.org/roster/ppmc/hop#podlingStatus

On Fri, 15 Oct 2021 at 12:44, Calvin Kirs  wrote:

> Hi,
>
> Is there a self-assessment for Hop Graduation Maturity Assessment？ help the
> decision (of the mentors, community, Incubator PMC, and ASF Board of
> Directors) discussion to graduate it as a top-level Apache project.
>
> sebb  于2021年10月15日周五 下午6:34写道：
>
> > The download area has several old releases; these should be removed and
> the
> > download page updated.
> >
> > https://dist.apache.org/repos/dist/release/incubator/hop/
> >
> > Although there are release Announce emails on the general announce@a.o
> > list, I could not find any such announcements on the Hop dev or user
> lists,
> > nor on general@incubator. This seems odd.
> >
> >
> > On Fri, 15 Oct 2021 at 11:02, Bart Maertens  wrote:
> >
> > > Hi All,
> > >
> > > After a discussion with the community[1], we believe Apache Hop
> > > (Incubating) is ready for graduation to a TLP, and we'd like to bring
> it
> > up
> > > in discussion with the IPMC.
> > >
> > > The Hop community achievements since Hop joined the Incubator in
> > September
> > > 2020:
> > >
> > > - over 3000 commits by 27 contributors
> > > - 4 releases (0.60, 0.70, 0.99, 1.0)
> > > - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers
> (mentors
> > > and PPMC members excluded)
> > > - diverse committers and PPMC, with regular contributions from at
> least 4
> > > different companies/institutes
> > > - Apache Hop website[2]
> > > - dev conversations at d...@hop.apache.org
> > > - assessed ourselves against the Apache Project maturity matrix[3] and
> > > didn't find any issues.
> > >
> > > [1]
> > >
> >
> https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
> > > [2] https://hop.incubator.apache.org/
> > > [3]
> > >
> >
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> > >
> > > Please see the proposed board resolution below and let us know what you
> > > think.
> > >
> > > The discussion will remain open for at least 72 hours.
> > >
> > >
> > >
> >
> -
> > >
> > > Establish the Apache Hop 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 short for the Hop Orchestration Platform. Written completely
> > > in Java it aims to provide a wide range of data orchestration tools,
> > > including a visual development environment, servers, metadata analysis,
> > > auditing services and so on. As a platform, Hop also wants to be a
> > > reusable library so that it can be easily reused by other software.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Hop Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Hop Project be and hereby is responsible for
> > > the creation and maintenance of software related to short for the Hop
> > > Orchestration Platform. Written completely in Java it aims to provide a
> > > wide range of data orchestration tools, including a visual development
> > > environment, servers, metadata analysis, auditing services and so on.
> As
> > > a platform, Hop also wants to be a reusable library so that it can be
> > > easily reused by other software; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> > > have primary responsibility for management of the projects within the
> > > scope of responsibility of the Apache Hop Project; and be it further
> > &

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[sebb]

The download area has several old releases; these should be removed and the
download page updated.

https://dist.apache.org/repos/dist/release/incubator/hop/

Although there are release Announce emails on the general announce@a.o
list, I could not find any such announcements on the Hop dev or user lists,
nor on general@incubator. This seems odd.


On Fri, 15 Oct 2021 at 11:02, Bart Maertens  wrote:

> Hi All,
>
> After a discussion with the community[1], we believe Apache Hop
> (Incubating) is ready for graduation to a TLP, and we'd like to bring it up
> in discussion with the IPMC.
>
> The Hop community achievements since Hop joined the Incubator in September
> 2020:
>
> - over 3000 commits by 27 contributors
> - 4 releases (0.60, 0.70, 0.99, 1.0)
> - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors
> and PPMC members excluded)
> - diverse committers and PPMC, with regular contributions from at least 4
> different companies/institutes
> - Apache Hop website[2]
> - dev conversations at d...@hop.apache.org
> - assessed ourselves against the Apache Project maturity matrix[3] and
> didn't find any issues.
>
> [1]
> https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
> [2] https://hop.incubator.apache.org/
> [3]
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> Please see the proposed board resolution below and let us know what you
> think.
>
> The discussion will remain open for at least 72 hours.
>
>
> -
>
> Establish the Apache Hop 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 short for the Hop Orchestration Platform. Written completely
> in Java it aims to provide a wide range of data orchestration tools,
> including a visual development environment, servers, metadata analysis,
> auditing services and so on. As a platform, Hop also wants to be a
> reusable library so that it can be easily reused by other software.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Hop Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Hop Project be and hereby is responsible for
> the creation and maintenance of software related to short for the Hop
> Orchestration Platform. Written completely in Java it aims to provide a
> wide range of data orchestration tools, including a visual development
> environment, servers, metadata analysis, auditing services and so on. As
> a platform, Hop also wants to be a reusable library so that it can be
> easily reused by other software; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Hop 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 Hop Project:
>
>  * Bart Maertens  
>  * Brandon Jackson
>  * Francois Papon 
>  * Hans Van Akelyen   
>  * Hiromu Hota
>  * Julian Hyde
>  * Kevin Ratnasekera  
>  * Matt Casters   
>  * Maximilian Michels 
>  * Nicolas Adment 
>  * Tom Barber 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
> appointed to the office of Vice President, Apache Hop, 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 Hop Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Hop podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Hop podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Incubator disclaimer missing from several podling websites

[sebb]

On Fri, 17 Sept 2021 at 14:50, 陈明雨  wrote:
>
> Hi Sebb:
> Thanks for reminding.
>
>
> But I don't understand what is "does not work at all without JavaScript" mean?

Browse to https://doris.apachr.org/ with JavaScript disabled.

This shows a completely blank page.

Automatic language selection should not require JavaScript.
There is no reason to use JavaScript for this.
If the pages are correctly named the server will do this for you.

Pages that use JavaScript must include a noscript section that allows
browsers without it to display an alternative to the user.
But ideally JS should only be used to enhance a page, rather than
provide essential content.

AIUI assistive readers may have problems understanding JavaScript, and
automated checkers certainly do.

>
> The DISCLAIMER is at the bottom of each website pages written as:
>
>
> "Apache Doris(incubating) is an effort undergoing incubation at The Apache 
> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is 
> required of all newly accepted projects until a further review indicates that 
> the infrastructure, communications, and decision making process have 
> stabilized in a manner consistent with other successful ASF projects. While 
> incubation status is not necessarily a reflection of the completeness or 
> stability of the code, it does indicate that the project has yet to be fully 
> endorsed by the ASF."
>
>
> Did I miss something?

The disclaimer looks OK, but automated checkers won't see it as they
aren't redirected properly.

> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org
>
>
>
>
>
> At 2021-09-17 20:35:11, "sebb"  wrote:
> >As the subject says: the disclaimer is missing from the following websites:
> >
> >Age
> >BlueMarlin (no website at all)
> >Doris - does not work at all without JavaScript
> >Inlong - does not work without Javascript
> >Kyuubi
> >Liminal
> >Linkis - no website yet
> >Nemo
> >
> >Yunikorn has some incorrect text: ", sponsored by the name of Apache
> >TLP sponsor."
> >
> >Milagro looks OK in a browser, but uses a redirect that does not work
> >for automated checkers.
> >Given that the redirect is unconditional, this would be better done by
> >the server, e.g. through .htaccess.
> >
> >It should be present on all pages.
> >
> >-
> >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

Require websites to have standard download URL?

[sebb]

Many of the podling websites have a download page of the form:

https://.apache.org/download/

Given that every website must have a download page, and that the
/download/ URL can easily be redirected to an alternate page, it might
be worth considering making this URL a requirement for all podling
websites.

Sebb

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

Re: [MENTORS] Download pages and dist area (BRPC, InLong, Kyuubi, Livy, Nemo and Tuweni)

[sebb]

AFAICT there is no download page for AGE, nor any ANNOUNCE emails I could find.

Other podlings with no download pages that I could find:

Liminal
Marvin (no source download I could find)
PageSpeed
SDAP (no releases?)
Sedona
Training (it does have released items)
Wayang


On Fri, 17 Sept 2021 at 02:51, Justin Mclean  wrote:
>
> Hi,
>
> Project dist areas should be up to date with the download page. I wrote a 
> script to check some things, again this may have missed some things or it may 
> be incorrect.
>
> I can see the following minor issues for BRPC, InLong, Kyuubi, Livy, Nemo and 
> Tuweni.
>
> BRPC
> https://dist.apache.org/repos/dist/release/incubator/brpc/
> https://brpc.apache.org/download/
> Version 0.9.6 missing from download page but in dist area. Dist area needs a 
> cleanup.
>
> InLong
> https://dist.apache.org/repos/dist/release/incubator/inlong/
> https://inlong.apache.org/en-us/docs/download/download.html
> Link on download page to 
> http://www.apache.org/dyn/closer.lua/incubator/inlong/0.9.0-incubating/apache-inlong-0.9.0-incubating-src.tar.gz
>  should be an archive link instead
>
> Kyuubi
> https://dist.apache.org/repos/dist/release/incubator/kyuubi/
> https://kyuubi.apache.org/releases.html
> Download link to 1.3.0 missing and please do not link to GitHub “releases".
>
> Livy
> https://dist.apache.org/repos/dist/release/incubator/livy/
> https://livy.apache.org/download/
> Versions 0.4.0, 0.5.0, 0.6.0 and 0.7.0 missing from download page but in dist 
> area.  Dist area needs a cleanup.
>
> Nemo
> https://dist.apache.org/repos/dist/release/incubator/nemo/
> https://nemo.apache.org/pages/downloads/
> Latest release 0.3-incubating is missing from download page
> Links to 0.1 and 0.2 are broken.
>
> Tuweni
> https://dist.apache.org/repos/dist/release/incubator/tuweni/
> https://tuweni.apache.org/download
> Version 1.3.0 missing from download page but in dist area. Dist area needs a 
> cleanup.
>
> Thanks
> Justin
> -
> 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

Incubator disclaimer missing from several podling websites

[sebb]

As the subject says: the disclaimer is missing from the following websites:

Age
BlueMarlin (no website at all)
Doris - does not work at all without JavaScript
Inlong - does not work without Javascript
Kyuubi
Liminal
Linkis - no website yet
Nemo

Yunikorn has some incorrect text: ", sponsored by the name of Apache
TLP sponsor."

Milagro looks OK in a browser, but uses a redirect that does not work
for automated checkers.
Given that the redirect is unconditional, this would be better done by
the server, e.g. through .htaccess.

It should be present on all pages.

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

Re: [MENTORS] Download pages and links to podling releases

[sebb]

Looks good now, thanks for the prompt fix

On Fri, 17 Sept 2021 at 01:59, tan zhongyi  wrote:
>
> Key's link are fixed.
> Thanks
>
>
>
> 在 2021/9/17 上午8:50，“tan zhongyi” 写入:
>
> Thanks， sebb,
>
> We will fix it today.
>
> Best wishes,
> Jerry
>
> 在 2021/9/16 下午10:55，“sebb” 写入:
>
> On Thu, 16 Sept 2021 at 09:53, tan zhongyi  
> wrote:
> >
> > brpc project's download page has been updated accordingly.
> > https://brpc.apache.org/download/
>
> The updated page is much better. However there is still an issue.
>
> The KEYS file must be linked from
> https://downloads.apache.org/incubator/brpc/KEYS
>
> Please fix the KEYS link.
>
> ==
>
> Note: the dist.apache.org host is not intended for use by the general
> public; it is for staging and publication only.
>
> Furthermore the current links points to
> http://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
> i.e. the dev tree, which is intended for short-term staging only.
>
> Please maintain the canonical KEYS file at
> http://dist.apache.org/repos/dist/release/incubator/brpc/KEYS
>
> [This is then published at:
> https://downloads.apache.org/incubator/brpc/KEYS
> for use by download pages]
> > thanks
> >
> >
> > 在 2021/9/16 上午10:15，“tan zhongyi” 写入:
> >
> > Thanks for pointing out it.
> > Brpc team will fix it soon.
> >
> > Best wishes,
> > Jerry
> >
> > 在 2021/9/16 上午9:18，“Justin Mclean” 
> 写入:
> >
> > Hi,
> >
> > Can mentors please make themselves familiar with the 
> requirements for download pages and links [1] as we seem to have a number of 
> projects that are not providing downloads in the required manner.
> >
> > In general:
> > - Please use https://www.apache.org/dyn/closer.lua 
> <https://www.apache.org/dyn/closer.lua> for releases
> > - Please use https://downloads.apache.org/  for hashes and 
> signatures
> >
> >
> > Form a quick check these project don’t seem to have an 
> obvious download page:
> > Age
> > Annotator
> > BlueMarlin
> > Liminal
> > Linkis
> > Marvin
> > SDAP
> > Sedona
> > Wayang
> >
> > Now in some cases these are newish projects and they 
> haven’t made a release, however others on that list have made releases and 
> really should have a download page. If they do have a download page please 
> provide the URL.
> >
> > These projects look to have issue with the download links 
> themselves:
> > BRPC - https://brpc.apache.org/download/ 
> <https://brpc.apache.org/download/>
> > Crail - http://crail.apache.org/download/ 
> <http://crail.apache.org/download/>
> > DataLab - http://datalab.apache.org/#download 
> <http://datalab.apache.org/#download>
> > Doris - 
> http://doris.apache.org/master/en/downloads/downloads.html 
> <http://doris.apache.org/master/en/downloads/downloads.html>
> > Heron - https://heron.apache.org/download 
> <https://heron.apache.org/download>
> > Hivemall - https://hivemall.apache.org/download.html 
> <https://hivemall.apache.org/download.html>
> > Kyuubi - https://kyuubi.apache.org/releases.html 
> <https://kyuubi.apache.org/releases.html>
> > Livy - https://livy.apache.org/download/ 
> <https://livy.apache.org/download/>
> > Milagro - https://milagro.apache.org/docs/downloads/ 
> <https://milagro.apache.org/docs/downloads/>
> > Nemo - https://nemo.apache.org/pages/downloads/ 
> <https://nemo.apache.org/pages/downloads/>
> > NLPCraft - https://nlpcraft.apache.org/download.html 
> <https://nlpcraft.apache.org/download.html>
> > NuttX - https://nuttx.apache.org/download/ 
> <https://nuttx.apache.org/download/>
> > PageSpeed - https://pagespeed.apache.org/doc/download 
> <https://pagespeed.apache.org/doc/

Re: [MENTORS] Download pages and links to podling releases

[sebb]

On Thu, 16 Sept 2021 at 09:53, tan zhongyi  wrote:
>
> brpc project's download page has been updated accordingly.
> https://brpc.apache.org/download/

The updated page is much better. However there is still an issue.

The KEYS file must be linked from
https://downloads.apache.org/incubator/brpc/KEYS

Please fix the KEYS link.

==

Note: the dist.apache.org host is not intended for use by the general
public; it is for staging and publication only.

Furthermore the current links points to
http://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
i.e. the dev tree, which is intended for short-term staging only.

Please maintain the canonical KEYS file at
http://dist.apache.org/repos/dist/release/incubator/brpc/KEYS

[This is then published at:
https://downloads.apache.org/incubator/brpc/KEYS
for use by download pages]
> thanks
>
>
> 在 2021/9/16 上午10:15，“tan zhongyi” 写入:
>
> Thanks for pointing out it.
> Brpc team will fix it soon.
>
> Best wishes,
> Jerry
>
> 在 2021/9/16 上午9:18，“Justin Mclean” 写入:
>
> Hi,
>
> Can mentors please make themselves familiar with the requirements for 
> download pages and links [1] as we seem to have a number of projects that are 
> not providing downloads in the required manner.
>
> In general:
> - Please use https://www.apache.org/dyn/closer.lua 
>  for releases
> - Please use https://downloads.apache.org/  for hashes and signatures
>
>
> Form a quick check these project don’t seem to have an obvious 
> download page:
> Age
> Annotator
> BlueMarlin
> Liminal
> Linkis
> Marvin
> SDAP
> Sedona
> Wayang
>
> Now in some cases these are newish projects and they haven’t made a 
> release, however others on that list have made releases and really should 
> have a download page. If they do have a download page please provide the URL.
>
> These projects look to have issue with the download links themselves:
> BRPC - https://brpc.apache.org/download/ 
> 
> Crail - http://crail.apache.org/download/ 
> 
> DataLab - http://datalab.apache.org/#download 
> 
> Doris - http://doris.apache.org/master/en/downloads/downloads.html 
> 
> Heron - https://heron.apache.org/download 
> 
> Hivemall - https://hivemall.apache.org/download.html 
> 
> Kyuubi - https://kyuubi.apache.org/releases.html 
> 
> Livy - https://livy.apache.org/download/ 
> 
> Milagro - https://milagro.apache.org/docs/downloads/ 
> 
> Nemo - https://nemo.apache.org/pages/downloads/ 
> 
> NLPCraft - https://nlpcraft.apache.org/download.html 
> 
> NuttX - https://nuttx.apache.org/download/ 
> 
> PageSpeed - https://pagespeed.apache.org/doc/download 
> 
> PonyMail - https://ponymail.apache.org/downloads.html 
> 
> Spot - https://spot.apache.org/download/ 
> 
> Teaclave - https://teaclave.apache.org/download/ 
> 
> Training - https://training.apache.org/downloads.html 
> 
>
> This list was autogenerated by a script and may have got some things 
> wrong. If you need details on a particular project and it’s links please 
> check here. [1]
>
> Thanks,
> Justin
>
> 1. 
> https://gist.github.com/justinmclean/60a824a2f3fe97e519ed25d7c39a47ed
>
>
> 1. https://infra.apache.org/release-distribution.html#download-links
>
> -
> 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: [ANNOUNCE] Release Apache Kyuubi(Incubating) 1.3.0-incubating

[sebb]

On Wed, 15 Sept 2021 at 15:58, Cheng Pan  wrote:
>
> Hi all,
>
> The Apache Kyuubi(Incubating) community is pleased to announce
> that Apache Kyuubi(Incubating) 1.3.0-incubating has been released!
>
> Download Links:
> https://downloads.apache.org/incubator/kyuubi/kyuubi-1.3.0-incubating/

Sorry, but that is not a valid download page.
A download page must use the ASF mirror system (closer.lua) and have
links to KEYS, sigs and hashes.

Please ask your mentors for help.

The website releases page is also not valid:
https://kyuubi.apache.org/releases.html

The website is also missing the Incubator disclaimer, as is this email.

Sebb
> Release Notes: https://kyuubi.apache.org/release/1.3.0-incubating.html
>
> Website: https://kyuubi.apache.org/
>
> Kyuubi Resources:
> - Issue: https://github.com/apache/incubator-kyuubi/issues
> - Mailing list: d...@kyuubi.apache.org
>
> Thanks,
> On behalf of Apache Kyuubi(Incubating) community

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

Re: [ANNOUNCE] Release Apache brpc (incubating) 1.0.0-rc02

[sebb]

On Mon, 13 Sept 2021 at 23:56, Dave Fisher  wrote:
>
> Once podlings report their download page something like this can be 
> incorporated in clutch3 which will have svn log info from dist.

Note that there are quite a few other checks that are needed for a
compliant download page, e.g.
- no references to nightly or snapshot builds
- no reference to repository.apache.org
- all releases have sigs and hashes (and vice-versa)
- KEYS file link is present and correct
- code verification instructions are present
- no md5 or sha1 hashes
- ...

The ruby script at
https://github.com/apache/whimsy/blob/master/tools/download_check.rb
does this, as well as checking that links actually work, i.e. that
mirrors have the files.

[Sorry, but it's not very well structured at present...]

Of course neither script is likely to work if the page uses JavaScript.

> Thanks
>
> Sent from my iPhone
>
> > On Sep 13, 2021, at 3:46 PM, Justin Mclean  wrote:
> >
> > Hi,
> >
> > A while back I wrote a script to check podling download links and we 
> > attempted to get them all corrected. you need to manual list all of the 
> > download pages.
> >
> > Things it doesn’t do:
> > - check if the latest release is there
> > - check if the contents match with what is in /dist
> >
> > Might be time to run it again.
> >
> > Here’s the python code, you might find it useful.
> >
> > from bs4 import BeautifulSoup
> > import urllib.request
> > import re
> >
> > downloadPages = [
> > "https://mxnet.apache.org/get_started/download";
> > ]
> >
> > for page in downloadPages:
> >response = urllib.request.urlopen(page)
> >data = response.read()
> >soup = BeautifulSoup(data,'lxml')
> >
> >print()
> >print("Checking " + page)
> >
> >alllinks = soup('a')
> >missing = True
> >for link in alllinks:
> >if link.has_attr('href'):
> >href =  link['href']
> >text = link.contents
> >if href.endswith('.zip') or href.endswith('.tar.gz') or 
> > href.endswith('.tzg') or href.endswith('.msi') or href.endswith('.rpm'):
> >if href.startswith('http://www.apache.org/dist/') or 
> > href.startswith('https://www.apache.org/dist/'):
> >print("Please change link to" + href + " to not use 
> > http://www.apache.org/dist/ and use https://www.apache.org/dyn/closer.lua 
> > instead")
> >if href.startswith('http://downloads.apache.org/') or 
> > href.startswith('https://downloads.apache.org/'):
> >print("Please change link to" + href + " to not use 
> > http://downloads.apache.org/ and use https://www.apache.org/dyn/closer.lua 
> > instead")
> >if href.startswith('http://dist.apache.org/repos/dist/dev') 
> > or href.startswith('https://dist.apache.org/repos/dist/dev'):
> >print("Please change link to " + href + " to release 
> > area and use https://www.apache.org/dyn/closer.lua";)
> >if 
> > href.startswith('http://dist.apache.org/repos/dist/release') or 
> > href.startswith('https://dist.apache.org/repos/dist/release'):
> >print("Please use use 
> > https://www.apache.org/dyn/closer.lua to download releases")
> >if 
> > href.startswith('https://downloads.apache.org/incubator/'):
> >print("Please use use 
> > https://www.apache.org/dyn/closer.lua to download releases")
> >if href.endswith('.sha512') or href.endswith('.sha256') or 
> > href.endswith('.asc'):
> >missing = False
> >if  href.startswith('http://www.apache.org/dist/') or 
> > href.startswith('https://www.apache.org/dist/'):
> >print("Please change link to " + href + " to go via 
> > https://downloads.apache.org/. https://www.apache.org/dist/ has been 
> > deprecated.")
> >if not href.startswith('https://downloads.apache.org/') and 
> > not href.startswith('https://archive.apache.org/dist'):
> >print("Please change link to " + href + " to go via 
> > https://downloads.apache.org/ or https://archive.apache.org/dist";)
> >if href.endswith('.sha'):
> > print("for link " + href + " .sha should no longer be used. 
> > Please change ot use .sha256 or .sha512.")
> >if missing:
> >print("Links to signatures and hashes are missing”)
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > 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 additi

Re: [ANNOUNCE] Release Apache brpc (incubating) 1.0.0-rc02

[sebb]

On Mon, 13 Sept 2021 at 16:45, Dave Fisher  wrote:
>
>
>
> > On Sep 12, 2021, at 4:45 PM, sebb  wrote:
> >
> > On Sun, 12 Sept 2021 at 23:49, Dave Fisher  wrote:
> >>
> >> The status of Podlings releases can be found in the clutch analysis.
> >>
> >> Please have a look at https://incubator.apache.org/clutch/ 
> >> <https://incubator.apache.org/clutch/> and for brpc - 
> >> https://incubator.apache.org/clutch/brpc.html 
> >> <https://incubator.apache.org/clutch/brpc.html>
> >>
> >> See https://incubator.apache.org/clutch/#p_has_a_distribution_area 
> >> <https://incubator.apache.org/clutch/#p_has_a_distribution_area> and P, Q, 
> >> and R instructions
> >>
> >
> > Note that releases must have download pages: these are not covered by
> > the Clutch analysis as far as I can tell.
>
> The clutch analysis counts on Whimsy for website checks and whimsy does not 
> check for download pages. I think that it might be worth discussing on 
> dev@whimsical how to add those checks. Once available in whimsy the check can 
> be added to the clutch analysis.

The point is that Clutch can only do some checks - mentors also need
to check other aspects of the release, such as the download page and
the content of the announce email.

Whilst Whimsy has a tool to check the contents of download pages, this
requires the user to provide the correct URL.
It's not possible in general to determine the download page URL (and
there may be more than one)
Maybe the podling status file could be updated to require download URL(s)?

> Regards,
> Dave
>
> >
> >>> On Sep 12, 2021, at 2:44 PM, sebb  wrote:
> >>>
> >>> On Sun, 12 Sept 2021 at 16:09, Lorin Lee  wrote:
> >>>>
> >>>> Hi all,
> >>>>
> >>>>
> >>>>
> >>>> The Apache brpc (incubating) community is pleased to announce that Apache
> >>>>
> >>>> brpc (incubating) 1.0.0-rc02 has been released!
> >>>>
> >>>>
> >>>>
> >>>> Brief notes of this release:
> >>>>
> >>>>  - Fix a latency issue caused by event_dispatcher
> >>>>  - Fix bug that time unit is not listed in grpc timeout options
> >>>>  - Fix heap overflow in simple_data_pool
> >>>>  - Support the length of redis args could be zero
> >>>>  - Fix bug that may throw out of index in rpc_replay
> >>>>  - Fix an access-after-return issue in TimerThread
> >>>>
> >>>>
> >>>>
> >>>> More details regarding Apache brpc can be found at:
> >>>>
> >>>> http://brpc.apache.org/
> >>>>
> >>>>
> >>>>
> >>>> The release artifacts can be downloaded here:
> >>>>
> >>>> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.0.0-rc02/
> >>>>
> >>>
> >>> Please do NOT use dist.apache.org as a public download location.
> >>> It is only intended for use by project developers when staging a release.
> >>>
> >>> Furthermore, the dist/dev tree is intended for holding release candidates 
> >>> only.
> >>> Once a release vote passes, the release should be moved to the
> >>> dist/release tree.
> >>>
> >>> Something has gone seriously wrong here.
> >>>
> >>>>
> >>>> The release notes can be found here:
> >>>>
> >>>> https://github.com/apache/incubator-brpc/releases/tag/1.0.0-rc02
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Lorin Lee
> >>>>
> >>>> Apache brpc (Incubating)
> >>>
> >>> -
> >>> 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: [ANNOUNCE] Release Apache brpc (incubating) 1.0.0-rc02

[sebb]

On Mon, 13 Sept 2021 at 01:58, tan zhongyi  wrote:
>
> Hi，sebb,
>
> Thanks for helping us to clarify this.
>
> We will update our website download page to github download page, so others 
> can visit our website or github repo to download the source tarball.

Download pages must use the mirror system for source.
They should not link directly to any unreleased source, so linking to
github is not correct.

Please ask your mentors if this is not clear.

> And move the source tarball from dist/dev to dist/release.

This also needs to be done for the previous releases so they are added
to the ASF archive.

Once they have been archived, the older releases should be removed
from dist/release.
Do not remove them until they have been successfully archived.

The archives should appear here (it will take a day or two):

http://archive.apache.org/dist/incubator/brpc

> Thanks
>
>
> 在 2021/9/13 上午5:44，“sebb” 写入:
>
> On Sun, 12 Sept 2021 at 16:09, Lorin Lee  wrote:
> >
> > Hi all,
> >
> >
> >
> > The Apache brpc (incubating) community is pleased to announce that 
> Apache
> >
> > brpc (incubating) 1.0.0-rc02 has been released!
> >
> >
> >
> > Brief notes of this release:
> >
> >- Fix a latency issue caused by event_dispatcher
> >- Fix bug that time unit is not listed in grpc timeout options
> >- Fix heap overflow in simple_data_pool
> >- Support the length of redis args could be zero
> >- Fix bug that may throw out of index in rpc_replay
> >- Fix an access-after-return issue in TimerThread
> >
> >
> >
> > More details regarding Apache brpc can be found at:
> >
> > http://brpc.apache.org/
> >
> >
> >
> > The release artifacts can be downloaded here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/brpc/1.0.0-rc02/
> >
>
> Please do NOT use dist.apache.org as a public download location.
> It is only intended for use by project developers when staging a release.
>
> Furthermore, the dist/dev tree is intended for holding release candidates 
> only.
> Once a release vote passes, the release should be moved to the
> dist/release tree.
>
> Something has gone seriously wrong here.
>
> >
> > The release notes can be found here:
> >
> > https://github.com/apache/incubator-brpc/releases/tag/1.0.0-rc02
> >
> >
> >
> > Thanks,
> >
> > Lorin Lee
> >
> > Apache brpc (Incubating)
>
> -
> 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: [MENTORS] Old releases in release area

[sebb]

FTR, livy and nlpcraft need to clear up their release directories please:

https://dist.apache.org/repos/dist/release/incubator/livy/
https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/

On Mon, 3 May 2021 at 01:43, Justin Mclean  wrote:
>
> Hi,
>
> Thanks to those who all responded and cleaned up their repo areas.
>
> Still to go are:
> Crail [1]
> DataLab [2]
> Livy [3]
> Milagro [4]
> MXnet [5]
> Nemo [6]
> NLPCraft [7]
> Pinot [8]
>
> Thanks,
> Justin
>
>
> 1. https://dist.apache.org/repos/dist/release/incubator/crail/ 
> 
> 2. https://dist.apache.org/repos/dist/release/incubator/datalab/ 
> 
> 3. https://dist.apache.org/repos/dist/release/incubator/livy/ 
> 
> 4. https://dist.apache.org/repos/dist/release/incubator/milagro/ 
> 
> 5. https://dist.apache.org/repos/dist/release/incubator/mxnet/ 
> 
> 6 https://dist.apache.org/repos/dist/release/incubator/nemo/ 
> 
> 7. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/ 
> 
> 8. https://dist.apache.org/repos/dist/release/incubator/pinot/ 
> 
>

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

Re: [ANNOUNCE] Release Apache brpc (incubating) 1.0.0-rc02

[sebb]

On Sun, 12 Sept 2021 at 23:49, Dave Fisher  wrote:
>
> The status of Podlings releases can be found in the clutch analysis.
>
> Please have a look at https://incubator.apache.org/clutch/ 
> <https://incubator.apache.org/clutch/> and for brpc - 
> https://incubator.apache.org/clutch/brpc.html 
> <https://incubator.apache.org/clutch/brpc.html>
>
> See https://incubator.apache.org/clutch/#p_has_a_distribution_area 
> <https://incubator.apache.org/clutch/#p_has_a_distribution_area> and P, Q, 
> and R instructions
>

Note that releases must have download pages: these are not covered by
the Clutch analysis as far as I can tell.

> > On Sep 12, 2021, at 2:44 PM, sebb  wrote:
> >
> > On Sun, 12 Sept 2021 at 16:09, Lorin Lee  wrote:
> >>
> >> Hi all,
> >>
> >>
> >>
> >> The Apache brpc (incubating) community is pleased to announce that Apache
> >>
> >> brpc (incubating) 1.0.0-rc02 has been released!
> >>
> >>
> >>
> >> Brief notes of this release:
> >>
> >>   - Fix a latency issue caused by event_dispatcher
> >>   - Fix bug that time unit is not listed in grpc timeout options
> >>   - Fix heap overflow in simple_data_pool
> >>   - Support the length of redis args could be zero
> >>   - Fix bug that may throw out of index in rpc_replay
> >>   - Fix an access-after-return issue in TimerThread
> >>
> >>
> >>
> >> More details regarding Apache brpc can be found at:
> >>
> >> http://brpc.apache.org/
> >>
> >>
> >>
> >> The release artifacts can be downloaded here:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.0.0-rc02/
> >>
> >
> > Please do NOT use dist.apache.org as a public download location.
> > It is only intended for use by project developers when staging a release.
> >
> > Furthermore, the dist/dev tree is intended for holding release candidates 
> > only.
> > Once a release vote passes, the release should be moved to the
> > dist/release tree.
> >
> > Something has gone seriously wrong here.
> >
> >>
> >> The release notes can be found here:
> >>
> >> https://github.com/apache/incubator-brpc/releases/tag/1.0.0-rc02
> >>
> >>
> >>
> >> Thanks,
> >>
> >> Lorin Lee
> >>
> >> Apache brpc (Incubating)
> >
> > -
> > 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: [ANNOUNCE] Release Apache brpc (incubating) 1.0.0-rc02

[sebb]

On Sun, 12 Sept 2021 at 16:09, Lorin Lee  wrote:
>
> Hi all,
>
>
>
> The Apache brpc (incubating) community is pleased to announce that Apache
>
> brpc (incubating) 1.0.0-rc02 has been released!
>
>
>
> Brief notes of this release:
>
>- Fix a latency issue caused by event_dispatcher
>- Fix bug that time unit is not listed in grpc timeout options
>- Fix heap overflow in simple_data_pool
>- Support the length of redis args could be zero
>- Fix bug that may throw out of index in rpc_replay
>- Fix an access-after-return issue in TimerThread
>
>
>
> More details regarding Apache brpc can be found at:
>
> http://brpc.apache.org/
>
>
>
> The release artifacts can be downloaded here:
>
> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.0.0-rc02/
>

Please do NOT use dist.apache.org as a public download location.
It is only intended for use by project developers when staging a release.

Furthermore, the dist/dev tree is intended for holding release candidates only.
Once a release vote passes, the release should be moved to the
dist/release tree.

Something has gone seriously wrong here.

>
> The release notes can be found here:
>
> https://github.com/apache/incubator-brpc/releases/tag/1.0.0-rc02
>
>
>
> Thanks,
>
> Lorin Lee
>
> Apache brpc (Incubating)

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

Re: [ANNOUNCE] Apache Annotator (incubating) 0.2.0 release

[sebb]

https://annotator.apache.org/www.apache.org/dist/incubator/annotator/KEYS
is not a valid keys link.

Looks like someone omitted the 'https://' prefix.

Please fix.
On Sun, 5 Sept 2021 at 13:57, sebb  wrote:
>
> On Fri, 3 Sept 2021 at 13:43, Gerben  wrote:
> >
> > Dear community,
> >
> > The Apache Annotator (incubating) community is pleased to announce the
> > release of Apache Annotator (incubating) 0.2.0.
> >
> > Apache Annotator (incubating) provides libraries to enable annotation
> > related software, with an initial focus on identification of textual
> > fragments in browser environments.
> >
> > These are the main changes since v0.1.0:
> >
> > - all code is converted to TypeScript
> > - the API is documented
> > - many tests have been added
> > - npm package names changed from “@annotator/…” to “@apache-annotator/…”
> > - a meta-package was added that includes all the others in one package
> > - it now supports TextPositionSelector
> > - it now supports CssSelector in both directions (match & describe)
> > - steps were made to apply text matching algorithms to other environments 
> > than the DOM
> > - and many small fixes, tweaks and improvements
> >
> > Download links:
> > https://annotator.apache.org/
>
> The KEYS link is broken.
>
> > The release tag:
> > https://github.com/apache/incubator-annotator/releases/tag/v0.2.0
> >
> > With regards on behalf of the team,
> >
> > — Gerben
> >

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

Re: [ANNOUNCE] Apache Annotator (incubating) 0.2.0 release

[sebb]

On Fri, 3 Sept 2021 at 13:43, Gerben  wrote:
>
> Dear community,
>
> The Apache Annotator (incubating) community is pleased to announce the
> release of Apache Annotator (incubating) 0.2.0.
>
> Apache Annotator (incubating) provides libraries to enable annotation
> related software, with an initial focus on identification of textual
> fragments in browser environments.
>
> These are the main changes since v0.1.0:
>
> - all code is converted to TypeScript
> - the API is documented
> - many tests have been added
> - npm package names changed from “@annotator/…” to “@apache-annotator/…”
> - a meta-package was added that includes all the others in one package
> - it now supports TextPositionSelector
> - it now supports CssSelector in both directions (match & describe)
> - steps were made to apply text matching algorithms to other environments 
> than the DOM
> - and many small fixes, tweaks and improvements
>
> Download links:
> https://annotator.apache.org/

The KEYS link is broken.

> The release tag:
> https://github.com/apache/incubator-annotator/releases/tag/v0.2.0
>
> With regards on behalf of the team,
>
> — Gerben
>

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

Re: [ANNOUNCE] Release Apache InLong(incubating) 0.9.0-incubating

[sebb]

On Fri, 23 Jul 2021 at 15:17, Goson zhang  wrote:
>
> Hi @sebb  :
>
> I just now modified the download page and added a reminder for the Release
> Integrity check [1];

That looks find now, thanks for the prompt attention to it.

However, the Chinese version of the page has the verification
instructions in English.
It would be better if it were translated.

> at the same time, I modified the notification template
> of the version release[2]. There should be no such problems later.
>
> If we have any other questions, please let me know
>
> thanks!!
>
> 1. https://inlong.apache.org/en-us/docs/download/download.html
> 2. https://inlong.apache.org/en-us/docs/development/how-to-release.html
>
> Goson zhang  于2021年7月23日周五 下午8:50写道：
>
> > Ok, will do that.
> >
> > Thanks, @sebb , You mentioned a few areas that need to
> > be dealt with in standardized rules. We will learn from the practices of
> > our peers and make adjustments.
> >
> > sebb  于2021年7月23日周五 下午7:24写道：
> >
> >> On Fri, 23 Jul 2021 at 08:36, Goson zhang  wrote:
> >> >
> >> > Hi all,
> >> >
> >> > The Apache InLong(incubating) community is pleased to announce that
> >> Apache
> >> > InLong(incubating) 0.9.0-incubating has been released!
> >> >
> >> > Apache InLong is a one-stop data streaming platform that provides
> >> > automatic, secure,
> >> > distributed, and efficient data publishing and subscription
> >> capabilities.
> >> > This platform helps you easily build stream-based data applications.
> >> >
> >> > Download Links:
> >> > https://downloads.apache.org/incubator/inlong/0.9.0-incubating/
> >>
> >> Sorry, but that is not a valid download link.
> >> Downloads must only be advertised from a page that contains links to
> >> the KEYS, sigs and hashes, as well as the artifacts themselves.
> >>
> >> The website already has a download page:
> >> https://inlong.apache.org/en-us/docs/download/download.html
> >> However that page is missing a link to the KEYS file, and does not
> >> explain the need to verify downloads, nor how to do so.
> >> Please fix the page ASAP, and use it in future announce emails.
> >>
> >> Thanks.
> >> >
> >> > Release Notes:
> >> >
> >> https://github.com/apache/incubator-inlong/blob/release-0.9.0/CHANGES.md
> >> >
> >> > Website: https://inlong.apache.org/
> >> >
> >> > InLong Resources:
> >> > - Issue: https://issues.apache.org/jira/projects/INLONG/issues
> >> > - Mailing-list: d...@inlong.apache.org
> >> >
> >> > Thanks
> >> > On behalf of Apache InLong(Incubating) community
> >>
> >

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

Re: [ANNOUNCE] Release Apache InLong(incubating) 0.9.0-incubating

[sebb]

On Fri, 23 Jul 2021 at 08:36, Goson zhang  wrote:
>
> Hi all,
>
> The Apache InLong(incubating) community is pleased to announce that Apache
> InLong(incubating) 0.9.0-incubating has been released!
>
> Apache InLong is a one-stop data streaming platform that provides
> automatic, secure,
> distributed, and efficient data publishing and subscription capabilities.
> This platform helps you easily build stream-based data applications.
>
> Download Links:
> https://downloads.apache.org/incubator/inlong/0.9.0-incubating/

Sorry, but that is not a valid download link.
Downloads must only be advertised from a page that contains links to
the KEYS, sigs and hashes, as well as the artifacts themselves.

The website already has a download page:
https://inlong.apache.org/en-us/docs/download/download.html
However that page is missing a link to the KEYS file, and does not
explain the need to verify downloads, nor how to do so.
Please fix the page ASAP, and use it in future announce emails.

Thanks.
>
> Release Notes:
> https://github.com/apache/incubator-inlong/blob/release-0.9.0/CHANGES.md
>
> Website: https://inlong.apache.org/
>
> InLong Resources:
> - Issue: https://issues.apache.org/jira/projects/INLONG/issues
> - Mailing-list: d...@inlong.apache.org
>
> Thanks
> On behalf of Apache InLong(Incubating) community

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