n Thu, Mar 15, 2018 at 11:09 AM, Ted Yu wrote:
>>>
>>>> +1 on marking bugs as fixed for 1.5.0 only.
>>>> Original message From: Piotr Nowojski <
>>>> pi...@data-artisans.com> Date: 3/15/18 12:48 AM (GMT-08:00) To:
>>>
l Rohrmann
> > Sent: Thursday, March 15, 2018 5:45:14 AM
> > To: dev@flink.apache.org
> > Subject: Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as
> > resolved in 1.6.0
> >
> > +1 for marking bugs as fixed 1.5.0 only
> >
> &
+1
>
>
> From: Till Rohrmann
> Sent: Thursday, March 15, 2018 5:45:14 AM
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as
> resolved in 1.6.0
>
> +1 for marking bugs as fixed 1.5.0 only
>
> On Thu, Mar 15, 2018
+1
From: Till Rohrmann
Sent: Thursday, March 15, 2018 5:45:14 AM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved
in 1.6.0
+1 for marking bugs as fixed 1.5.0 only
On Thu, Mar 15, 2018 at 11:09 AM, Ted Yu
he.org Subject: Re: [DISCUSS] Not marking Jira issues as
> resolved in 1.5.0 as resolved in 1.6.0
> Same as Chesnay
>
> +1 for marking bugs as fixed 1.5.0 only
>
> > On 15 Mar 2018, at 07:57, Chesnay Schepler wrote:
> >
> > +1 to mark bugs as fixed in 1.5.0 only.
+1 on marking bugs as fixed for 1.5.0 only.
Original message From: Piotr Nowojski
Date: 3/15/18 12:48 AM (GMT-08:00) To:
dev@flink.apache.org Subject: Re: [DISCUSS] Not marking Jira issues as resolved
in 1.5.0 as resolved in 1.6.0
Same as Chesnay
+1 for marking bugs as
Same as Chesnay
+1 for marking bugs as fixed 1.5.0 only
> On 15 Mar 2018, at 07:57, Chesnay Schepler wrote:
>
> +1 to mark bugs as fixed in 1.5.0 only.
>
> On 15.03.2018 01:40, Aljoscha Krettek wrote:
>> Hi,
>>
>> We currently have some issues that are marked as resolved for both 1.5.0 and
>
+1 to mark bugs as fixed in 1.5.0 only.
On 15.03.2018 01:40, Aljoscha Krettek wrote:
Hi,
We currently have some issues that are marked as resolved for both 1.5.0 and
1.6.0 [1]. The reason is that we have the release-1.5 branch and the master
branch, which will eventually become the branch for
Hi,
We currently have some issues that are marked as resolved for both 1.5.0 and
1.6.0 [1]. The reason is that we have the release-1.5 branch and the master
branch, which will eventually become the branch for 1.6.0.
I think this can lead to confusion because the release notes are created based
