I went ahead and took over all the bugs and did the cherrypicks for the
remaining backports targeting 2.7.1:
https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012344458
The tests are not healthy. I have not had time to
Created an up-to-date version of the Flink backports for 2.7.1:
https://github.com/apache/beam/pull/8787
Some of the Gradle task names have changed which makes testing via Jenkins
hard. Will have to run them manually before merging.
-Max
On 06.06.19 17:41, Kenneth Knowles wrote:
Hi all,
Re-
Hi all,
Re-raising this thread. I got busy for the last month, and also did not
want to overlap the 2.13.0 release process. Now I want to pick up 2.7.1
again.
Can everyone check on any bug they have targeted to 2.7.1 [1] and get the
backports merged to release-2.7.1 and the tickets resolved?
Ken
I agree with both keeping 2.7.x going until a new LTS is declared and
declaring LTS spost-release after some use. 2.12 might actually be a good
candidate, with multiple RCs/validations it presumably is well tested. We
can consider that after it gets some real world use.
On Fri, Apr 26, 2019 at 6:2
IIRC, there was some talk on making 2.12 the next LTS, but the
consensus is to decide on a LTS after having had some experience with
it, not at or before the release itself.
On Fri, Apr 26, 2019 at 3:04 PM Alexey Romanenko
wrote:
>
> Thanks for working on this, Kenn.
>
> Perhaps, I missed this b
Thanks for working on this, Kenn.
Perhaps, I missed this but has it been already discussed/decided what will be
the next LTS release?
> On 26 Apr 2019, at 08:02, Kenneth Knowles wrote:
>
> Since it is all trivially reversible if there is some other feeling about
> this thread, I have gone ahe
Sounds good Kenn. Thanks for starting the preparation for the LTS patch
release.
I assembled a list of Flink issues a while ago which I will have to
revisit because there have been more critical fixes since.
Thanks,
Max
On 26.04.19 08:02, Kenneth Knowles wrote:
Since it is all trivially reve
Since it is all trivially reversible if there is some other feeling about
this thread, I have gone ahead and started the work:
- I made release-2.7.1 branch point to the same commit as release-2.7.0 so
there is something to target PRs
- I have opened the first PR, cherry-picking the set_version
+1 it sounds good to me.
Thanks !
Regards
JB
On 26/04/2019 02:42, Kenneth Knowles wrote:
> Hi all,
>
> Since the release of 2.7.0 we have identified some serious bugs:
>
> - There are 8 (non-dupe) issues* tagged with Fix Version 2.7.1
> - 2 are rated "Blocker" (aka P0) but I think the others
+1 great idea. Could you share a link to the list of issues you are
planning to patch?
For clarification, how long we plan to support 2.7.x line?
On Thu, Apr 25, 2019 at 5:42 PM Kenneth Knowles wrote:
> Hi all,
>
> Since the release of 2.7.0 we have identified some serious bugs:
>
> - There ar
Hi all,
Since the release of 2.7.0 we have identified some serious bugs:
- There are 8 (non-dupe) issues* tagged with Fix Version 2.7.1
- 2 are rated "Blocker" (aka P0) but I think the others may be underrated
- If you know of a critical bug that is not on that list, please file an
LTS backpor
11 matches
Mail list logo
