Thanks,
I'm on it.
By the way, on the RC1, I did the python zip cleanup by hand (removing .eggs,
.tox, etc).
Regards
JB
On 07/15/2017 08:42 AM, Sourabh Bajaj wrote:
Hi JB,
https://github.com/apache/beam/pull/3563 cherrypicks the fix for BEAM-2595
to the release branch, please review.
I wasn't able to reproduce the issue in BEAM-2271 but was hoping
https://github.com/apache/beam/pull/3563 will fix it, so would be great if
you can take a look at it as well.
Thanks
Sourabh
On Fri, Jul 14, 2017 at 10:30 PM Jean-Baptiste Onofré <[email protected]>
wrote:
Hi Ahmet,
sorry I missed those Jira.
Can you help to cherry-pick and fix both issues on release-2.1.0 branch ?
The release guide already mention to check to open Jira on the release
target. I
just missed these two Jira, sorry about that.
I don't think an additional list is required.
I will cancel this vote and cut a RC2 as soon as BEAM-2595 and BEAM-2771
are
addressed.
Thanks,
Regards
JB
On 07/14/2017 06:15 AM, Ahmet Altay wrote:
-1
Thank you JB. Unfortunately I do not want to approve this RC :(. My
reason
is that there are two open issues in the burndown list (
https://s.apache.org/beam-2.1.0-burndown). I think we should either fix
them or explicitly move them out of the list. BEAM-2595 is a regression
in
usability (not in functionality), and it is fixed in master. We could
cherry pick that. BEAM-2271 is an improvement to the release process. I
would prefer fixing the process now instead of the next release cycle.
However, if we want to release sooner, it is fine to clean the zip files
manually.
Another point I would like to raise is about the validation process.
During
2.0 release we created a list of things to validate before that release.
Should we re-use that list for this and subseqeuent releases?
Ahmet
On Tue, Jul 11, 2017 at 6:02 AM, Jean-Baptiste Onofré <[email protected]>
wrote:
Hi everyone,
Please review and vote on the release candidate #1 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-RC1" [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?proje
ctId=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-1018/
[5] https://github.com/apache/beam/tree/v2.1.0-RC1
[6] https://github.com/apache/beam-site/pull/270
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
