Thank you every one.
The vote has already opened for at least 72 hours and necessary number of
votes are reached.
Release vote is passed, I will sent a new thread to statistics all
participant mentors and paste thread link here.
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
Sorry, Let me correct. I will statistics vote result here, not for new
thread.
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
zhangli...@apache.org 于2019年4月21日周日 下午4:46写道：
> Thank you every one.
> The vote has already opened for at least 72 hours and necessary number of
We’ve received 3 +1 binding votes and 0 +1 non-binding vote:
+1 binding, Willen Jiang
+1 binding, Sheng Wu
+1 binding, Gosling Von
Thank you everyone for taking the time to review the release and help us.
I will process to publish the release and send ANNOUNCE.
--
Liang Zhang (
Hi,
> The vote has already opened for at least 72 hours and necessary number of
> votes are reached.
There’s only 2 +1 votes I count here and you need 3 for a vote to pass. Did you
have the rIPMC member vote on your dev list?
Thanks,
Justin
--
Hi Justin
I saw three +1 votes, including two mentors, Willem and Gosling, and I
gave +1 too.
Sheng Wu 吴晟
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108
Justin Mclean 于2019年4月21日周日 下午4:54写道：
> Hi,
>
> > The vote has already opened for at least 72 hours and necessary number of
Hi,
> I saw three +1 votes, including two mentors, Willem and Gosling, and I
> gave +1 too.
AFACS Willem's vote didn’t end up in this thread [1] but ended up on your dev
list [2]. I think this confusion happed as you sent the initial vote email to
both lists.
Thanks,
Justin
1.
https://lists.
Hi Justin
Yes. You are right. Sorry, my misread.
I saw the following mail from Willem, but this mail goes to dev@. My mail
achieved them in the same thread(maybe because of the title).
```
+1 (binding)
Forward my VOTE from dev@ list
```
Hi Liang Zhang
Please notice this, if face this again, ple
Hi,
> I saw the following mail from Willem, but this mail goes to dev@. My mail
> achieved them in the same thread(maybe because of the title).
No issue he vote is still binding and you have the 3 +1 votes, it just good to
clear :-)
Thanks,
Justin
-
Thank for your remind, I will remind mentor to make vote clear next time.
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
Justin Mclean 于2019年4月21日周日 下午5:50写道：
> Hi,
>
> > I saw the following mail from Willem, but this mail goes to dev@. My
> mail
> > achieved them in the
Hi all,
Apache ShardingSphere (incubating) Team is glad to announce the first
release of Apache ShardingSphere Incubating 4.0.0-RC1.
ShardingSphere is an open-source ecosystem consisted of a set of
distributed database middleware solutions, including 2 independent
products, Sharding-JDBC & Shardi
Congrats on the release, however there are some issues with the announce mail.
1) it should include the Incubation disclaimer.
2) Download links must not use dist.apache.org. They must point to a
download page.
Perhaps simplify the description of the product; IMO there's too much
detail for a gen
Thank you for suggestion. I will remind issues next time.
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
sebb 于2019年4月21日周日 下午7:22写道：
> Congrats on the release, however there are some issues with the announce
> mail.
>
> 1) it should include the Incubation disclaimer.
> 2
Hi Liang
The introduction is a little too long. One or two sentences for project
description is good and clear for everyone.
And be good for clear project landscape.
Let's start a discussion in dev mail.
zhangli...@apache.org 于2019年4月21日 周日下午6:52写道：
> Hi all,
>
> Apache ShardingSphere (incubati
Hi Justin,
> On Apr 20, 2019, at 3:05 PM, Justin Mclean wrote:
>
> H,
>
> So this is the only date you want to change:
>> 1. PME + 5 days - Podling reports due by end of day
>
> My concern with that is that will it give mentors and the IPMC time to
> review and sign off?
My concern with th
Hi,
I am thinking why spring-boot-starter-data-jpa depends on LGPL
licensed library "hibernate-core", and can still be Apache 2.0
licensed.
I am reading [1]. In section 5 it says:
A program that contains no derivative of any portion of the Library,
but is designed to work with the Library by bein
Hi.
> 1. Stop distribute the binary of incubator-dubbo-admin
I think "stop distribute the binary" would NOT change the fact the source
release could lead users to use `hiberante-core`. I doubt this is an option.
Also based on the license issue, you should consider canceling this vote,
and move t
Hi,
I’ve went through and organised teh incubator wiki a little;
- Reports page have been organised user [1]. Some are missing I’ve raise an
INFRA JIRA for this.
- A lot off pages can be deleted I’ve moved these to “To Delete” [2]
- People have been moved to [3]. I think the majority of these can
Hi,
> I am thinking why spring-boot-starter-data-jpa depends on LGPL
> licensed library "hibernate-core", and can still be Apache 2.0
> licensed.
That may be the case for a non ASF project, but it is ASF policy to not depends
on GPL code. [1][2]
In short "The Apache Software Foundation does not
Hi,
> My concern with the original dates is that as written, there is only one day
> for the podling to prepare the report.
The bulk of the report could be prepped before that date, as it unlikely in the
majority of cases and anything board worthy happened in the last couple of days
of teh mon
Hi,
Can someone please confirm this is the case and the vote was not just on the
GitHub repo?
> Assuming the artefact voted on was [1].
>
> 1.
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.11.0-incubating-rc2/
Thanks,
Justin
--
Hi,
On Mon, Apr 22, 2019 at 8:18 AM Justin Mclean wrote:
>
> Hi,
>
> > I am thinking why spring-boot-starter-data-jpa depends on LGPL
> > licensed library "hibernate-core", and can still be Apache 2.0
> > licensed.
>
> That may be the case for a non ASF project, but it is ASF policy to not
> dep
HI,
> However, LGPL software does not fit into this case, because in [2]
> section 5, it says linking to a LGPL software is not considered to
> create a derivative work.
It still places restriction above and beyond what the ALv2 does and that why
it’s listing in Category X. [1]
> Basically I am
Hi,
On Sun, Apr 21, 2019 at 11:11 PM Sheng Wu wrote:
>
> Hi.
>
> > 1. Stop distribute the binary of incubator-dubbo-admin
>
> I think "stop distribute the binary" would NOT change the fact the source
> release could lead users to use `hiberante-core`. I doubt this is an option.
That option is ba
On Mon, Apr 22, 2019 at 10:17 AM Justin Mclean wrote:
>
> HI,
>
> > However, LGPL software does not fit into this case, because in [2]
> > section 5, it says linking to a LGPL software is not considered to
> > create a derivative work.
>
> It still places restriction above and beyond what the ALv2
Hi,
Interesting to note that has been discuss at the board level but no resolution
was passed. This was back in 2005 so I’m not aware of the history or why the
resolution wasn’t passed [1] a search of the mailing lists from that time may
provide an answer.
Thanks,
Justin
1,https://www.apache.
Just an update here is that we are done with DNS, LDAP, mailing lists and
name search (we didn't gate on it, but it finished before other things
anyhow). We are making sure everyone has their ICLAs and is subscribed to
the lists and will discuss next steps there. I believe the need to discuss
DataS
Hi
> That option is based on my understanding that linking to
> "hibernate-core" does not create a derivative work of
> "hibernate-core".
> Yes, when compiling the source code and run the incubator-dubbo-admin
> code, the hibernate-core binary will be included, this
> will create a derivative work
Hi,
Just FYI:
On Mon, Apr 22, 2019 at 10:22 AM Justin Mclean wrote:
>
> Hi,
>
> Interesting to note that has been discuss at the board level but no
> resolution was passed. This was back in 2005 so I’m not aware of the history
> or why the resolution wasn’t passed [1] a search of the mailing l
Hi,
> From my understanding, I don't see any issues that stop us from
> allowing product depend on LGPL licensed software…
Expect that it is against ASF policy as it listed in Category X, and podlings
(and TLP) are expected to follow ASF legal / release policy. Please ask why on
legal discuss a
Hi,
On Mon, Apr 22, 2019 at 12:20 PM Justin Mclean wrote:
>
> Hi,
>
> > From my understanding, I don't see any issues that stop us from
> > allowing product depend on LGPL licensed software…
>
> Expect that it is against ASF policy as it listed in Category X, and podlings
> (and TLP) are expecte
Hi All,
I've excluded the `hibernate-core` dependency and verified as follows:
$ mvn license:add-third-party -Dlicense.useMissingFile
$ cat dubbo-admin-server/target/generated-sources/license/THIRD-PARTY.txt |
grep "General Public License"
here is the output
(Eclipse Public License -
31 matches
Mail list logo
