[VOTE] Release 1.6.0, release candidate #3

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release 1.6.0, release candidate #3

Till Rohrmann
Hi everyone,
Please review and vote on the release candidate #3 for the version 1.6.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.6.0-rc3" [5],

Please use this document for coordinating testing efforts: [6]

The vote will be shortened since we only added minor fixes on top of the RC
2. It will close on Wednesday 6:30pm CET. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Your friendly Release Manager

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1177
[5] https://github.com/apache/flink/tree/release-1.6.0-rc3
[6]
https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing

Pro-tip: you can create a settings.xml file with these contents:

<settings>
<activeProfiles>
  <activeProfile>flink-1.6.0</activeProfile>
</activeProfiles>
<profiles>
  <profile>
    <id>flink-1.6.0</id>
    <repositories>
      <repository>
        <id>flink-1.6.0</id>
        <url>

https://repository.apache.org/content/repositories/orgapacheflink-1177/
        </url>
      </repository>
      <repository>
        <id>archetype</id>
        <url>

https://repository.apache.org/content/repositories/orgapacheflink-1177/
        </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 | Threaded
Open this post in threaded view
|

Re: [VOTE] Release 1.6.0, release candidate #3

Andrey Zagrebin
Hi everyone,

After careful consideration, I think that it makes sense to change the order of serialisation for state values with TTL. It will simplify further optimisations and feature improvements.

If it is still possible, I would ask to include this PR to the release candidate:
https://github.com/apache/flink/pull/6510 <https://github.com/apache/flink/pull/6510>
This change will help to avoid compatibility issues in future.

Sorry for the short notice.

Thanks,
Andrey

> On 7 Aug 2018, at 10:01, Till Rohrmann <[hidden email]> wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.6.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint 1F302569A96CFFD5 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.6.0-rc3" [5],
>
> Please use this document for coordinating testing efforts: [6]
>
> The vote will be shortened since we only added minor fixes on top of the RC
> 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Your friendly Release Manager
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> [4] https://repository.apache.org/content/repositories/orgapacheflink-1177
> [5] https://github.com/apache/flink/tree/release-1.6.0-rc3
> [6]
> https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing
>
> Pro-tip: you can create a settings.xml file with these contents:
>
> <settings>
> <activeProfiles>
>  <activeProfile>flink-1.6.0</activeProfile>
> </activeProfiles>
> <profiles>
>  <profile>
>    <id>flink-1.6.0</id>
>    <repositories>
>      <repository>
>        <id>flink-1.6.0</id>
>        <url>
>
> https://repository.apache.org/content/repositories/orgapacheflink-1177/
>        </url>
>      </repository>
>      <repository>
>        <id>archetype</id>
>        <url>
>
> https://repository.apache.org/content/repositories/orgapacheflink-1177/
>        </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 | Threaded
Open this post in threaded view
|

Re: [VOTE] Release 1.6.0, release candidate #3

Till Rohrmann
Thanks for reporting this issue Andrey. I think it would be good to include
this change into the 1.6 release in order to avoid additional backwards
compatibility work in the future. Therefore, I cancel this RC and will
publish a new RC as soon as we have merged the pull request #6510.

Cheers,
Till

On Tue, Aug 7, 2018 at 2:28 PM Andrey Zagrebin <[hidden email]>
wrote:

> Hi everyone,
>
> After careful consideration, I think that it makes sense to change the
> order of serialisation for state values with TTL. It will simplify further
> optimisations and feature improvements.
>
> If it is still possible, I would ask to include this PR to the release
> candidate:
> https://github.com/apache/flink/pull/6510 <
> https://github.com/apache/flink/pull/6510>
> This change will help to avoid compatibility issues in future.
>
> Sorry for the short notice.
>
> Thanks,
> Andrey
>
> > On 7 Aug 2018, at 10:01, Till Rohrmann <[hidden email]> wrote:
> >
> > Hi everyone,
> > Please review and vote on the release candidate #3 for the version 1.6.0,
> > as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> >
> > The complete staging area is available for your review, which includes:
> > * JIRA release notes [1],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 1F302569A96CFFD5 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.6.0-rc3" [5],
> >
> > Please use this document for coordinating testing efforts: [6]
> >
> > The vote will be shortened since we only added minor fixes on top of the
> RC
> > 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Your friendly Release Manager
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1177
> > [5] https://github.com/apache/flink/tree/release-1.6.0-rc3
> > [6]
> >
> https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing
> >
> > Pro-tip: you can create a settings.xml file with these contents:
> >
> > <settings>
> > <activeProfiles>
> >  <activeProfile>flink-1.6.0</activeProfile>
> > </activeProfiles>
> > <profiles>
> >  <profile>
> >    <id>flink-1.6.0</id>
> >    <repositories>
> >      <repository>
> >        <id>flink-1.6.0</id>
> >        <url>
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
> >        </url>
> >      </repository>
> >      <repository>
> >        <id>archetype</id>
> >        <url>
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
> >        </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 | Threaded
Open this post in threaded view
|

Re: [VOTE] Release 1.6.0, release candidate #3

Till Rohrmann
FYI: The issue belonging to PR #6510 is
https://issues.apache.org/jira/browse/FLINK-10095.

On Tue, Aug 7, 2018 at 2:51 PM Till Rohrmann <[hidden email]> wrote:

> Thanks for reporting this issue Andrey. I think it would be good to
> include this change into the 1.6 release in order to avoid additional
> backwards compatibility work in the future. Therefore, I cancel this RC and
> will publish a new RC as soon as we have merged the pull request #6510.
>
> Cheers,
> Till
>
> On Tue, Aug 7, 2018 at 2:28 PM Andrey Zagrebin <[hidden email]>
> wrote:
>
>> Hi everyone,
>>
>> After careful consideration, I think that it makes sense to change the
>> order of serialisation for state values with TTL. It will simplify further
>> optimisations and feature improvements.
>>
>> If it is still possible, I would ask to include this PR to the release
>> candidate:
>> https://github.com/apache/flink/pull/6510 <
>> https://github.com/apache/flink/pull/6510>
>> This change will help to avoid compatibility issues in future.
>>
>> Sorry for the short notice.
>>
>> Thanks,
>> Andrey
>>
>> > On 7 Aug 2018, at 10:01, Till Rohrmann <[hidden email]> wrote:
>> >
>> > Hi everyone,
>> > Please review and vote on the release candidate #3 for the version
>> 1.6.0,
>> > as follows:
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> >
>> > The complete staging area is available for your review, which includes:
>> > * JIRA release notes [1],
>> > * the official Apache source release and binary convenience releases to
>> be
>> > deployed to dist.apache.org [2], which are signed with the key with
>> > fingerprint 1F302569A96CFFD5 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "release-1.6.0-rc3" [5],
>> >
>> > Please use this document for coordinating testing efforts: [6]
>> >
>> > The vote will be shortened since we only added minor fixes on top of
>> the RC
>> > 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > Your friendly Release Manager
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
>> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
>> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapacheflink-1177
>> > [5] https://github.com/apache/flink/tree/release-1.6.0-rc3
>> > [6]
>> >
>> https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing
>> >
>> > Pro-tip: you can create a settings.xml file with these contents:
>> >
>> > <settings>
>> > <activeProfiles>
>> >  <activeProfile>flink-1.6.0</activeProfile>
>> > </activeProfiles>
>> > <profiles>
>> >  <profile>
>> >    <id>flink-1.6.0</id>
>> >    <repositories>
>> >      <repository>
>> >        <id>flink-1.6.0</id>
>> >        <url>
>> >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
>> >        </url>
>> >      </repository>
>> >      <repository>
>> >        <id>archetype</id>
>> >        <url>
>> >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
>> >        </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.
>>
>>