Hello everyone,
we will explore a workaround for the issues with the Dataflow worker.
Because of this, the 2.6.0 release is no longer blocked by the Dataflow
workers at the moment. I hope to produce a release candidate by end-of-day
tomorrow.
Please reach out on this thread, or to me directly if
No problem :) I'm not entirely sure why the PR fixed his issue, but it
couldn't cause any harm so I went ahead and merged it.
On Sun, Jul 29, 2018 at 11:56 AM Jean-Baptiste Onofré
wrote:
> Yes, it's this one and I planned to do the review tonight.
>
> Just saw that you did the review and merge
Yes, it's this one and I planned to do the review tonight.
Just saw that you did the review and merge it. Thanks.
Regards
JB
On 29/07/2018 19:40, Reuven Lax wrote:
> Jozef, you reference a pull request in the bug, are you referring to
> this one?
>
>
Jozef, you reference a pull request in the bug, are you referring to this
one?
https://github.com/apache/beam/pull/6075/files
On Sun, Jul 29, 2018 at 12:13 AM Jozef Vilcek wrote:
> Hello, is there a change this bug make it into the release?
>
> https://issues.apache.org/jira/browse/BEAM-5028
>
Hi,
let me take the review as Eugene is off. We will do our best to include
in the release.
Regards
JB
On 29/07/2018 09:12, Jozef Vilcek wrote:
> Hello, is there a change this bug make it into the release?
>
> https://issues.apache.org/jira/browse/BEAM-5028
>
> On Sat, Jul 28, 2018 at 1:38 AM
Hello, is there a change this bug make it into the release?
https://issues.apache.org/jira/browse/BEAM-5028
On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada wrote:
> Hello all,
> I will start daily updates of progress on the 2.6.0 release.
> As of today, the main release blockers are issues in
Hello all,
I will start daily updates of progress on the 2.6.0 release.
As of today, the main release blockers are issues in Dataflow that are
preventing us from cutting the Dataflow workers.
- One issue in Java SDK related to FnAPI. Specifically PR 5709 requires
Dataflow worker changes[1].
Hello everyone,
I wanted to do an update on the state of the release, as there haven't been
news on this for a while.
We have found a few issues that broke postcommits a few weeks back, but we
hadn't noticed. Some people are tacking these to try to stabilize the
release branch[1].
In the
Hello all!
I've cut the release branch (release-2.6.0), with some help from Ahmet and
Boyuan. From now on, please cherry-pick 2.6.0 blockers into the branch.
Now we start stabilizing it.
Thanks!
-P.
On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré
wrote:
> Hi Pablo,
>
> I'm investigating
Hi Pablo,
I'm investigating this issue, but it's a little long process.
So, I propose you start with the release process, cutting the branch,
and then, I will create a cherry-pick PR for this one.
Regards
JB
On 17/07/2018 20:19, Pablo Estrada wrote:
> Checking once more:
> What does the
+1 for cutting the release branch and merging in any necessary PRs.
On Tue, Jul 17, 2018 at 11:33 AM Ahmet Altay wrote:
> JB said that he is looking at it (
> https://lists.apache.org/thread.html/1e329318a4dafe27b9ff304d9460d05d8966e5ceebaf4ebfb948e2b8@%3Cdev.beam.apache.org%3E
> )
>
> I
JB said that he is looking at it (
https://lists.apache.org/thread.html/1e329318a4dafe27b9ff304d9460d05d8966e5ceebaf4ebfb948e2b8@%3Cdev.beam.apache.org%3E
)
I propose cutting the release branch as proposed (July 17); and applying
any fixes related to the issue to the branch.
On Tue, Jul 17, 2018
Checking once more:
What does the communitythink we should do about
https://issues.apache.org/jira/browse/BEAM-4750 ? Should I bump it to 2.7.0?
Best
-P.
On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay wrote:
> Update: https://issues.apache.org/jira/browse/BEAM-4784 is not a release
> blocker,
Update: https://issues.apache.org/jira/browse/BEAM-4784 is not a release
blocker, details in the JIRA issue.
On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise wrote:
> Can one of our Python experts please take a look at
> https://issues.apache.org/jira/browse/BEAM-4784 and advise if this should
>
Can one of our Python experts please take a look at
https://issues.apache.org/jira/browse/BEAM-4784 and advise if this should
be addressed for the release?
Thanks,
Thomas
On Fri, Jul 13, 2018 at 11:02 AM Ahmet Altay wrote:
>
>
> On Fri, Jul 13, 2018 at 10:48 AM, Pablo Estrada
> wrote:
>
>>
On Fri, Jul 13, 2018 at 10:48 AM, Pablo Estrada wrote:
> Hi all,
> I've triaged most issues marked for 2.6.0 release. I've localized two that
> need a decision / attention:
>
> - https://issues.apache.org/jira/browse/BEAM-4417 - Bigquery IO Numeric
> Datatype Support. Cham is not available to
Hi all,
I've triaged most issues marked for 2.6.0 release. I've localized two that
need a decision / attention:
- https://issues.apache.org/jira/browse/BEAM-4417 - Bigquery IO Numeric
Datatype Support. Cham is not available to fix this at the moment, but this
is a critical issue. Is anyone able
+1,
Thanks for volunteering Pablo, thanks also to have caught tickets that I forgot
to close :)
Etienne
Le mercredi 11 juillet 2018 à 12:55 -0700, Alan Myrvold a écrit :
> +1 Thanks for volunteering, Pablo
>
> On Wed, Jul 11, 2018 at 11:49 AM Jason Kuster wrote:
> > +1 sounds great
> >
> > On
+1, Thanks Pablo!
śr., 11 lip 2018 o 21:55 Alan Myrvold napisał(a):
> +1 Thanks for volunteering, Pablo
>
> On Wed, Jul 11, 2018 at 11:49 AM Jason Kuster
> wrote:
>
>> +1 sounds great
>>
>> On Wed, Jul 11, 2018 at 11:06 AM Thomas Weise wrote:
>>
>>> +1
>>>
>>> Thanks for volunteering, Pablo!
+1 Thanks for volunteering, Pablo
On Wed, Jul 11, 2018 at 11:49 AM Jason Kuster
wrote:
> +1 sounds great
>
> On Wed, Jul 11, 2018 at 11:06 AM Thomas Weise wrote:
>
>> +1
>>
>> Thanks for volunteering, Pablo!
>>
>> On Mon, Jul 9, 2018 at 9:56 PM Jean-Baptiste Onofré
>> wrote:
>>
>>> +1
>>>
>>>
+1
Thanks for volunteering, Pablo!
On Mon, Jul 9, 2018 at 9:56 PM Jean-Baptiste Onofré wrote:
> +1
>
> I planned to send the proposal as well ;)
>
> Regards
> JB
>
> On 09/07/2018 23:16, Pablo Estrada wrote:
> > Hello everyone!
> >
> > As per the previously agreed-upon schedule for Beam
+1
I planned to send the proposal as well ;)
Regards
JB
On 09/07/2018 23:16, Pablo Estrada wrote:
> Hello everyone!
>
> As per the previously agreed-upon schedule for Beam releases, the
> process for the 2.6.0 Beam release should start on July 17th.
>
> I volunteer to perform this release.
>
Hello everyone!
As per the previously agreed-upon schedule for Beam releases, the process
for the 2.6.0 Beam release should start on July 17th.
I volunteer to perform this release.
Here is the schedule that I have in mind:
- We start triaging JIRA issues this week.
- I will cut a release
23 matches
Mail list logo
