+1.
I checked
The artifacts has incubating in the name.
There is no binary in the release kit.
signature and hash is OK
DISCLAIMER file exists
LICENSE and NOTICE looks good to me.
There is a license notice section in the README file need to be
polished, I think by default build we should exclude
Hi,
I put up suggested text changes for an incubator disclaimer here [1]. Comments
and feedback welcome. Text changes have been highlighted in yellow.
Note that a disclaimer can’t remove any licence or other rights a user may
have, the intent here it to just inform them that some podling releas
Hi,
+1 (binding)
I checked:
- incubating in name
- signature and hashes fine
- DISCLAIMER exists
- LICENSE has minor issue (see below)
- NOTICE is fine
- all ASF files have correct headers
As noted above the LICENSE file has incorrect copyright line in the license
appendix.
Thanks,
Justin
Hi,
+1 (binding)
I checked:
- incubating in name
- DISCLAIMER exists
- LICENSE has some minor issues (see below)
- NOTICE is fine
- ASF file have ASF headers
- No unexpected binary files
- I didn’t compile as I’m on an unsupported platform
LICENSE is missing:
- UTF-8 library [1][2]
- These files
Hi Willem:
Thank you for your check.
We will change the default building options of some libraries which License are
not compatible with ASL, such as Mysql, to false
on next release.
> 在 2019年6月29日，下午5:58，Willem Jiang 写道：
>
> +1.
>
> I checked
> The artifacts has incubating in the name.
> T
Hi,
Mentors, if you not done so, can you please kindly remind your podlings that
reports are due in a few days. In particular for the following podlings:
Livy
Milagro
Tuweni
Amaterasu
Gobblin
BatchEE
Annotator
Rya
There are also two podlings missing reports which failed to report last month:
DLa
Hi Justin
Thank you for your check.
License problem is always make us confused. So we are going to take a deep dive
into the License.
And all of these issues will be solved or clearly declared in next release.
> 在 2019年6月30日，上午8:53，Justin Mclean 写道：
>
> Hi,
>
> +1 (binding)
>
> I checked:
> We will change the default building options of some libraries which
License are not compatible with ASL, such as Mysql, to false
on next release.
Just a reminder.
For this kind of dependency, you also should make this library as optional
in your feature. Such as for MySQL, should have a default
Hi,
I put down some thoughts to help podling expectations and list some of the
issues a podling may face on it’s incubating journey. [1] Feedback and edits
welcome.
Most projects do not run into serious issues or are good at handling any issue
that do crop up. I think it would be a good idea t
Hi Justin
I like this list.
One suggestion,
In You will need to change the way you build and distribute software
> For instance, you now need to vote on releases over a 72 whole cycle, and
> also have the IPMC vote on your releases.
You need 72 hours pod inside vote, and IPMC vote take at lea
Hi Justin,
Thanks for the review!
RE License appendix:
Is it just the Copyright symbol that’s incorrect? Or do you see something else.
Just checking so that I know what to fix. Its the only thing I can see as
different from [1]
reads as follwos:
APPENDIX: How to apply the Apache License t
crap. Sorry, posts on wrong thread!
> On Jun 30, 2019, at 12:13 AM, Joshua Poore wrote:
>
> Hi Justin,
>
> Thanks for the review!
>
> RE License appendix:
>
> Is it just the Copyright symbol that’s incorrect? Or do you see something
> else. Just checking so that I know what to fix. Its the o
Hi Justin,
Thanks for the review!
RE License appendix:
Is it just the Copyright symbol that’s incorrect? Or do you see something else.
Just checking so that I know what to fix. Its the only thing I can see as
different from [1]
reads as follwos:
APPENDIX: How to apply the Apache License to
Hi,
> In You will need to change the way you build and distribute software
>> For instance, you now need to vote on releases over a 72 whole cycle, and
>> also have the IPMC vote on your releases.
Thanks for the suggestion, I’ll update that,. BTW I wasn’t trying to make it
comprehensive or repe
HI,
> Is it just the Copyright symbol that’s incorrect? Or do you see something
> else. Just checking so that I know what to fix. Its the only thing I can see
> as different from [1]
Sorry, incorrect to probably not teh right word. I just noticed it was
different to the standard one. Probably
You are better about polishing English words than me😄
The point is only, I received many feedback about the long release
procedure is unexpected.
Justin Mclean 于2019年6月30日 周日下午1:13写道：
> Hi,
>
> > In You will need to change the way you build and distribute software
> >> For instance, you now need
16 matches
Mail list logo
