Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo

[Wilfred Spiegelenburg]

For Go based projects dropping the incubator reference in the git repo makes 
things easier also when graduating. Packages and dependencies are referenced 
based on the repository name. Renaming the repository either requires changes 
throughout the code base to remove the incubator reference or the packages will 
always have the incubator reference in them.

Wilfred

On 2024/04/23 01:22:02 tison wrote:
> Hi,
> 
> Recently, the new added podlings, namely Amoro and Hertzbeat, have their
> GitHub repo in the names:
> 
> * https://github.com/apache/amoro
> * https://github.com/apache/hertzbeat
> 
> ... which is different to the other 20+ podlings and 200+ repos [1]
> existing (this number counts retired ones and those for the Incubator PMC
> itself, but it's approximate).
> 
> [1]
> https://github.com/orgs/apache/repositories?language==incubator-==all
> 
> My opinion is to agree that generally:
> 
> 1. The incubator prefix comes from the SVN days where all podlings were under
> the incubator SVN tree.
> 2. Dropping the incubator- prefix for podling's GitHub repo can reduce some
> graduation tasks (although it's somewhat a milestone and ceremony for the
> podling, and INFRA does not find it a large job, as well as it won't break
> downstream almost due to redirections).
> 3. It's still significant to make it clear that a podling is in the
> incubating status and thus a DISCLAIMER to protect the ASF branding.
> 
> With these premises, I started this thread with the following proposals and
> questions.
> 
> 1. Establish a consensus to allow podling's GitHub repo to have a name
> without incubator- prefix.
> 2. Allow other podlings to ask the INFRA to drop their incubator- prefix by
> now, not MUST during the graduation.
> 3. Update the docs on incubator.apache.org everywhere if the description
> can conflict with this consensus.
> 4. However, find a way to clarify that a repo belongs to a podling.
> 
> For 4, I'd propose to add the "incubating" words to each repo's README.
> This can be regarded as treating those READMEs a homepage for the repo and,
> 
> 1. Name the project as "Apache Foo (Incubating)" in its first and most
> prominent uses, hopefully and H1 heading.
> 2. Add a footer including the Incubator logo and DISCLAIMER, like the
> current footer of Apache Answer (Incubating) [3]
> 
> [3] https://answer.apache.org/
> 
> This method, however, can be a new chore for podlings that have many
> satellite repos that may previously claim their incubating status by naming
> the repos incubator-foo-satellite. But it's just another template to
> follow, so it won't be a big deal.
> 
> Looking forward to your thoughts on this proposal and any suggestions to
> improve the implementation part.
> 
> Best,
> tison.
> 

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

Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo

[Francis Chuang]

I think this is a well thought-out and change. It reduces the load on 
Infra and allows the project's contributors to take ownership of 
removing the (incubating) disclaimers and annotations after graduation.


On 23/04/2024 11:22 am, tison wrote:

Hi,

Recently, the new added podlings, namely Amoro and Hertzbeat, have their
GitHub repo in the names:

* https://github.com/apache/amoro
* https://github.com/apache/hertzbeat

... which is different to the other 20+ podlings and 200+ repos [1]
existing (this number counts retired ones and those for the Incubator PMC
itself, but it's approximate).

[1]
https://github.com/orgs/apache/repositories?language==incubator-==all

My opinion is to agree that generally:

1. The incubator prefix comes from the SVN days where all podlings were under
the incubator SVN tree.
2. Dropping the incubator- prefix for podling's GitHub repo can reduce some
graduation tasks (although it's somewhat a milestone and ceremony for the
podling, and INFRA does not find it a large job, as well as it won't break
downstream almost due to redirections).
3. It's still significant to make it clear that a podling is in the
incubating status and thus a DISCLAIMER to protect the ASF branding.

With these premises, I started this thread with the following proposals and
questions.

1. Establish a consensus to allow podling's GitHub repo to have a name
without incubator- prefix.
2. Allow other podlings to ask the INFRA to drop their incubator- prefix by
now, not MUST during the graduation.
3. Update the docs on incubator.apache.org everywhere if the description
can conflict with this consensus.
4. However, find a way to clarify that a repo belongs to a podling.

For 4, I'd propose to add the "incubating" words to each repo's README.
This can be regarded as treating those READMEs a homepage for the repo and,

1. Name the project as "Apache Foo (Incubating)" in its first and most
prominent uses, hopefully and H1 heading.
2. Add a footer including the Incubator logo and DISCLAIMER, like the
current footer of Apache Answer (Incubating) [3]

[3] https://answer.apache.org/

This method, however, can be a new chore for podlings that have many
satellite repos that may previously claim their incubating status by naming
the repos incubator-foo-satellite. But it's just another template to
follow, so it won't be a big deal.

Looking forward to your thoughts on this proposal and any suggestions to
improve the implementation part.

Best,
tison.



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

Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo

[Sheng Wu]

Repeated my opinion again

1. Incubating should be required for words in README and other places
mentioned, such as blogs, videos, website, github repository
2. incubator- prefix is required.
3. DISCLAIMER is required.

All of these make sure the incubating status is clear. All these have
existed for years and are easy to practice.
Basically, nothing needs to be changed about this.

Sheng Wu 吴晟
Twitter, wusheng1108

tison  于2024年4月23日周二 09:24写道：
>
> Hi,
>
> Recently, the new added podlings, namely Amoro and Hertzbeat, have their
> GitHub repo in the names:
>
> * https://github.com/apache/amoro
> * https://github.com/apache/hertzbeat
>
> ... which is different to the other 20+ podlings and 200+ repos [1]
> existing (this number counts retired ones and those for the Incubator PMC
> itself, but it's approximate).
>
> [1]
> https://github.com/orgs/apache/repositories?language==incubator-==all
>
> My opinion is to agree that generally:
>
> 1. The incubator prefix comes from the SVN days where all podlings were under
> the incubator SVN tree.
> 2. Dropping the incubator- prefix for podling's GitHub repo can reduce some
> graduation tasks (although it's somewhat a milestone and ceremony for the
> podling, and INFRA does not find it a large job, as well as it won't break
> downstream almost due to redirections).
> 3. It's still significant to make it clear that a podling is in the
> incubating status and thus a DISCLAIMER to protect the ASF branding.
>
> With these premises, I started this thread with the following proposals and
> questions.
>
> 1. Establish a consensus to allow podling's GitHub repo to have a name
> without incubator- prefix.
> 2. Allow other podlings to ask the INFRA to drop their incubator- prefix by
> now, not MUST during the graduation.
> 3. Update the docs on incubator.apache.org everywhere if the description
> can conflict with this consensus.
> 4. However, find a way to clarify that a repo belongs to a podling.
>
> For 4, I'd propose to add the "incubating" words to each repo's README.
> This can be regarded as treating those READMEs a homepage for the repo and,
>
> 1. Name the project as "Apache Foo (Incubating)" in its first and most
> prominent uses, hopefully and H1 heading.
> 2. Add a footer including the Incubator logo and DISCLAIMER, like the
> current footer of Apache Answer (Incubating) [3]
>
> [3] https://answer.apache.org/
>
> This method, however, can be a new chore for podlings that have many
> satellite repos that may previously claim their incubating status by naming
> the repos incubator-foo-satellite. But it's just another template to
> follow, so it won't be a big deal.
>
> Looking forward to your thoughts on this proposal and any suggestions to
> improve the implementation part.
>
> Best,
> tison.

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

[DISCUSS] Drop the incubator- prefix for podling's GitHub repo

[tison]

Hi,

Recently, the new added podlings, namely Amoro and Hertzbeat, have their
GitHub repo in the names:

* https://github.com/apache/amoro
* https://github.com/apache/hertzbeat

... which is different to the other 20+ podlings and 200+ repos [1]
existing (this number counts retired ones and those for the Incubator PMC
itself, but it's approximate).

[1]
https://github.com/orgs/apache/repositories?language==incubator-==all

My opinion is to agree that generally:

1. The incubator prefix comes from the SVN days where all podlings were under
the incubator SVN tree.
2. Dropping the incubator- prefix for podling's GitHub repo can reduce some
graduation tasks (although it's somewhat a milestone and ceremony for the
podling, and INFRA does not find it a large job, as well as it won't break
downstream almost due to redirections).
3. It's still significant to make it clear that a podling is in the
incubating status and thus a DISCLAIMER to protect the ASF branding.

With these premises, I started this thread with the following proposals and
questions.

1. Establish a consensus to allow podling's GitHub repo to have a name
without incubator- prefix.
2. Allow other podlings to ask the INFRA to drop their incubator- prefix by
now, not MUST during the graduation.
3. Update the docs on incubator.apache.org everywhere if the description
can conflict with this consensus.
4. However, find a way to clarify that a repo belongs to a podling.

For 4, I'd propose to add the "incubating" words to each repo's README.
This can be regarded as treating those READMEs a homepage for the repo and,

1. Name the project as "Apache Foo (Incubating)" in its first and most
prominent uses, hopefully and H1 heading.
2. Add a footer including the Incubator logo and DISCLAIMER, like the
current footer of Apache Answer (Incubating) [3]

[3] https://answer.apache.org/

This method, however, can be a new chore for podlings that have many
satellite repos that may previously claim their incubating status by naming
the repos incubator-foo-satellite. But it's just another template to
follow, so it won't be a big deal.

Looking forward to your thoughts on this proposal and any suggestions to
improve the implementation part.

Best,
tison.

Re: Questions about a new project entering Apache Incubator

[Justin Mclean]

HI,

So, I had an informal chat with Infra, and they don't care which one they do, 
but is it some work for them to change from “incubator-foo” to “foo” on 
graduation. I’m curious as to why some people in this thread think this is a 
big issue if the project clearly states it is an incubating project. I will 
note that Hertzbeat put the GitHub name in their propopal, and no one said 
anything about it.

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

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Francis Chuang]

It's a Category A license, so it should be compatible with the Apache 
License 2.0 [1]. It's listed as Creative Commons Copyright-Only 
Dedication and links to the CC0 1.0 Public Domain page.


[1] https://www.apache.org/legal/resolved.html#category-a

On 23/04/2024 7:22 am, Julian Hyde wrote:

Creative Commons Public License


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

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Julian Hyde]

I am a mentor of Baremaps. Sorry that I didn't have time to vote on
this RC on dev@.

+1 (binding)

Downloaded, checked keys, compiled and ran tests (following
instructions in README), ran RAT.

I am not familiar with "Creative Commons Public License". Is it
compatible with ALv2?

Julian

On Mon, Apr 22, 2024 at 7:13 AM Julien Waddle
 wrote:
>
> Hello
>
> + 1
>
> - build it from source => ok
> - checked download => ok
> - verified signature => ok
>
> On Mon, Apr 22, 2024 at 3:21 PM Xuanwo  wrote:
>
> > +1 binding
> >
> > [x] Download links are valid.
> > [x] Checksums and signatures.
> >
> > gpg: Signature made Wed 10 Apr 2024 04:04:56 AM CST
> > gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> > gpg: checking the trustdb
> > gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> > gpg: depth: 0  valid:  27  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 27u
> > gpg: next trustdb check due at 2024-05-25
> > gpg: Good signature from "Bertil Chapuis " [ultimate]
> > ./apache-baremaps-0.7.3-incubating-bin.tar.gz: OK
> > gpg: Signature made Wed 10 Apr 2024 04:04:57 AM CST
> > gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> > gpg: Good signature from "Bertil Chapuis " [ultimate]
> > ./apache-baremaps-0.7.3-incubating-src.tar.gz: OK
> >
> > [x] LICENSE/NOTICE files exist
> > [x] No unexpected binary files
> > [x] All source files have ASF headers
> > [x] Can compile from source on archlinux x86-64
> >
> > [INFO]
> > 
> > [INFO] Reactor Summary for baremaps 0.7.3:
> > [INFO]
> > [INFO] baremaps ... SUCCESS [
> > 0.454 s]
> > [INFO] baremaps-core .. SUCCESS [
> > 49.027 s]
> > [INFO] baremaps-server  SUCCESS [01:20
> > min]
> > [INFO] baremaps-cli ... SUCCESS [01:48
> > min]
> > [INFO]
> > 
> > [INFO] BUILD SUCCESS
> > [INFO]
> > 
> > [INFO] Total time:  03:58 min
> > [INFO] Finished at: 2024-04-22T21:16:39+08:00
> > [INFO]
> > 
> > mvn install  104.60s user 4.21s system 45% cpu 3:59.40 total
> >
> > On Mon, Apr 22, 2024, at 20:20, Bertil Chapuis wrote:
> > > Thanks a lot for taking the time to cast your votes.
> > >
> > > If we carry all the votes from the dev mailing list, we currently have
> > > 2 positive binding votes and 4 positive non-binding votes. I suggest we
> > > keep this thread open until we get a third positive binding vote from
> > > the PPMC.
> > >
> > > Best regards,
> > >
> > > Bertil
> > >
> > >> On 18 Apr 2024, at 13:06, Bertil Chapuis  wrote:
> > >>
> > >> Hello Everyone,
> > >>
> > >> This is a call for a vote to release Apache Baremaps 0.7.3
> > (incubating), release candidate 1. Apache Baremaps is a toolkit and a set
> > of infrastructure components for creating, publishing, and operating online
> > maps.
> > >>
> > >> We already voted for this release candidate in our dev mailing list:
> > >> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
> > >>
> > >> We now would like to request the Incubator PMC members to review and
> > vote on this release.
> > >>
> > >> You can read the release notes here:
> > >> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
> > >>
> > >> The commit to be voted upon:
> > >> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
> > >>
> > >> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
> > >>
> > >> Its tag is v0.7.3-rc1.
> > >>
> > >> The artifacts to be voted on are located here:
> > >> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
> > >>
> > >> The hashes of the artifacts are as follows:
> > >>
> > 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
> > ./apache-baremaps-0.7.3-incubating-src.tar.gz
> > >>
> > 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
> > ./apache-baremaps-0.7.3-incubating-bin.tar.gz
> > >>
> > >> Release artifacts are signed with the following key:
> > >> http://people.apache.org/keys/committer/bchapuis.asc
> > >> https://downloads.apache.org/incubator/baremaps/KEYS
> > >>
> > >> The README file for the src distribution contains instructions for
> > building and testing the release.
> > >>
> > >> Please vote on releasing this package as Apache Baremaps 0.7.3.
> > >>
> > >> The vote is open for the next 72 hours and passes if a majority of at
> > least three +1 PMC votes are cast.
> > >>
> > >> [ ] +1 Release this package as Apache Baremaps 0.7.3
> > >> [ ] 0 I don't feel strongly about it, but I'm okay with the release

Re: Questions about a new project entering Apache Incubator

[Sheng Wu]

With no further update, the consensus is clear from most that.

The podlings should have `incubator-` prefix as most other projects followed.

Armoro and Hertzbeat PPMC team, please fix this.

Sheng Wu 吴晟
Twitter, wusheng1108

Chao Gong  于2024年4月17日周三 20:03写道：
>
> Hi rat O,
>
> Sorry for slowly response, We will clean the non-english language in the
> codes later.
>
> Best Wishes.
> Tom
>
> rat O  于2024年4月17日周三 17:48写道：
>
> >
> > > For projects in incubation, is it no longer necessary for the project
> > name to have the "incubator-" prefix as it used to be?
> >
> > Thanks to the Apache members for responding. It make me know that this
> > issue is being looked into.
> >
> > > I wonder if the situation of having a significant amount of non-English
> > languages in the codes, like these
> > >
> > https://github.com/apache/hertzbeat/blob/master/warehouse/src/main/java/org/apache/hertzbeat/warehouse/config/WarehouseProperties.java
> > ,
> > >
> > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/entity/manager/NoticeRule.java
> > ,
> > >
> > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/config/AviatorConfiguration.java
> > > ...
> > > , will all of them also be addressed in the future?
> >
> > I would also like to receive a response from Apache regarding this issue
> > of a significant amount of non-English language in codes.
> >
> > 
> > From: tison 
> > Sent: Wednesday, April 17, 2024 5:16 PM
> > To: general@incubator.apache.org 
> > Subject: Re: Questions about a new project entering Apache Incubator
> >
> > And [1] is actually update the community docs without INFRA changes.
> > Previously (and now?), foo.incubator.apache.org has the same content with
> > foo.apache.org unless you explicitly ask INFRA to change.
> >
> > Like even
> > https://flink.incubator.apache.org/.
> >
> > I guess the main "pain point" is whimsy Web check checks "
> > foo.incubator.apache.org" in config in some file on SVN before, and thus
> > cause the Web check having a red mark.
> >
> > Best,
> > tison.
> >
> >
> > tison 于2024年4月17日 周三17:02写道：
> >
> > > I vote in [1] since it's how we practice for quite a while and it's a
> > > clear consensus by the vote.
> > >
> > > All the repo of podlings have incubator- prefix, I don't see a motivation
> > > to change.
> > >
> > > In [2] it says:
> > >
> > > > make less work for Infra
> > >
> > > I wonder if INFRA complained for this process. And what is the associated
> > > JIRA ticket in INFRA to do the rename. I'd like to take INFRA's opinion
> > > into consideration.
> > >
> > > In my previous experience, keep the name "foo", let INFRA move the repo,
> > > rename it to "incubator-foo", and drop the prefix on graduation. In this
> > > way, the link "apache/foo" will always work with GH redirections.
> > >
> > > To John:
> > >
> > > > , it can be confusing that they do.
> > >
> > > What is the certain redirection causing your confusion?
> > >
> > > Best,
> > > tison.
> > >
> > > [1]
> > > https://lists.apache.org/thread/n18gkb23bp005gb176jnwo2nrxty3z84
> > > [2]
> > > https://github.com/apache/amoro/issues/2700
> > >
> > >
> > > Sheng Wu 于2024年4月17日 周三12:09写道：
> > >
> > >> This is not to get the conclusion, and it is not clear, and many other
> > >> project repositories are with this prefix.
> > >>
> > >>
> > >>
> > https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator
> > >> (tison
> > >> found)
> > >>
> > >> Graduation doc is there indicating incaubtor- prefix is expected. This
> > is
> > >> just a 10s operation on GitHub admin page, not a heavy work. Graduation
> > is
> > >> not happening every day, even not every month. Developer don't have to
> > >> change remote git, as that redirect forward is supported too.
> > >>
> > >> More importantly, I don't agree this is clear without prefix.
> > >>
> > >> This us serious change, if you inist this is clear, start a vote. A lot
> > of
> > >> ppl in this context don't agree too.
> > >>
> > >> Sheng Wu 吴晟
> > >>
> > >> Apache SkyWalking
> > >> Twitter, wusheng1108
> > >>
> > >>
> > >> Justin Mclean 于2024年4月17日 周三11:59写道：
> > >>
> > >> > Hi,
> > >> >
> > >> > Both of these projects are new and just getting set up. I'd give them
> > a
> > >> > little time to do that. Infra in recent years have asked to minimise
> > >> work
> > >> > for them on graduation. We recently dropped the requirement for having
> > >> > incubating in podling domain names so I don't see it's needed in repo
> > >> names
> > >> > as long as it clear the project is an incubating project.
> > >> > Kind Regards,
> > >> > Justin
> > >> >
> > >> >
> > >> > On Wed, 17 Apr 2024, 1:47 pm Willem Jiang, 
> > >> wrote:
> > >> >
> > >> > > With the "incubator" profix, it's easy for us to tell if the project
> > >> > > belongs to the incubator and it is still in the incubating process.
> > >> > > Currently I cannot find any 

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Xuanwo]

+1 binding

[x] Download links are valid.
[x] Checksums and signatures.

gpg: Signature made Wed 10 Apr 2024 04:04:56 AM CST
gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:  27  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 27u
gpg: next trustdb check due at 2024-05-25
gpg: Good signature from "Bertil Chapuis " [ultimate]
./apache-baremaps-0.7.3-incubating-bin.tar.gz: OK
gpg: Signature made Wed 10 Apr 2024 04:04:57 AM CST
gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
gpg: Good signature from "Bertil Chapuis " [ultimate]
./apache-baremaps-0.7.3-incubating-src.tar.gz: OK

[x] LICENSE/NOTICE files exist
[x] No unexpected binary files
[x] All source files have ASF headers
[x] Can compile from source on archlinux x86-64

[INFO] 
[INFO] Reactor Summary for baremaps 0.7.3:
[INFO]
[INFO] baremaps ... SUCCESS [  0.454 s]
[INFO] baremaps-core .. SUCCESS [ 49.027 s]
[INFO] baremaps-server  SUCCESS [01:20 min]
[INFO] baremaps-cli ... SUCCESS [01:48 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  03:58 min
[INFO] Finished at: 2024-04-22T21:16:39+08:00
[INFO] 
mvn install  104.60s user 4.21s system 45% cpu 3:59.40 total

On Mon, Apr 22, 2024, at 20:20, Bertil Chapuis wrote:
> Thanks a lot for taking the time to cast your votes. 
>
> If we carry all the votes from the dev mailing list, we currently have 
> 2 positive binding votes and 4 positive non-binding votes. I suggest we 
> keep this thread open until we get a third positive binding vote from 
> the PPMC.
>
> Best regards,
>
> Bertil
>
>> On 18 Apr 2024, at 13:06, Bertil Chapuis  wrote:
>> 
>> Hello Everyone,
>> 
>> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating), 
>> release candidate 1. Apache Baremaps is a toolkit and a set of 
>> infrastructure components for creating, publishing, and operating online 
>> maps.
>> 
>> We already voted for this release candidate in our dev mailing list:
>> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
>> 
>> We now would like to request the Incubator PMC members to review and vote on 
>> this release.
>> 
>> You can read the release notes here:
>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
>> 
>> The commit to be voted upon:
>> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
>> 
>> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
>> 
>> Its tag is v0.7.3-rc1.
>> 
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
>> 
>> The hashes of the artifacts are as follows:
>> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>>  ./apache-baremaps-0.7.3-incubating-src.tar.gz
>> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/bchapuis.asc
>> https://downloads.apache.org/incubator/baremaps/KEYS
>> 
>> The README file for the src distribution contains instructions for building 
>> and testing the release.
>> 
>> Please vote on releasing this package as Apache Baremaps 0.7.3.
>> 
>> The vote is open for the next 72 hours and passes if a majority of at least 
>> three +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Baremaps 0.7.3
>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because…
>> 
>> Best regards,
>> 
>> Bertil Chapuis
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-- 
Xuanwo

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

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Bertil Chapuis]

Thanks a lot for taking the time to cast your votes. 

If we carry all the votes from the dev mailing list, we currently have 2 
positive binding votes and 4 positive non-binding votes. I suggest we keep this 
thread open until we get a third positive binding vote from the PPMC.

Best regards,

Bertil

> On 18 Apr 2024, at 13:06, Bertil Chapuis  wrote:
> 
> Hello Everyone,
> 
> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating), 
> release candidate 1. Apache Baremaps is a toolkit and a set of infrastructure 
> components for creating, publishing, and operating online maps.
> 
> We already voted for this release candidate in our dev mailing list:
> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
> 
> We now would like to request the Incubator PMC members to review and vote on 
> this release.
> 
> You can read the release notes here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
> 
> The commit to be voted upon:
> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
> 
> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
> 
> Its tag is v0.7.3-rc1.
> 
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
> 
> The hashes of the artifacts are as follows:
> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>  ./apache-baremaps-0.7.3-incubating-src.tar.gz
> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
> 
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/bchapuis.asc
> https://downloads.apache.org/incubator/baremaps/KEYS
> 
> The README file for the src distribution contains instructions for building 
> and testing the release.
> 
> Please vote on releasing this package as Apache Baremaps 0.7.3.
> 
> The vote is open for the next 72 hours and passes if a majority of at least 
> three +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Baremaps 0.7.3
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because…
> 
> Best regards,
> 
> Bertil Chapuis


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

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Bertil Chapuis]

Thanks a lot, it is good to see that the compilation went well on WSL.

> On 18 Apr 2024, at 13:38, Francis Chuang  wrote:
> 
> My vote is +1 (binding)
> 
> - Checked SHA512 signatures - OK
> - Extracted contents of binary and source archives - OK
> - Checked GPG signatures - OK
> - Checked README - OK
> - Checked NOTICE - OK
> - Checked LICENSE - OK
> - Went through release notes - OK
> - Ran tests and built: mvn clean install - OK
> 
> Environment: maven:3-eclipse-temurin-17 docker container using Docker Desktop 
> 4.29.0 on Windows 11 23H2 in WSL.
> 
> $ mvn -v
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/share/maven
> Java version: 17.0.10, vendor: Eclipse Adoptium, runtime: /opt/java/openjdk
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.146.1-microsoft-standard-wsl2", arch: 
> "amd64", family: "unix"
> 
> $ java --version
> openjdk 17.0.10 2024-01-16
> OpenJDK Runtime Environment Temurin-17.0.10+7 (build 17.0.10+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (build 17.0.10+7, mixed mode, 
> sharing)
> 
> Francis
> 
> On 18/04/2024 9:06 pm, Bertil Chapuis wrote:
>> Hello Everyone,
>> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating), 
>> release candidate 1. Apache Baremaps is a toolkit and a set of 
>> infrastructure components for creating, publishing, and operating online 
>> maps.
>> We already voted for this release candidate in our dev mailing list:
>> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
>> We now would like to request the Incubator PMC members to review and vote on 
>> this release.
>> You can read the release notes here:
>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
>> The commit to be voted upon:
>> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
>> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
>> Its tag is v0.7.3-rc1.
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
>> The hashes of the artifacts are as follows:
>> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>>  ./apache-baremaps-0.7.3-incubating-src.tar.gz
>> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/bchapuis.asc
>> https://downloads.apache.org/incubator/baremaps/KEYS
>> The README file for the src distribution contains instructions for building 
>> and testing the release.
>> Please vote on releasing this package as Apache Baremaps 0.7.3.
>> The vote is open for the next 72 hours and passes if a majority of at least 
>> three +1 PMC votes are cast.
>> [ ] +1 Release this package as Apache Baremaps 0.7.3
>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because…
>> Best regards,
>> Bertil Chapuis
>> -
>> 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 Baremaps 0.7.3-rc1 (incubating)

[Bertil Chapuis]

Thanks a lot for your feedback, I will include these intructions in the future.

Best,

Bertil

> On 22 Apr 2024, at 13:40, Suyan  wrote:
> 
> +1 non-binding
> Apache ID: suyanhanx
> 
> I checked:
> 
> [x] Download links are valid.
> [x] Checksums and signatures.
> gpg: Signature made Wed Apr 10 04:04:57 2024 CST
> gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:  23  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 23u
> gpg: next trustdb check due at 2024-05-25
> gpg: Good signature from "Bertil Chapuis " [ultimate]
> 
> [x] LICENSE/NOTICE files exist
> [x] Can compile from source on macOS(arm64)
> 
> [INFO] 
> 
> [INFO] Reactor Summary for baremaps 0.7.3:
> [INFO]
> [INFO] baremaps ... SUCCESS [  0.324 
> s]
> [INFO] baremaps-core .. SUCCESS [  8.191 
> s]
> [INFO] baremaps-server  SUCCESS [  6.621 
> s]
> [INFO] baremaps-cli ... SUCCESS [ 30.057 
> s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time:  45.442 s
> [INFO] Finished at: 2024-04-22T19:37:34+08:00
> [INFO] 
> 
> 
> 
> One small suggestion, your vote email doesn't mention how to compile.
> It will be better to add a link.
> 
> Sincerely,
> Suyan
> 
> Bertil Chapuis  于2024年4月18日周四 19:06写道：
>> 
>> Hello Everyone,
>> 
>> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating), 
>> release candidate 1. Apache Baremaps is a toolkit and a set of 
>> infrastructure components for creating, publishing, and operating online 
>> maps.
>> 
>> We already voted for this release candidate in our dev mailing list:
>> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
>> 
>> We now would like to request the Incubator PMC members to review and vote on 
>> this release.
>> 
>> You can read the release notes here:
>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
>> 
>> The commit to be voted upon:
>> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
>> 
>> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
>> 
>> Its tag is v0.7.3-rc1.
>> 
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
>> 
>> The hashes of the artifacts are as follows:
>> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>>  ./apache-baremaps-0.7.3-incubating-src.tar.gz
>> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/bchapuis.asc
>> https://downloads.apache.org/incubator/baremaps/KEYS
>> 
>> The README file for the src distribution contains instructions for building 
>> and testing the release.
>> 
>> Please vote on releasing this package as Apache Baremaps 0.7.3.
>> 
>> The vote is open for the next 72 hours and passes if a majority of at least 
>> three +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Baremaps 0.7.3
>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because…
>> 
>> Best regards,
>> 
>> Bertil Chapuis
>> 
>> -
>> 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 Baremaps 0.7.3-rc1 (incubating)

[Suyan]

+1 non-binding
Apache ID: suyanhanx

I checked:

[x] Download links are valid.
[x] Checksums and signatures.
gpg: Signature made Wed Apr 10 04:04:57 2024 CST
gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:  23  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 23u
gpg: next trustdb check due at 2024-05-25
gpg: Good signature from "Bertil Chapuis " [ultimate]

[x] LICENSE/NOTICE files exist
[x] Can compile from source on macOS(arm64)

[INFO] 
[INFO] Reactor Summary for baremaps 0.7.3:
[INFO]
[INFO] baremaps ... SUCCESS [  0.324 s]
[INFO] baremaps-core .. SUCCESS [  8.191 s]
[INFO] baremaps-server  SUCCESS [  6.621 s]
[INFO] baremaps-cli ... SUCCESS [ 30.057 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  45.442 s
[INFO] Finished at: 2024-04-22T19:37:34+08:00
[INFO] 


One small suggestion, your vote email doesn't mention how to compile.
It will be better to add a link.

Sincerely,
Suyan

Bertil Chapuis  于2024年4月18日周四 19:06写道：
>
> Hello Everyone,
>
> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating), 
> release candidate 1. Apache Baremaps is a toolkit and a set of infrastructure 
> components for creating, publishing, and operating online maps.
>
> We already voted for this release candidate in our dev mailing list:
> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
>
> We now would like to request the Incubator PMC members to review and vote on 
> this release.
>
> You can read the release notes here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
>
> The commit to be voted upon:
> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
>
> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
>
> Its tag is v0.7.3-rc1.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
>
> The hashes of the artifacts are as follows:
> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>  ./apache-baremaps-0.7.3-incubating-src.tar.gz
> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/bchapuis.asc
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The README file for the src distribution contains instructions for building 
> and testing the release.
>
> Please vote on releasing this package as Apache Baremaps 0.7.3.
>
> The vote is open for the next 72 hours and passes if a majority of at least 
> three +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Baremaps 0.7.3
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because…
>
> Best regards,
>
> Bertil Chapuis
>
> -
> 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 Fury(incubating) v0.5.0-rc3

[Shawn Yang]

Hi Sebb,

Thanks for reviewing the Fury release.

You are right that the snapshot packages should not be included in the
project website according to the apache release policy[1].

I created a PR[2] to fix this. It won't block this vote.

For download pages, as PJ said, we haven't released Fury since it became a
podling. So we didn't add download pages yet.
If this vote passes, we will add download pages later according to the
release-download-pages document, which is your suggestion too.


1. https://www.apache.org/legal/release-policy.html#what
2. https://github.com/apache/incubator-fury-site/pull/111/
3. https://infra.apache.org/release-download-pages.html

On Mon, Apr 22, 2024 at 4:35 PM sebb  wrote:

> On Sat, 20 Apr 2024 at 16:26, Shawn Yang  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating)
> v0.5.0-rc3.
> >
> > The Apache Fury community has voted and approved the release of Apache
> > Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > Fury community vote thread:
> > https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
> >
> > Vote result thread:
> > https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/fury/KEYS
> >
>
> I could not find a proper download page for the release.
> This must have links to the source bundle which must use closer.lua,
> as well as links to KEYS, sigs and hashes, with instructions on how to
> validate downloads.
>
> There is an install page on the website at
> https://fury.apache.org/docs/start/install, but that does not link to
> any source bundle.
>
> Furthermore, the install page links to nightly snapshots; this is not
> allowed except on a page intended for Fury developers, who should be
> made aware that nightly code has not been vetted.
>
> > Git tag for the release:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
> >
> > Git commit for the release:
> >
> https://github.com/apache/incubator-fury/commit/fae06330edd049bb960536e978a45b97bca66faf
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachefury-1003
> >
> > How to Build and Test, please refer to:
> >
> https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.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
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache fury, please see https://fury.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> >
> > Thanks,
> >
> > Chaokun Yang
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

[Shawn Yang]

Hi Suyan,

Thanks for reviewing Fury  release and the suggestions. We will update our
build document to give a more detailed environment requirements later.

On Monday, April 22, 2024, Suyan  wrote:

> +1 non-binding
> Apache ID: suyanhanx
>
> I checked:
>
> [x] Download links are valid.
> [x] Checksums and signaturesgpg: Signature made Wed Apr 17 23:49:45 2024
> CST
> gpg:using RSA key 1E2CDAE4C08AD7D694D1CB139D7BE8E45E580BA4
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:  22  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 22u
> gpg: next trustdb check due at 2024-05-25
> gpg: Good signature from "chaokunyang (CODE SIGNING KEY)
> " [ultimate].
>
> [x] LICENSE/NOTICE files exist
> [x] No unexpected binary files
> [x] All source files have ASF headers
> [x] Can compile from source
>
> I built packages for three languages, java, javaScript, and rust.They
> all finished fine.
>
> But when I was compiling the javascript package since you are using
> node-gyp,
> it also relies on a specific range of versions of Python.
> My local Python version is newer, which gave me some unexpected
> dependency issues.
> You guys might want to give more explicit guidance on environment
> requirements.
>
> refs:
> - https://github.com/nodejs/node-gyp/issues/2869
>
> Sincerely,
> Suyan
>
> Shawn Yang  于2024年4月20日周六 23:26写道：
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating)
> v0.5.0-rc3.
> >
> > The Apache Fury community has voted and approved the release of Apache
> > Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > Fury community vote thread:
> > https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
> >
> > Vote result thread:
> > https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/fury/KEYS
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
> >
> > Git commit for the release:
> > https://github.com/apache/incubator-fury/commit/
> fae06330edd049bb960536e978a45b97bca66faf
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachefury-1003
> >
> > How to Build and Test, please refer to:
> > https://github.com/apache/incubator-fury/blob/main/docs/
> guide/DEVELOPMENT.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
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache fury, please see https://fury.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> >
> > Thanks,
> >
> > Chaokun Yang
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

[PJ Fanning]

Hi Sebb,
This email thread is a vote for an RC. If this vote passes, v0.5.0
will be the first release of Fury since it became a podling.
We will add a download page but at the moment, there is nothing to
link to there (except perhaps a KEYS file).

The Install page does need to be updated to not mention snapshots.

Thanks,
PJ

On Mon, 22 Apr 2024 at 10:35, sebb  wrote:
>
> On Sat, 20 Apr 2024 at 16:26, Shawn Yang  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc3.
> >
> > The Apache Fury community has voted and approved the release of Apache
> > Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > Fury community vote thread:
> > https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
> >
> > Vote result thread:
> > https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/fury/KEYS
> >
>
> I could not find a proper download page for the release.
> This must have links to the source bundle which must use closer.lua,
> as well as links to KEYS, sigs and hashes, with instructions on how to
> validate downloads.
>
> There is an install page on the website at
> https://fury.apache.org/docs/start/install, but that does not link to
> any source bundle.
>
> Furthermore, the install page links to nightly snapshots; this is not
> allowed except on a page intended for Fury developers, who should be
> made aware that nightly code has not been vetted.
>
> > Git tag for the release:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
> >
> > Git commit for the release:
> > https://github.com/apache/incubator-fury/commit/fae06330edd049bb960536e978a45b97bca66faf
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachefury-1003
> >
> > How to Build and Test, please refer to:
> > https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.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
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache fury, please see https://fury.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> >
> > Thanks,
> >
> > Chaokun Yang
>
> -
> 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 Devlake(incubating) 0.21.0-incubating

[Zikuan An]

Hi Sebb,

Thank you very much for your advice and guidance.
We will reach out to our mentors to ensure that our download page meets the
required criteria.

Thanks again for your patience and assistance!

Best,
Zikuan An

sebb  于2024年4月22日周一 16:20写道：

> On Mon, 22 Apr 2024 at 03:47, Zikuan An  wrote:
> >
> > Hello everyone,
> >
> >
> > The Apache Devlake(incubating) 0.21.0-incubating has been released!
> >
> >
> > Apache DevLake is an open-source dev data platform that ingests,
> analyzes,
> > and visualizes the fragmented data from DevOps tools to distill insights
> > for engineering productivity.
> >
> >
> > Download Links:  https://downloads.apache.org/incubator/devlake/
>
> Sorry, but that is not a valid download page.
>
> A download page must use closer.lua to link to thw artifacts, and must
> include links to KEYS, sigs and hashes, and instructions on
> validation.
>
> Your mentors should be able to help with this.
>
> > Changelogs:
> >
> > - Support circle ci as a data source for the CI/CD domain
> >
> > - Support opsgenie plugin
> >
> > - Add original_status and original_result to all CICD entities
> >
> > - Allow deployment webhook to push deployments to multiple repos in one
> > request
> > - Simplify the display of the GitHub Scope Config
> >
> >
> > Website: https://devlake.apache.org/
> >
> >
> > Resources:
> >
> > - Issue: https://github.com/apache/incubator-devlake/issues
> >
> > - Mailing list: d...@devlake.apache.org
> >
> >
> > Best Regards
> >
> > Zikuan An
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

[sebb]

On Sat, 20 Apr 2024 at 16:26, Shawn Yang  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc3.
>
> The Apache Fury community has voted and approved the release of Apache
> Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> review and vote for this release.
>
> Apache Fury(incubating) - A blazingly fast multi-language serialization
> framework powered by JIT and zero-copy.
>
> Fury community vote thread:
> https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
>
> Vote result thread:
> https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
>
> This release has been signed with a PGP available here:
> https://downloads.apache.org/incubator/fury/KEYS
>

I could not find a proper download page for the release.
This must have links to the source bundle which must use closer.lua,
as well as links to KEYS, sigs and hashes, with instructions on how to
validate downloads.

There is an install page on the website at
https://fury.apache.org/docs/start/install, but that does not link to
any source bundle.

Furthermore, the install page links to nightly snapshots; this is not
allowed except on a page intended for Fury developers, who should be
made aware that nightly code has not been vetted.

> Git tag for the release:
> https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
>
> Git commit for the release:
> https://github.com/apache/incubator-fury/commit/fae06330edd049bb960536e978a45b97bca66faf
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachefury-1003
>
> How to Build and Test, please refer to:
> https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.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
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache fury, please see https://fury.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
>
> Thanks,
>
> Chaokun Yang

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

Re: [ANNOUNCE] Release Apache Devlake(incubating) 0.21.0-incubating

[sebb]

On Mon, 22 Apr 2024 at 03:47, Zikuan An  wrote:
>
> Hello everyone,
>
>
> The Apache Devlake(incubating) 0.21.0-incubating has been released!
>
>
> Apache DevLake is an open-source dev data platform that ingests, analyzes,
> and visualizes the fragmented data from DevOps tools to distill insights
> for engineering productivity.
>
>
> Download Links:  https://downloads.apache.org/incubator/devlake/

Sorry, but that is not a valid download page.

A download page must use closer.lua to link to thw artifacts, and must
include links to KEYS, sigs and hashes, and instructions on
validation.

Your mentors should be able to help with this.

> Changelogs:
>
> - Support circle ci as a data source for the CI/CD domain
>
> - Support opsgenie plugin
>
> - Add original_status and original_result to all CICD entities
>
> - Allow deployment webhook to push deployments to multiple repos in one
> request
> - Simplify the display of the GitHub Scope Config
>
>
> Website: https://devlake.apache.org/
>
>
> Resources:
>
> - Issue: https://github.com/apache/incubator-devlake/issues
>
> - Mailing list: d...@devlake.apache.org
>
>
> Best Regards
>
> Zikuan An

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

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

[Suyan]

+1 non-binding
Apache ID: suyanhanx

I checked:

[x] Download links are valid.
[x] Checksums and signaturesgpg: Signature made Wed Apr 17 23:49:45 2024 CST
gpg:using RSA key 1E2CDAE4C08AD7D694D1CB139D7BE8E45E580BA4
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:  22  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 22u
gpg: next trustdb check due at 2024-05-25
gpg: Good signature from "chaokunyang (CODE SIGNING KEY)
" [ultimate].

[x] LICENSE/NOTICE files exist
[x] No unexpected binary files
[x] All source files have ASF headers
[x] Can compile from source

I built packages for three languages, java, javaScript, and rust.They
all finished fine.

But when I was compiling the javascript package since you are using node-gyp,
it also relies on a specific range of versions of Python.
My local Python version is newer, which gave me some unexpected
dependency issues.
You guys might want to give more explicit guidance on environment requirements.

refs:
- https://github.com/nodejs/node-gyp/issues/2869

Sincerely,
Suyan

Shawn Yang  于2024年4月20日周六 23:26写道：
>
> Hello everyone,
>
> This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc3.
>
> The Apache Fury community has voted and approved the release of Apache
> Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> review and vote for this release.
>
> Apache Fury(incubating) - A blazingly fast multi-language serialization
> framework powered by JIT and zero-copy.
>
> Fury community vote thread:
> https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
>
> Vote result thread:
> https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
>
> This release has been signed with a PGP available here:
> https://downloads.apache.org/incubator/fury/KEYS
>
> Git tag for the release:
> https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
>
> Git commit for the release:
> https://github.com/apache/incubator-fury/commit/fae06330edd049bb960536e978a45b97bca66faf
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachefury-1003
>
> How to Build and Test, please refer to:
> https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.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
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache fury, please see https://fury.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
>
> Thanks,
>
> Chaokun Yang

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

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Leo]

I also carry my +1 non-binding vote from dev.

> On 18 Apr 2024, at 13:08, Calvin Kirs  wrote:
> 
> Carry my +1 binding from dev@ vote.
> 
> On Thu, Apr 18, 2024 at 7:06 PM Bertil Chapuis  > wrote:
> 
>> Hello Everyone,
>> 
>> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating),
>> release candidate 1. Apache Baremaps is a toolkit and a set of
>> infrastructure components for creating, publishing, and operating online
>> maps.
>> 
>> We already voted for this release candidate in our dev mailing list:
>> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
>> 
>> We now would like to request the Incubator PMC members to review and vote
>> on this release.
>> 
>> You can read the release notes here:
>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
>> 
>> The commit to be voted upon:
>> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
>> 
>> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
>> 
>> Its tag is v0.7.3-rc1.
>> 
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
>> 
>> The hashes of the artifacts are as follows:
>> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>> ./apache-baremaps-0.7.3-incubating-src.tar.gz
>> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>> ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/bchapuis.asc
>> https://downloads.apache.org/incubator/baremaps/KEYS
>> 
>> The README file for the src distribution contains instructions for
>> building and testing the release.
>> 
>> Please vote on releasing this package as Apache Baremaps 0.7.3.
>> 
>> The vote is open for the next 72 hours and passes if a majority of at
>> least three +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Baremaps 0.7.3
>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because…
>> 
>> Best regards,
>> 
>> Bertil Chapuis
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>> 
>> For additional commands, e-mail: general-h...@incubator.apache.org 
>> 
>> 
>> 
> 
> -- 
> Best wishes！
> CalvinKirs