On Tue, Sep 1, 2020 at 10:41 AM Daniel Oliveira <[email protected]> wrote: > > I should probably call out that Dataflow containers aren't built yet (I will > be building them today), so testing of Dataflow should probably wait until > tomorrow. > > > If Java 11 was used to build the release artifacts, does this create any > > backwards-compatibility challenges for Java 8 users? > > It's definitely possible, but I only realized this at the end of the process, > so I elected to just finish the release candidate rather than restarting the > whole process, so we can find out in testing.
I am concerned testing alone may not cover the issues in corner cases that this may cause (and users would hit). I'd prefer we just re-build it with Java 8 to be safe. (That doesn't preclude validating the artifacts in other ways in the meantime.) > On Tue, Sep 1, 2020 at 9:14 AM Valentyn Tymofieiev <[email protected]> > wrote: >> >> > * Java artifacts were built with Maven 3.6.3 and OpenJDK 11.0.7. >> >> If Java 11 was used to build the release artifacts, does this create any >> backwards-compatibility challenges for Java 8 users? >> >> On Mon, Aug 31, 2020 at 8:59 PM Daniel Oliveira <[email protected]> >> wrote: >>> >>> Hi everyone, >>> Please review and vote on the release candidate #1 for the version 2.24.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 to be deployed to dist.apache.org [2], >>> which is signed with the key with fingerprint >>> D0E7B69D911ADA3C0482BAA1C4E6B2F8C71D742F [3], >>> * all artifacts to be deployed to the Maven Central Repository [4], >>> * source code tag "v2.24.0-RC1" [5], >>> * website pull request listing the release [6], publishing the API >>> reference manual [7], and the blog post [8]. >>> * Java artifacts were built with Maven 3.6.3 and OpenJDK 11.0.7. >>> * Python artifacts are deployed along with the source release to the >>> dist.apache.org [2]. >>> * Validation sheet with a tab for 2.24.0 release to help with validation >>> [9]. >>> * Docker images published to Docker Hub [10]. >>> >>> The vote will be open for at least 72 hours. It is adopted by majority >>> approval, with at least 3 PMC affirmative votes. >>> >>> Thanks, >>> Release Manager >>> >>> [1] >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12347146 >>> [2] https://dist.apache.org/repos/dist/dev/beam/2.24.0/ >>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS >>> [4] https://repository.apache.org/content/repositories/orgapachebeam-1108/ >>> [5] https://github.com/apache/beam/tree/v2.24.0-RC1 >>> [6] https://github.com/apache/beam/pull/12743 >>> [7] https://github.com/apache/beam-site/pull/607 >>> [8] https://github.com/apache/beam/pull/12745 >>> [9] >>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1432428331 >>> [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image
