Re: Resolving all JIRAs affecting EOL releases

I am going to resolve those JIRAs now. 2019년 9월 9일 (월) 오전 9:46, Hyukjin Kwon 님이 작성: > Yup, no worries. I roughly set the one week delay considering the official > release date :D > > On Mon, 9 Sep 2019, 09:45 Dongjoon Hyun, wrote: > >> Thank you, Hyukjin. >> >> +1 for closing according to 2.3.x

Re: Resolving all JIRAs affecting EOL releases

Yup, no worries. I roughly set the one week delay considering the official release date :D On Mon, 9 Sep 2019, 09:45 Dongjoon Hyun, wrote: > Thank you, Hyukjin. > > +1 for closing according to 2.3.x EOL. > > For the timing, please do that after the official 2.3.4 release > announcement. > >

Re: Resolving all JIRAs affecting EOL releases

Thank you, Hyukjin. +1 for closing according to 2.3.x EOL. For the timing, please do that after the official 2.3.4 release announcement. Bests, Dongjoon. On Sun, Sep 8, 2019 at 16:27 Sean Owen wrote: > I think simply closing old issues with no activity in a long time is > OK. The "Affected

Re: Resolving all JIRAs affecting EOL releases

I think simply closing old issues with no activity in a long time is OK. The "Affected Version" is somewhat noisy, so not even particularly important to also query, but yeah I see some value in trying to limit the scope this way. On Sat, Sep 7, 2019 at 10:15 PM Hyukjin Kwon wrote: > > HI all, >

Re: Resolving all JIRAs affecting EOL releases

Thanks for the kind explanation. I see and it looks ok to me. On Sun, Sep 8, 2019 at 1:54 PM Hyukjin Kwon wrote: > Thanks for checking it. > > I think it's fine by two reasons below: > > 1. It has another condition for such cases - one year time range. > Basically, such PRs have not been

Re: Resolving all JIRAs affecting EOL releases

Thanks for checking it. I think it's fine by two reasons below: 1. It has another condition for such cases - one year time range. Basically, such PRs have not been merged for one year, which I believe are not likely merged soon. The JIRA status will be updated when such PRs are merged

Re: Resolving all JIRAs affecting EOL releases

Hi, Hyukjin, I checked entries in the list and I found that some entries have 'In-Progress' in their status and have oepn prs (e.g., SPARK-25211 ). We can also close these PRs according to the bulk close? (But, we might need to check the

Resolving all JIRAs affecting EOL releases

HI all, We have resolved JIRAs that targets EOL releases (up to Spark 2.2.x) in order to make it the manageable size before. Since Spark 2.3.4 will be EOL release, I plan to do this again roughly in a week. The JIRAs that has not been updated for the last year, and having affect version of EOL

Re: Resolving all JIRAs affecting EOL releases

I took an action for those JIRAs. The JIRAs that has not been updated for the last year, and having affect version of EOL releases were now: - Resolved as 'Incomplete' status - Has a 'bulk-closed' label. Thanks guys. 2019년 5월 21일 (화) 오전 8:35, shane knapp 님이 작성: > alright, i found 3 jiras

Re: Resolving all JIRAs affecting EOL releases

alright, i found 3 jiras that i was able to close: 1. SPARK-19612 2. 1. SPARK-22996 2. 1. SPARK-22766

Re: Resolving all JIRAs affecting EOL releases

Thanks Shane .. the URL I linked somehow didn't work in other people browser. Hope this link works:

Re: Resolving all JIRAs affecting EOL releases

I will add one more condition for "updated". So, it will additionally avoid things updated within one year but left open against EOL releases. project = SPARK AND status in (Open, "In Progress", Reopened) AND ( affectedVersion = EMPTY OR NOT (affectedVersion in versionMatch("^3.*")

Re: Resolving all JIRAs affecting EOL releases

I'd only tweak this to perhaps not close JIRAs that have been updated recently -- even just avoiding things updated in the last month. For example this would close https://issues.apache.org/jira/browse/SPARK-27758 which was opened Friday (though, for other reasons it should probably be closed).

Re: Resolving all JIRAs affecting EOL releases

Thanks guys. This thread got more than 3 PMC votes without any objection. I slightly edited JQL from Abdeali's suggestion (thanks, Abdeali). JQL: project = SPARK AND status in (Open, "In Progress", Reopened) AND ( affectedVersion = EMPTY OR NOT (affectedVersion in

Re: Resolving all JIRAs affecting EOL releases

+1, too. Thank you, Hyukjin! Bests, Dongjoon. On Fri, May 17, 2019 at 9:07 AM Imran Rashid wrote: > +1, thanks for taking this on > > On Wed, May 15, 2019 at 7:26 PM Hyukjin Kwon wrote: > >> oh, wait. 'Incomplete' can still make sense in this way then. >> Yes, I am good with 'Incomplete'

Re: Resolving all JIRAs affecting EOL releases

+1, thanks for taking this on On Wed, May 15, 2019 at 7:26 PM Hyukjin Kwon wrote: > oh, wait. 'Incomplete' can still make sense in this way then. > Yes, I am good with 'Incomplete' too. > > 2019년 5월 16일 (목) 오전 11:24, Hyukjin Kwon 님이 작성: > >> I actually recently used 'Incomplete' a bit when the

Re: Resolving all JIRAs affecting EOL releases

I actually recently used 'Incomplete' a bit when the JIRA is basically too poorly formed (like just copying and pasting an error) ... I was thinking about 'Unresolved' status or `Auto Closed' too. I double checked they can be reopen as well after resolution. [image: Screen Shot 2019-05-16 at

Re: Resolving all JIRAs affecting EOL releases

oh, wait. 'Incomplete' can still make sense in this way then. Yes, I am good with 'Incomplete' too. 2019년 5월 16일 (목) 오전 11:24, Hyukjin Kwon 님이 작성: > I actually recently used 'Incomplete' a bit when the JIRA is basically > too poorly formed (like just copying and pasting an error) ... > > I was

Re: Resolving all JIRAs affecting EOL releases

Agree, anything without an Affected Version should be old enough to time out. I might use "Incomplete" or something as the status, as we haven't otherwise used that. Maybe that's simpler than a label. But, anything like that sounds good. On Wed, May 15, 2019 at 8:40 PM Hyukjin Kwon wrote: >

Re: Resolving all JIRAs affecting EOL releases

BTW, affected version became a required field (I don't remember when exactly was .. I believe it's around when we work on Spark 2.3): [image: Screen Shot 2019-05-16 at 10.29.50 AM.png] So, including all EOL versions and affected versions not specified will roughly work. Using "Cannot Reproduce"

Re: Resolving all JIRAs affecting EOL releases

+1 in favor of some sort of JIRA cleanup. My only request is that we attach some sort of 'bulk-closed' label to issues that we close via JIRA filter batch operations (and resolve the issues as "Timed Out" / "Cannot Reproduce", not "Fixed"). Using a label makes it easier to audit what was closed,

Re: Resolving all JIRAs affecting EOL releases

I gave up looking through JIRAs a long time ago, so, big respect for continuing to try to triage them. I am afraid we're missing a few important bug reports in the torrent, but most JIRAs are not well-formed, just questions, stale, or simply things that won't be added. I do think it's important to

Re: Resolving all JIRAs affecting EOL releases

Yea, more sophisticated condition is welcome. My only goal is to make it to a manageable size. I would go for the option that reduces more tickets - under 1000 OPEN (and REOPEN) tickets so that we can at least go through in one go without coming up with a non duplicating filter to go through. On

Re: Resolving all JIRAs affecting EOL releases

Was thinking that getting an estimated statistic of the number of issues that would be closed if this is done would help. Open issues: 3882 (project = SPARK AND status in (Open, "In Progress", Reopened)) Open + Does not affect 3.0+ = 2795 Open + Does not affect 2.4+ = 2373 Open + Does not affect

Resolving all JIRAs affecting EOL releases

Hi all, I would like to propose to resolve all JIRAs that affects EOL releases - 2.2 and below. and affected version not specified. I was rather against this way and considered this as last resort in roughly 3 years ago when we discussed. Now I think we should go ahead with this. See below. I