All blockers are resolved.

This vote thread is cancelled.
There is a new vote thread for RC3:
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Apache-Flink-Stateful-Functions-Release-2-0-0-release-candidate-3-td39424.html

On Sat, Mar 28, 2020 at 7:00 PM Tzu-Li (Gordon) Tai <tzuli...@apache.org>
wrote:

> After a check-through on the licenses, there are in total the following 3
> blockers due to licensing issues:
>
> - https://issues.apache.org/jira/browse/FLINK-16841
> - https://issues.apache.org/jira/browse/FLINK-16842
> - https://issues.apache.org/jira/browse/FLINK-16843
>
> Will open a new RC as soon as those are addressed.
>
> On Sat, Mar 28, 2020 at 1:34 AM Tzu-Li (Gordon) Tai <tzuli...@apache.org>
> wrote:
>
>> Hi Hequn,
>>
>> That's a good catch.
>>
>> Unfortunately, the spring boot dependency there, while itself being ASLv2
>> licensed, pulls in other dependencies that are not ASLv2.
>> That would indeed make this problem a blocker.
>>
>> I'll do a thorough check again on the Maven artifacts that do bundle
>> dependencies, before creating a new RC. AFAIK, there should be no more
>> other than:
>> - statefun-flink-distribution
>> - statefun-ridesharing-example-simulator
>>
>> BR,
>> Gordon
>>
>> On Fri, Mar 27, 2020 at 10:41 PM Hequn Cheng <he...@apache.org> wrote:
>>
>>> Thanks Gordon for the release and the nice release checking guide!
>>>
>>> It seems the NOTICE file is missing in the
>>> `statefun-ridesharing-example-simulator` module while it bundles
>>> dependencies like
>>> `org.springframework.boot:spring-boot-loader:2.1.6.RELEASE`.
>>>
>>> Best,
>>> Hequn
>>>
>>> On Fri, Mar 27, 2020 at 3:35 PM Tzu-Li (Gordon) Tai <tzuli...@apache.org
>>> >
>>> wrote:
>>>
>>> > Hi everyone,
>>> >
>>> > Please review and vote on the release candidate #2 for the version
>>> 2.0.0 of
>>> > Apache Flink Stateful Functions,
>>> > as follows:
>>> > [ ] +1, Approve the release
>>> > [ ] -1, Do not approve the release (please provide specific comments)
>>> >
>>> > **Testing Guideline**
>>> >
>>> > You can find here [1] a doc that we can use for collaborating testing
>>> > efforts.
>>> > The listed testing tasks in the doc also serve as a guideline in what
>>> to
>>> > test for this release.
>>> > If you wish to take ownership of a testing task, simply put your name
>>> down
>>> > in the "Checked by" field of the task.
>>> >
>>> > **Release Overview**
>>> >
>>> > As an overview, the release consists of the following:
>>> > a) Stateful Functions canonical source distribution, to be deployed to
>>> the
>>> > release repository at dist.apache.org
>>> > b) Stateful Functions Python SDK distributions to be deployed to PyPI
>>> > c) Maven artifacts to be deployed to the Maven Central Repository
>>> >
>>> > **Staging Areas to Review**
>>> >
>>> > The staging areas containing the above mentioned artifacts are as
>>> follows,
>>> > for your review:
>>> > * All artifacts for a) and b) can be found in the corresponding dev
>>> > repository at dist.apache.org [2]
>>> > * All artifacts for c) can be found at the Apache Nexus Repository [3]
>>> >
>>> > All artifacts are singed with the
>>> > key 1C1E2394D3194E1944613488F320986D35C33D6A [4]
>>> >
>>> > Other links for your review:
>>> > * JIRA release notes [5]
>>> > * source code tag "release-2.0.0-rc2" [6] [7]
>>> >
>>> > **Extra Remarks**
>>> >
>>> > * Part of the release is also official Docker images for Stateful
>>> > Functions. This can be a separate process, since the creation of those
>>> > relies on the fact that we have distribution jars already deployed to
>>> > Maven. I will follow-up with this after these artifacts are officially
>>> > released.
>>> > In the meantime, there is this discussion [8] ongoing about where to
>>> host
>>> > the StateFun Dockerfiles.
>>> > * The Flink Website and blog post is also being worked on (by Marta) as
>>> > part of the release, to incorporate the new Stateful Functions
>>> project. We
>>> > can follow up with a link to those changes afterwards in this vote
>>> thread,
>>> > but that would not block you to test and cast your votes already.
>>> > * Since the Flink website changes are still being worked on, you will
>>> not
>>> > yet be able to find the Stateful Functions docs from there. Here are
>>> the
>>> > links [9] [10].
>>> >
>>> > **Vote Duration**
>>> >
>>> > The vote will be open for at least 72 hours *(target end date is next
>>> > Tuesday, April 31).*
>>> > It is adopted by majority approval, with at least 3 PMC affirmative
>>> votes.
>>> >
>>> > Thanks,
>>> > Gordon
>>> >
>>> > [1]
>>> >
>>> >
>>> https://docs.google.com/document/d/1P9yjwSbPQtul0z2AXMnVolWQbzhxs68suJvzR6xMjcs/edit?usp=sharing
>>> > [2]
>>> https://dist.apache.org/repos/dist/dev/flink/flink-statefun-2.0.0-rc2/
>>> > [3]
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheflink-1340/
>>> > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
>>> > [5]
>>> >
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12346878
>>> > [6]
>>> >
>>> >
>>> https://gitbox.apache.org/repos/asf?p=flink-statefun.git;a=commit;h=14ce58048a3dda792f2329cf14d30aa952f6cb24
>>> > [7] https://github.com/apache/flink-statefun/tree/release-2.0.0-rc2
>>> > [8]
>>> >
>>> >
>>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Creating-a-new-repo-to-host-Stateful-Functions-Dockerfiles-td39342.html
>>> > [9] https://ci.apache.org/projects/flink/flink-statefun-docs-master/
>>> > [10]
>>> https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.0/
>>> >
>>> > TIP: You can create a `settings.xml` file with these contents:
>>> >
>>> > """
>>> > <settings>
>>> >   <activeProfiles>
>>> >     <activeProfile>flink-statefun-2.0.0</activeProfile>
>>> >   </activeProfiles>
>>> >   <profiles>
>>> >     <profile>
>>> >       <id>flink-statefun-2.0.0</id>
>>> >       <repositories>
>>> >         <repository>
>>> >           <id>flink-statefun-2.0.0</id>
>>> >           <url>
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheflink-1340/
>>> > </url>
>>> >         </repository>
>>> >         <repository>
>>> >           <id>archetype</id>
>>> >           <url>
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheflink-1340/
>>> > </url>
>>> >         </repository>
>>> >       </repositories>
>>> >     </profile>
>>> >   </profiles>
>>> > </settings>
>>> > """
>>> >
>>> > And reference that in you maven commands via `--settings
>>> > path/to/settings.xml`.
>>> > This is useful for creating a quickstart based on the staged release
>>> and
>>> > for building against the staged jars.
>>> >
>>>
>>

Reply via email to