Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

Nice, it seems we're in agreement. I'll batch-edit the existing issues to remove the 1.6.0 fixVersion. Aljoscha > On 15. Mar 2018, at 08:34, Thomas Weise wrote: > > +1 > > Since it is guaranteed that all pre 1.5.0 release patches also make it to > master, it would be

Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

+1 Since it is guaranteed that all pre 1.5.0 release patches also make it to master, it would be confusing to mark them resolved for 1.6.x. On Thu, Mar 15, 2018 at 8:25 AM, Stephan Ewen wrote: > +1 > > Important: Please still write in the notes (when closing the issue) the >

Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

+1 Important: Please still write in the notes (when closing the issue) the commit hashes for both 1.5 (release-1.5) and 1.6 (master). Otherwise it makes hind-sight digging into the fixed more complicated. On Thu, Mar 15, 2018 at 3:28 PM, Felix Cheung wrote: > +1 >

Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

+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,

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 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: >

Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

+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

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. > > On 15.03.2018 01:40, Aljoscha Krettek wrote: >> Hi, >> >> We currently have some issues that are marked as resolved

Re: [DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

+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

[DISCUSS] Not marking Jira issues as resolved in 1.5.0 as resolved in 1.6.0

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