Ahmet, Yes in a comment in this ticket
https://issues.apache.org/jira/browse/BEAM-6292 I supposed there were cherry
picks.Thanks for the confirmation !
No problem about not having cherry picked these PRs they were not release
blockers. It is just that these features were
announced for 2.11 in
I agree this is a good idea. I used the same technique for 2.11 blog post
(JIRA release notes -> editorialized list + diffed the dependencies).
On Mon, Mar 11, 2019 at 1:40 PM Kenneth Knowles wrote:
> That is a good idea. The blog post is probably the main avenue where folks
> will find out
That is a good idea. The blog post is probably the main avenue where folks
will find out about new features or big fixes.
When I did 2.10.0 I just used the automated Jira release notes and pulled
out significant things based on my judgment. I would also suggest that our
Jira hygiene could be
Ahmet, thanks managing the release!
I have a suggestion (not specific to only this release):
The release blogs could be more useful to users. In this case, we have a
long list of dependency updates on the top, but probably the improvements
and features section should come first. I was also very
I updated the JIRAs for these two PRs to set the fix version correctly as
2.12.0. That should fix the release notes issue.
On Mon, Mar 11, 2019 at 10:44 AM Ahmet Altay wrote:
> Hi Etienne,
>
> I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST --
> github timestamp). Release
Hi Etienne,
I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST --
github timestamp). Release tag, as you pointed out, points to a commit on
Feb 25, 2019 11:48 PM PST. And that is a commit on the release branch.
After cutting the release branch, I only merged cherry picks from
Thank you for the additional votes and validations.
Update: Binaries are pushed. Website updates are blocked on an issue that
is preventing beam-site changes to be synced the beam website.
(INFRA-17953). I am waiting for that to be resolved before sending an
announcement.
On Mon, Mar 4, 2019 at
I see the vote has passed, but +1 (binding) from me as well.
On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré wrote:
>
> +1 (binding)
>
> Tested with beam-samples.
>
> Regards
> JB
>
> On 26/02/2019 10:40, Ahmet Altay wrote:
> > Hi everyone,
> >
> > Please review and vote on the release
+1 (binding)
Tested with beam-samples.
Regards
JB
On 26/02/2019 10:40, Ahmet Altay wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version
> 2.11.0, as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific
Excellent thank you Ahmet and all involved!!!
On Fri, Mar 1, 2019, 7:23 AM Ahmet Altay wrote:
> Thank you everyone for voting.
>
> The vote has passed with 5 supportive +1 votes, 4 of which are binding PMC
> votes:
>
> * Maximilian Michels
> * Reuven Lax
> * Kenneth Knowles
> * Ahmet Altay
>
>
Thank you everyone for voting.
The vote has passed with 5 supportive +1 votes, 4 of which are binding PMC
votes:
* Maximilian Michels
* Reuven Lax
* Kenneth Knowles
* Ahmet Altay
I will proceed with release finalization steps.
Ahmet
On Fri, Mar 1, 2019 at 6:59 AM Ahmet Altay wrote:
> +1
+1 (binding)
On Tue, Feb 26, 2019 at 9:18 PM Kenneth Knowles wrote:
> +1 (binding)
>
> Ran run_rc_validation.sh and said "yes" to everything up to one mobile
> gaming example. I did not get to the Python tests towards the end of the
> script (it is the same as last RC anyhow? I did not verify
+1 (binding)
Ran run_rc_validation.sh and said "yes" to everything up to one mobile
gaming example. I did not get to the Python tests towards the end of the
script (it is the same as last RC anyhow? I did not verify this)
On Tue, Feb 26, 2019 at 2:16 PM Charles Chen wrote:
> Thank you, +1. I
+1 (binding)
On Tue, Feb 26, 2019 at 2:16 PM Charles Chen wrote:
> Thank you, +1. I tested Python 3 support in batch and streaming mode
> (using wordcount and streaming wordcount) on both DirectRunner and
> DataflowRunner.
>
> On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
>
Thank you, +1. I tested Python 3 support in batch and streaming mode
(using wordcount and streaming wordcount) on both DirectRunner and
DataflowRunner.
On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis
wrote:
> +1.
> (Same rational as my earlier post for RC1).
>
> On Tue, Feb 26, 2019 at
+1.
(Same rational as my earlier post for RC1).
On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels wrote:
> +1 (binding)
>
> * Verified checksums
> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>
> -Max
>
> On 26.02.19 10:40, Ahmet Altay wrote:
> > Hi everyone,
> >
> >
+1 (binding)
* Verified checksums
* Ran quickstart WordCount tests local/cluster with the Flink Runner
-Max
On 26.02.19 10:40, Ahmet Altay wrote:
Hi everyone,
Please review and vote on the release candidate #2 for the version
2.11.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not
Hi everyone,
Please review and vote on the release candidate #2 for the version 2.11.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],
18 matches
Mail list logo
