Re: Missing Incubator disclaimer text

> The array is a list of pages in which the disclaimer could not be found. I do a quick check for the podlings I'm familiar with: For StreamPark, it reports: "disclaimers": [ 14, [ "https://streampark.incubator.apache.org/team;,

Re: Missing Incubator disclaimer text

On Wed, 24 Apr 2024 at 13:05, tison wrote: > > Hi Sebb, > > > quite a few podlings where the text is only present on some of the web > pages > > [1] you refers writes: > > >> Podling web sites MUST include a clear disclaimer on their website > > So, IMO it's clear that every page should contain

Helping podlings to follow our culture and policy

Hi, This is mainly for IPMC members. But I think it's suitable to discuss publicly also. I suggest we actively give positive feedback on podlings making progress on improving themselves. We're all volunteers. TBH, most IPMC members do not participate in the development of podling too much. So,

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.4-rc1

+1 binding with a few suggestions. I checked: * Download links valid. * Signature and checksum match. * LICENSE, NOTICE and DISCLAIMER are included in both source and binary releases. The content looks good to me. * No binary files in the source release Below are two suggestions: 1. You may

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

Hi, The release for Apache Fury(incubating) v0.5.0-rc3 is canceled. We didn't include the benchmark code in the source release, but the LICENSE file did contain the reference to benchmark code. This has been fixed in [1] 1. https://github.com/apache/incubator-fury/pull/1562 We will propose a

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

Hi tison, My previous reply is a little confusing. What the "we don't release furyjs in 0.5.0" means is that we don't upload release bundles to npm in this release. Best, Chaokun Yang On Thu, Apr 25, 2024 at 5:36 PM tison wrote: > Let me first summarize the result of the feedback on LICENSE

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

Let me first summarize the result of the feedback on LICENSE issues: > - there are several references to a benchmark directory, but it is not included in the release This is correct. We made [10] to address it. And We're preparing a new release candidate. [10]

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

> close this vote and start a new release candidate later. There is no blocker to cancel this vote now. You can test the new release packaging logics correctly exclude benchmark license info and we're ready to make the next RC. To cancel a vote. You can send a reply to this thread with a

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

Hi tison, Thanks for the suggestion, we don't release furyjs in 0.5.0. We can cooperate with OpenSumi after we make the first formal release of furyjs under ASF later. Best, Chaokun On Thu, Apr 25, 2024 at 5:11 PM tison wrote: > Hi Shawn, > > Thanks for sharing the finding. I can see the

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

Hi Shawn, Thanks for sharing the finding. I can see the dependency from OpenSumi to Fury as in [1] now. [1] https://github.com/search?q=repo:opensumi/core%20fury=code After we make the first formal release, we can cooperate with OpenSumi to upgrade to an incubating release and thus update the

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

Hi Justin, Thanks for sharing this tool. I checked the code in Fury with this tool. Here is the result: 1) [5][6] are osscan results. 2) Those files has duplication with package/lib/worker-host.js in opensumi[7] Opensumi relies on furyjs, so it packaged the code in apache fury into its release

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

Just have a comment on the Github repo descriptions of Incubating projects: " We need to have word of (Incubating) in the repo description." It can be updated by editing the file of .asf.yaml in the repo. Willem Jiang On Tue, Apr 23, 2024 at 9:23 AM tison wrote: > > Hi, > > Recently, the new

[VOTE] Release Apache StreamPark(Incubating) 2.1.4-rc1

Hello Incubator Community: This is a call for a vote to release Apache StreamPark(Incubating) version 2.1.4-RC1. The Apache StreamPark community has voted on and approved a proposal to release Apache StreamPark(Incubating) version 2.1.4-RC1. We now kindly request the Incubator PMC members review

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

To preview the render result I made https://github.com/apache/incubator-fury/pull/1574 to showcase. You can head to https://github.com/apache/incubator-fury/tree/tisonkun-patch-1 to see the render version. I made two candidates: 1. Inline the DISCLAIMER with an IMPORTANT callout 2. Add a badge

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

Hi Justin, Thank you, and that's not in a hurry. I'd just like to make the status clear and ensure we can make progress instead of subjective arguing. Now I know you use ScanOSS and I'd suggest other members in Fury try to check the project with this tool. I'll try it out if I find some time,

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

Hi, > 4. To clarify that a repo belongs to a podling, introduce a guideline or > policy to help PPMCs include the DISCLAIMER in the README of all their > repos. Alternatively, perhaps we can come up with something a little shorter shorter that points to DISCLAIMER? What is important is that the

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

HI, I’m happy to share it, but as I said, I'm travelling right now and don't have access. I used ScanOSS workbench, but there are other checkers out there. And yes, tools like this can sometimes give false positives, and it can sometimes be unclear where things were originally copied or, in

Improve the website of StreamPark

Hi, Recently I made two patches to improve the content of StreamPark website: * https://github.com/apache/incubator-streampark-website/pull/347 * https://github.com/apache/incubator-streampark-website/pull/349 They should showcase several common mistakes and less-than-awesome we can improve:

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

> For Go based projects dropping the incubator reference in the git repo makes things easier also when graduating I support this statement. For Java or Rust release, we generally don't include the incubator prefix in dep ID. But Golang dependency relies on the name of the GitHub repository. So it

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

> Of course we'd like to add the license info As you can see, for files we're clear that is derived, we keep their license headers, and add a link to the origin. [1] https://github.com/apache/incubator-fury/blob/dd9f9128d24b418f6a420880c7780ce83d6448a2/licenserc.toml#L28-L54 So what I'm

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

On Thu, Apr 25, 2024 at 10:36 AM Justin Mclean wrote: > Hi, > > I’m currently travelling and may be slow in responding to emails. > > > The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was > written > > by me before we open-sourced Fury and > > I submitted it to Ray in PR[8] ,which

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

> That should be fine, but having an ASF header on the files may be a little misleading? What do you think? Could you elaborate a bit on "misleading"? Shawn owned the code and he contributed the code under Apache License 2.0, and also he has filed an iCLA. So it follows the headers write:

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

> It certainly looks like some code was copied; one file, for instance, is about 70% the same. This is not an issue as it is under a compatible MIT license, but that needs to be mentioned in the LICENSE file. Could you please tell the file name and the file on OpenSumi that is overlapped? Of

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

Hi, I would be for requiring the incubator disclaimer text in the project's README: "Apache FOO 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

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

Hi, Thank you very much for the guidance from our mentors. We have updated the download page: https://devlake.apache.org/download Best, Zikuan An Zikuan An 于2024年4月24日周三 12:41写道： > Hi Willem, > > > Thank you so much for taking the time to review the download links on the > DevLake website and

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

Hi, I’m currently travelling and may be slow in responding to emails. > The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was written > by me before we open-sourced Fury and > I submitted it to Ray in PR[8] ,which was planned to optimize zero-copy > serialization in Ray. I think

Re: Missing Incubator disclaimer text

On Wed, 24 Apr 2024 at 13:05, tison wrote: > > Hi Sebb, > > > quite a few podlings where the text is only present on some of the web > pages > > [1] you refers writes: > > >> Podling web sites MUST include a clear disclaimer on their website > > So, IMO it's clear that every page should contain

Re: Publishing pywayang for pip

Awesome Xuanwo, thank you! —Alex > On 24. Apr 2024, at 16:07, Xuanwo wrote: > > Hi, > > Pypi supports OIDC so that we don't need to configure static tokens at all. > > Welcome to take a look over opendal's python release workflow[1]. You can > find more at pypa/gh-action-pypi-publish[2] >

Re: Publishing pywayang for pip

Hi, Pypi supports OIDC so that we don't need to configure static tokens at all. Welcome to take a look over opendal's python release workflow[1]. You can find more at pypa/gh-action-pypi-publish[2] [1]: https://github.com/apache/opendal/blob/main/.github/workflows/release_python.yml#L114-L139

Re: Publishing pywayang for pip

Hi Juri et all, I extend to the incubator community, since that is quite a great question. Does any project have a python module released and how does the process looks like? Thank you, —Alex > On 24. Apr 2024, at 14:23, Juri Petersen wrote: > > Hello, > we plan to publish our Python API

Re: Missing Incubator disclaimer text

Hi Sebb, > quite a few podlings where the text is only present on some of the web pages [1] you refers writes: >> Podling web sites MUST include a clear disclaimer on their website So, IMO it's clear that every page should contain such info (typically as part of the footer). If you find any

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

Thanks for your participation! For people who support drop the incubator- prefix, please describe you opinion on: > 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. > I'd propose to add the "incubating" words

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

Since it's valid that the LICENSE content to benchmark is redundant, I suggest we cancel this RC and start a new RC. In order to resolve the other potential compliance issues before the next RC is out, I'd appreciate if Justin can confirm that the reply above is clear, that is: * 5-6 is authored

Missing Incubator disclaimer text

My understanding is that the Incubator disclaimer text [1] should be present on all website pages and in announcement emails, so consumers are clear about the status of the software. However there are quite a few podlings where the text is only present on some of the web pages, and most announce

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

Hi Sebb, The published install page[1] should look good now, could you check it again? 1. https://fury.apache.org/docs/start/install Best Regards, Chaoun Yang On Wed, Apr 24, 2024 at 3:44 PM sebb wrote: > On Wed, 24 Apr 2024 at 08:29, Shawn Yang wrote: > > > > Hi Sebb, > > > > I

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

On Wed, 24 Apr 2024 at 08:29, Shawn Yang wrote: > > Hi Sebb, > > I highlight that the current release is not an asf release in the install > page in PR https://github.com/apache/incubator-fury-site/pull/113. > > Could you take a look at it again? I have just looked at the PR you just raised, and

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

Hi Sebb, I highlight that the current release is not an asf release in the install page in PR https://github.com/apache/incubator-fury-site/pull/113. Could you take a look at it again? Thanks for taking time to review Fury's release. Best regards, Chaokun Yang On Wed, Apr 24, 2024 at 3:20 PM

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

There is now a link to a potential download page, which is great. However, the install page does not make it obvious that the 0.4.1 release is not an ASF release. That information should be shown prominently at the start of the page, not buried in a note near the end. On Tue, 23 Apr 2024 at

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

Hi Justin, Thanks for helping review this release. The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was written by me before we open-sourced Fury and I submitted it to Ray in PR[8] ,which was planned to optimize zero-copy serialization in Ray. I think it's OK to include it here

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

Hi Justin, Thanks for verifying potential compliance issue. For 1-6 that you specify certain possible origins, do you have a report of the overlap files? I try to search the content of datetime.ts in OpenSumi but fail to find a result:

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

Hi Willem, Thank you so much for taking the time to review the download links on the DevLake website and for providing valuable feedback. Your guidance is greatly appreciated. We will work diligently to implement the necessary changes to ensure that our download page meets the required

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

Hi Zikuan I just checked the download links from the website of devlake[1]. We need to a page to host the downloads related information just like this[2], to provide the KEYS and signed asc files. [1] https://devlake.apache.org/ [2]https://opendal.apache.org/download Willem Jiang Twitter:

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

HI, Sorry, it’s -1 (binding) from me as it looks like there is additional third-party code without correct headers or mentioned in LICENSE. I checked: - incubating in name - signatures and hashes are fine - LICENSE has some issues (see below) - NOTICE is fine - It looks like some 3rd party code

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

All pages should have the Incubation disclaimer, but especially the home page and download page. On Wed, 3 Apr 2024 at 17:11, sebb wrote: > > On Wed, 3 Apr 2024 at 15:56, Jacky Yang wrote: >> >> Hi,sebb >> >> The download page problem has been basically fixed. >> > > There are still some

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

I updated it in the PR https://github.com/apache/incubator-fury-site/pull/112. Sorry for my last reply, I forgot to put the PR link. On Tue, Apr 23, 2024 at 10:22 PM sebb wrote: > On Tue, 23 Apr 2024 at 14:05, Shawn Yang wrote: > > > > Hi Sebb, > > > > I updated the content in the install doc

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

Hello, The vote for Apache Baremaps 0.7.3-rc1 (incubating) is now closed [1]. The results are summarised below and include the votes casted on the dev mailing list [2]. Thanks you all for your participation and for taking the time to verify the artifacts. +1 votes [9]: - Calvin Kirs

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

On Tue, 23 Apr 2024 at 14:05, Shawn Yang wrote: > > Hi Sebb, > > I updated the content in the install doc and added notes that this is not > an ASF release. > > And added a download page for download and verify source release only. > Currently this page is basically empty, but will be updated

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

Yes, for this release, we conducted extensive verifications using the list of compatible licenses provided by Apache. I believe that most, if not all, remaining licensing issues were addressed, including the one found in the test data. As honest mistakes can happen, we decided to retain the

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

Hi Sebb, I updated the content in the install doc and added notes that this is not an ASF release. And added a download page for download and verify source release only. Currently this page is basically empty, but will be updated once this vote is done, and updated to closer.lua according to

Re: Verification of download pages and links

On Tue, 23 Apr 2024 at 13:25, tison wrote: > > Thanks for starting this thread and thanks a lot for verifying the download > page for a lot of podlings! > > For previewing a staging website, with .asf.yaml config, there is a way [1] > to do so self-served by any (P)PMC. And I agree that we should

Re: Verification of download pages and links

Thanks for starting this thread and thanks a lot for verifying the download page for a lot of podlings! For previewing a staging website, with .asf.yaml config, there is a way [1] to do so self-served by any (P)PMC. And I agree that we should spread such practices to every project. [1]

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

On Tue, 23 Apr 2024 at 13:08, tison wrote: > > > They could fix the page now, while waiting for the release vote to > complete. > > Make sense. At least remove the page/content now to indicate "no Apache > release" now. Then it won't be some "forth and back" updates. It's a timing > issue. > > >

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

> They could fix the page now, while waiting for the release vote to complete. Make sense. At least remove the page/content now to indicate "no Apache release" now. Then it won't be some "forth and back" updates. It's a timing issue. > Note that the page needs more than just an update to version

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

+1 binding Please remember to update the installation page, replace the current content with the first Apache release, and remove all the prior releases refs, once this release is concluded. Otherwise, if you'd like to keep the refs to prior releases, make it clear that they are not Apache

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

On Tue, 23 Apr 2024 at 12:46, tison wrote: > > > I would be very disappointed if the podling published the code > > *knowing* that the download page is missing or incorrect. > > IIUC Fury will update the content and delete all the references to prior > releases. Note that the page needs more

Verification of download pages and links

The primary mission of the ASF is to produce open SOURCE, so it seems to me that an essential part of a release is a download page with properly constituted links to the source bundle and the associated download verification files. However, no attention seems to be given to this aspect of a

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

> I would be very disappointed if the podling published the code > *knowing* that the download page is missing or incorrect. IIUC Fury will update the content and delete all the references to prior releases. Or instead, Fury can keep these references and state clearly it's prior releases. My

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

On Tue, 23 Apr 2024 at 09:42, tison wrote: > > > There is no indication that 0.4.1 is not an ASF release. > > You may found that the group id is not org.apache.fury also. Whilst this is true, it is still not obvious that this is not an ASF release; it is easy to overlook this minor detail.

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

> There is no indication that 0.4.1 is not an ASF release. You may found that the group id is not org.apache.fury also. This is an intermediate state that we would update the content as: org.apache.fury fury-core 0.5.0 And then the content is correct. If we make any workaround or patch

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

On Mon, 22 Apr 2024 at 10:11, PJ Fanning wrote: > > 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

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

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

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

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

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

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

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

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

Re: Questions about a new project entering Apache Incubator

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

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

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:

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

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,

Re: Questions about a new project entering Apache Incubator

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

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

+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:

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

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,

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

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

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

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

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

+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

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

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

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

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]

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

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

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

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

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

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 >

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

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

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

+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

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

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

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

+1 binding [x] Download links are valid. [x] Checksums and signatures. gpg: Signature made Wed 17 Apr 2024 11:49:45 PM CST gpg:using RSA key 1E2CDAE4C08AD7D694D1CB139D7BE8E45E580BA4 gpg: checking the trustdb gpg: marginals needed: 3 completes needed: 1 trust model: pgp gpg:

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

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:

[RESULT][VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

Hello everyone, I am pleased to announce that the vote for Apache DevLake(Incubating) v0.21.0-rc1 has now concluded. Thank you all for your review and participation in the voting process. The release voting has passed with 4 binding votes and no +0 or -1 votes. The individuals who provided

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

+1. [x] Download Fury is valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct. [x] All files have license headers if necessary. [x] No compiled archives bundled in source archive.

Re: [VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

+1 (binding) Here are the checks I made. - [X] Download links are valid. - [X] Checksums and PGP signatures are valid. - [X] Source code artifacts have correct names matching the current release. - [X] LICENSE and NOTICE files are correct for the repository. - [X] All files have license headers

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

+1 binding carried over from PPMC vote On Sat 20 Apr 2024, 17: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

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

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

+1 (binding) from me, and I checked the following items: - [X] Download links are valid. - [X] Checksums and PGP signatures are valid. - [X] Source code artifacts have correct names matching the current release. - [X] LICENSE and NOTICE files are correct for the repository. - [X] All files have

Re: [VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

+1 (binding) - incubating in name - signature and hash fine - DISCLAIMER is fine - LICENSE and NOTICE are fine - No unexpected binary files - All source files have ASF headers did not compile from source On Mon, Apr 15, 2024 at 5:02 AM Jean-Baptiste Onofré wrote: > +1 (binding) > > I

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

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

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

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,

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

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

Re: [MENTORS] May report timeline - reports due May 2024

HI, As Sdap has just graduated, it doesn’t need to report. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

[MENTORS] May report timeline - reports due May 2024

Dates for next board report: Wed May 01 - Podling reports due by end of day Sun May 05 - Shepherd reviews due by end of day Sun May 05 - Summary due by end of day Tue May 07 - Mentor signoff due by end of day Wed May 08 - Report submitted to Board Wed May 15 - Board meeting Expected to report

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

+ general channel. On Wed, Apr 17, 2024 at 11:03 AM Thamir Qadah wrote: > Dear Junchao, > > I just checked the release notes for this RC. If I remember correctly, PoE > was published in EDBT 2021, not 2011, as mentioned in the change log. > > Best > > Thamir > > > On Wed, Apr 17, 2024 at 3:38 

Re: [ANNOUNCE] Apache Answer(Incubating) v1.3.0 available

On Wed, 17 Apr 2024 at 16:40, LinkinStar wrote: > > Hello everyone, > > The Apache Answer(Incubating) v1.3.0 has been released! > > Apache Answer is a Q platform software for teams at any scale. > Whether it's a community forum, help center, or knowledge management > platform, you can always

[ANNOUNCE] Apache Answer(Incubating) v1.3.0 available

Hello everyone, The Apache Answer(Incubating) v1.3.0 has been released! Apache Answer is a Q platform software for teams at any scale. Whether it's a community forum, help center, or knowledge management platform, you can always count on Apache Answer. Download Links:

Re: Questions about a new project entering Apache Incubator

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

[RESULT][VOTE] Release Apache Answer(Incubating) v1.3.0-RC1

Hello Incubator PMC and Community, The vote to release Apache Answer(Incubating) v1.3.0-RC1 has passed with 3 +1 binding and 2 +1 non-binding votes, no +0 or -1 votes. 3 (+1 binding) Xuanwo Willem Jiang Charles Zhang 2 (+1 non-binding) Feng Dong Suyan no

<    1   2   3   4   5   6   7   8   9   10   >