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
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:
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
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
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
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
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
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
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
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
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]
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.
>
> >
> 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
+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
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
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
> 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
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.
> 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
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
20 matches
Mail list logo
