Hi,
> It not a requirement but many project do it so they can link to it from
their download page.
Yes, and I in favor of this view.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Justin Mclean 于2020年8月20日周四 上午10:22写道:
> Hi,
Hi,
> I checked many projects on [1], few projects put the readme file
> separated with the source-release file.
It not a requirement but many project do it so they can link to it from their
download page. People often want to look at the README before downloading and
installing the software.
Hi,
I checked many projects on [1], few projects put the readme file
separated with the source-release file.
I think the Apache release guideline does not require that.
I agree that an easy-touched README file helps the community
(especially who are not familiar with the project) knowing the proj
Hi @Kevin Ratnasekera . Thank you for your important vote for us.
> 2020年8月19日 下午11:17,Kevin Ratnasekera 写道:
>
> +1
>
> I checked the following.
>
> - Incubating in name.
>
> - PGP Signatures.
>
> - SHA512 Checksums.
>
> - DISCLAIMER exists.
>
> - LICENSE and NOTICE are fine.
>
> - No un
+1 (Binding) I verified autogluon.
Best,
Xingjian
On 8/19/20, 6:15 PM, "Chen, Ciyong" wrote:
Hi Jason,
Thank you for your time to check and vote on this.
Hi IPMC and community,
We've got two binding votes, and now we're looking forward to one more
binding votes for this relea
Hi Jason,
Thank you for your time to check and vote on this.
Hi IPMC and community,
We've got two binding votes, and now we're looking forward to one more binding
votes for this release, please help on this, many thanks!!
Regards,
-Ciyong
-Original Message-
From: Jason Dai
Sent: Wedne
I see
jlowe is a binding IPMC vote that can carry forward from dev@ vote.
We just need 1 more binding vote.
On Mon, Aug 17, 2020 at 11:06 PM Felix Cheung
wrote:
> +1 (binding)
>
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE and NOTICE are fine
> - No un
I wouldn't say they have to be there ...
but I personally do like projects that have them there: A README as well as a
RELEASE_NOTES.
Chris
Am 19.08.20, 16:17 schrieb "Xiangdong Huang" :
Hi,
> I just have a quick question about the README files. Why do we put them
into
+1
I checked the following.
- Incubating in name.
- PGP Signatures.
- SHA512 Checksums.
- DISCLAIMER exists.
- LICENSE and NOTICE are fine.
- No unexpected binary files.
- Maven build passes.
Regards
Kevin
On Wed, Aug 19, 2020 at 3:03 PM JUN GAO wrote:
> Hi , Thank you very much for no
Hi,
> I just have a quick question about the README files. Why do we put them
into the release directory?
Thanks, Willem. Yes, you are right, we do not need to put the README files
to the SVN
(But they still need to be included in our source-release files)...
We will fix our release process to r
+1 (binding)
I checked:
- Incubating in name
- Signatures and hashes
- Disclaimer, LICENSE and NOTICE
Thanks,
-Jason
On Tue, Aug 18, 2020 at 6:25 PM Michael Wall wrote:
> Thanks for the follow up Ciyong. You are right, -vv did not enable
> verbose. If I had used -VV (with capital V's)
Hi , Thank you very much for noticing this email.
This maven plugin is dependency by a pull request, so we hope to release this
version soon .
Now we still need 2 binding votes, We look forward to more votes from IPMCs for
this release.
Can you help me?
Best regards
> 2020年8月19日 上午8:58,JUN
Hi , Thank you very much for noticing this email.
This maven plugin is dependency by a pull request, so we hope to release this
version soon .
Now we still need 2 binding votes, We look forward to more votes from IPMCs for
this release.
Can you help me?
Best regards
> 2020年8月19日 上午8:58,JUN
13 matches
Mail list logo