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 th
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 Amor
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 f
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 f
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 proj
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:
Cre
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, A
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 res
+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: dept
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,
Ber
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
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
+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 need
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 sin
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] Chec
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 me
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
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
> revi
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
>
+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
20 matches
Mail list logo