I believe this release is complete now. Thank you JB for pushing this release, and everyone else who contributed to it.
On Tue, Aug 22, 2017 at 4:26 PM, Ahmet Altay <al...@google.com> wrote: > Remaining items for closing this release are: > - Move source distribution from dev repository to release repository in > dist.apache.org > Done. > - Finalize the version in JIRA. > Done. > - Announce on user@ and other places. > JB, I think it would be best if you announce this to user@ as the release manager. If you do not have time I will send the announcement message tomorrow. > > On Tue, Aug 22, 2017 at 2:18 PM, Ahmet Altay <al...@google.com> wrote: > >> >> >> On Tue, Aug 22, 2017 at 2:07 PM, Ahmet Altay <al...@google.com> wrote: >> >>> >>> >>> On Tue, Aug 22, 2017 at 12:08 PM, Ahmet Altay <al...@google.com> wrote: >>> >>>> >>>> >>>> On Tue, Aug 22, 2017 at 10:59 AM, Ahmet Altay <al...@google.com> wrote: >>>> >>>>> Thank you JB. >>>>> >>>>> On Mon, Aug 21, 2017 at 11:33 PM, Jean-Baptiste Onofré < >>>>> j...@nanthrax.net> wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> This vote passed with only +1. >>>>>> >>>>>> I'm promoting the artifacts to central and update Jira. >>>>>> >>>>> >>>>> Are you also pushing the PyPI artifacts? Do you want me to do it? >>>>> >>>> >> Let me know if you want me to push to PyPI. >> > > I noticed that the Maven artifacts are published and for parity published > the PyPI packages. > > >> >> >>> >>>>> >>>>> >>>>>> As I'm in vacation can a committer deal with the tag and website or >>>>>> merge ? >>>>>> >>>>> >>>>> Website PR had errors with dead-links. Re-running the test. If it >>>>> fails again, I can merge and we can fix with a follow up PR. >>>>> >>>> >>>> I noticed that pydocs contents are empty (i.e. headers are in there, >>>> but content is missing) in this PR. I am not sure what caused it. What is >>>> the recommendation here, we can do two things: >>>> >>>> a) Drop this PR, and re-create whole documentation again >>>> b) Merge this PR, and create another PR to fix the pydocs. >>>> >>> >>> This is done. I updated the pydocs while merging it. Pydoc generation >>> worked fine for me, I do not know what was the issue. >>> >>> >>>> >>>> >>>>> >>>>> I can do the tagging. >>>>> >>>> >> This is also done. >> >> >>> >>>>> >>>>>> >>>>>> Sorry for this very short e-mail. Thanks all for your vote. >>>>>> >>>>>> Regards >>>>>> JB >>>>>> >>>>>> >>>>>> On Aug 18, 2017, 18:43, at 18:43, "Jean-Baptiste Onofré" < >>>>>> j...@nanthrax.net> wrote: >>>>>> >Hi >>>>>> > >>>>>> >I'm in vacation so I'm looking for a decent Internet connection to >>>>>> >finalize the release. >>>>>> > >>>>>> >I keep you posted. >>>>>> > >>>>>> >Regards >>>>>> >JB >>>>>> > >>>>>> >On Aug 18, 2017, 17:48, at 17:48, Eugene Kirpichov >>>>>> ><kirpic...@google.com.INVALID> wrote: >>>>>> >>Hi JB, >>>>>> >> >>>>>> >>Any updates on finalizing the release? >>>>>> >> >>>>>> >>Thanks. >>>>>> >> >>>>>> >>On Thu, Aug 17, 2017 at 5:42 AM Aljoscha Krettek < >>>>>> aljos...@apache.org> >>>>>> >>wrote: >>>>>> >> >>>>>> >>> (Belated) +1 >>>>>> >>> >>>>>> >>> * verified signatures >>>>>> >>> * verified that Quickstart works with Flink Runner >>>>>> >>> >>>>>> >>> > On 16. Aug 2017, at 20:41, Robert Bradshaw >>>>>> >><rober...@google.com.INVALID> >>>>>> >>> wrote: >>>>>> >>> > >>>>>> >>> > +1 binding >>>>>> >>> > >>>>>> >>> > (I've been on vacation as well.) >>>>>> >>> > >>>>>> >>> > On Wed, Aug 16, 2017 at 8:50 AM, Lukasz Cwik >>>>>> >><lc...@google.com.invalid> >>>>>> >>> wrote: >>>>>> >>> >> Back from vacation. >>>>>> >>> >> >>>>>> >>> >> +1 binding >>>>>> >>> >> >>>>>> >>> >> BEAM-2671 has been marked for 2.2.0 release. >>>>>> >>> >> >>>>>> >>> >> >>>>>> >>> >> >>>>>> >>> >> On Wed, Aug 16, 2017 at 2:08 AM, Kobi Salant >>>>>> >><kobi.sal...@gmail.com> >>>>>> >>> wrote: >>>>>> >>> >> >>>>>> >>> >>> Hi, >>>>>> >>> >>> >>>>>> >>> >>> Spark runner was tested with word count example and a more >>>>>> >>complex >>>>>> >>> session >>>>>> >>> >>> based application on a yarn cluster. >>>>>> >>> >>> Both application run successfully so we can say that spark >>>>>> >runner >>>>>> >>> passed >>>>>> >>> >>> the sanity tests needed. >>>>>> >>> >>> >>>>>> >>> >>> Still there is an open ticket >>>>>> >>> >>> https://issues.apache.org/jira/browse/BEAM-2671 which Stas is >>>>>> >>working >>>>>> >>> on >>>>>> >>> >>> and its implications should be taken into consideration >>>>>> >regarding >>>>>> >>the >>>>>> >>> >>> release. >>>>>> >>> >>> >>>>>> >>> >>> Regards >>>>>> >>> >>> Kobi >>>>>> >>> >>> >>>>>> >>> >>> 2017-08-16 5:02 GMT+03:00 Eugene Kirpichov >>>>>> >>> <kirpic...@google.com.invalid>: >>>>>> >>> >>> >>>>>> >>> >>>> Hey all, >>>>>> >>> >>>> >>>>>> >>> >>>> Seems like we're missing one more affirmative vote from a PMC >>>>>> >>member >>>>>> >>> (so >>>>>> >>> >>>> far we have JB and Ahmet) to proceed with the release. >>>>>> >>> >>>> >>>>>> >>> >>>> On Mon, Aug 14, 2017 at 9:30 AM Ahmet Altay >>>>>> >><al...@google.com.invalid >>>>>> >>> > >>>>>> >>> >>>> wrote: >>>>>> >>> >>>> >>>>>> >>> >>>>> On Mon, Aug 14, 2017 at 6:32 AM, Ismaël Mejía >>>>>> >><ieme...@gmail.com> >>>>>> >>> >>> wrote: >>>>>> >>> >>>>> >>>>>> >>> >>>>>> +1 (non-binding) >>>>>> >>> >>>>>> >>>>>> >>> >>>>>> - Validated signatures OK >>>>>> >>> >>>>>> - mvn clean verify -Prelease on both OpenJDK 1.7 and Oracle >>>>>> >>JDK 8 >>>>>> >>> >>> with >>>>>> >>> >>>>>> the docker development images (WIP), both OK >>>>>> >>> >>>>>> - Run WordCount on local Flink and Spark runners OK >>>>>> >>> >>>>>> >>>>>> >>> >>>>>> Everything looks nice, only one minor thing (not blocking >>>>>> at >>>>>> >>all). >>>>>> >>> >>> The >>>>>> >>> >>>>>> proto generated files for python are not cleaned correctly >>>>>> >and >>>>>> >>this >>>>>> >>> >>>>>> causes the validation to complain because the maven rat >>>>>> >plugin >>>>>> >>does >>>>>> >>> >>>>>> not find the apache headers on the files (this happens if >>>>>> >you >>>>>> >>> >>> execute >>>>>> >>> >>>>>> mvn clean verify -Prelease immediately after the >>>>>> validation). >>>>>> >>> >>>>>> >>>>>> >>> >>>>> >>>>>> >>> >>>>> Ismaël, could you create a JIRA issue for this (to be fixed >>>>>> at >>>>>> >>a >>>>>> >>> future >>>>>> >>> >>>>> release)? >>>>>> >>> >>>>> >>>>>> >>> >>>>> >>>>>> >>> >>>>>> >>>>>> >>> >>>>>> On Sun, Aug 13, 2017 at 6:52 AM, Jean-Baptiste Onofré < >>>>>> >>> >>> j...@nanthrax.net >>>>>> >>> >>>>> >>>>>> >>> >>>>>> wrote: >>>>>> >>> >>>>>>> +1 (binding) >>>>>> >>> >>>>>>> >>>>>> >>> >>>>>>> I do my own tests and casting my own vote ;) >>>>>> >>> >>>>>>> >>>>>> >>> >>>>>>> Regards >>>>>> >>> >>>>>>> JB >>>>>> >>> >>>>>>> >>>>>> >>> >>>>>>> On 08/09/2017 07:08 AM, Jean-Baptiste Onofré wrote: >>>>>> >>> >>>>>>>> >>>>>> >>> >>>>>>>> Hi everyone, >>>>>> >>> >>>>>>>> >>>>>> >>> >>>>>>>> Please review and vote on the release candidate #3 for >>>>>> the >>>>>> >>version >>>>>> >>> >>>>>> 2.1.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 >>>>>> C8282E76 >>>>>> >>[3], >>>>>> >>> >>>>>>>> * all artifacts to be deployed to the Maven Central >>>>>> >>Repository >>>>>> >>> >>> [4], >>>>>> >>> >>>>>>>> * source code tag "v2.1.0-RC3" [5], >>>>>> >>> >>>>>>>> * website pull request listing the release and publishing >>>>>> >>the API >>>>>> >>> >>>>>>>> reference manual [6]. >>>>>> >>> >>>>>>>> * Python artifacts are deployed along with the source >>>>>> >>release to >>>>>> >>> >>> the >>>>>> >>> >>>>>>>> dist.apache.org [2]. >>>>>> >>> >>>>>>>> >>>>>> >>> >>>>>>>> The vote will be open for at least 72 hours. It is >>>>>> adopted >>>>>> >>by >>>>>> >>> >>>> majority >>>>>> >>> >>>>>>>> approval, with at least 3 PMC affirmative votes. >>>>>> >>> >>>>>>>> >>>>>> >>> >>>>>>>> Thanks, >>>>>> >>> >>>>>>>> JB >>>>>> >>> >>>>>>>> >>>>>> >>> >>>>>>>> [1] >>>>>> >>> >>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >>>>>> >>> >>>>>> projectId=12319527&version=12340528 >>>>>> >>> >>>>>>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.1.0/ >>>>>> >>> >>>>>>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS >>>>>> >>> >>>>>>>> [4] https://repository.apache.org/content/repositories/ >>>>>> >>> >>>>>> orgapachebeam-1020/ >>>>>> >>> >>>>>>>> [5] https://github.com/apache/beam/tree/v2.1.0-RC3 >>>>>> >>> >>>>>>>> [6] https://github.com/apache/beam-site/pull/270 >>>>>> >>> >>>>>>> >>>>>> >>> >>>>>>> >>>>>> >>> >>>>>>> -- >>>>>> >>> >>>>>>> Jean-Baptiste Onofré >>>>>> >>> >>>>>>> jbono...@apache.org >>>>>> >>> >>>>>>> http://blog.nanthrax.net >>>>>> >>> >>>>>>> Talend - http://www.talend.com >>>>>> >>> >>>>>> >>>>>> >>> >>>>> >>>>>> >>> >>>> >>>>>> >>> >>> >>>>>> >>> >>>>>> >>> >>>>>> >>>>> >>>>> >>>> >>> >> >
