Already on it. I closed some and commented on others to ask people whether we can close. :-)
On Sun, 29 Jan 2017 at 22:31 Robert Metzger <rmetz...@apache.org> wrote: > Thank you for fixing the link Chesnay. > > Over the weekend, I've assigned all JIRAs without a component to one. > I think some of the assignments were not 100% accurate. But the available > components in the overview list is somewhat limited: > https://cwiki.apache.org/confluence/display/FLINK/Components+and+Shepherds > > Also, there were some components that were accidentally created (probably > by using the autosuggest functionality of jira and pressing ENTER to > early). I've removed them. > It would be nice if the committers could check old issues they've reported, > they are assigned to and they are shepherding to clean up our JIRA a bit. > > > On Tue, Jan 24, 2017 at 4:46 PM, Chesnay Schepler <ches...@apache.org> > wrote: > > > fixed link: https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D% > > 201.2.0%20AND%20project%20%3D%20FLINK%20AND%20resolution%20% > > 3D%20Unresolved%20ORDER%20BY%20priority%20DESC > > > > Previous link lead to FLINK-5048. > > > > > > On 24.01.2017 16:33, Robert Metzger wrote: > > > >> Hey friends of a clean JIRA, > >> > >> I've unmarked as many JIRAs as possible from "Fix Version = 1.2.0" as > >> possible. > >> The list of unresolved 1.2.0 issues is now 15 items short: > >> https://issues.apache.org/jira/browse/FLINK-5048?jql=fixVers > >> ion%20%3D%201.2.0%20AND%20project%20%3D%20FLINK%20AND% > >> 20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC > >> Most of then are documentation fixes, some of them are not resolved yet, > >> because multiple fix versions are set. > >> > >> > >> I will try to send a monthly release status email (how many weeks until > >> next feature freeze / number of open JIRAs for that version / ... ) to > >> encourage people to clean up our JIRA. > >> > >> > >> > >> On Thu, Dec 22, 2016 at 9:45 AM, Fabian Hueske <fhue...@gmail.com> > wrote: > >> > >> Hi Anton, > >>> > >>> Thanks a lot for digging through JIRA! > >>> I'll do a pass over the issues and close or comment on those issue > that I > >>> know about. > >>> > >>> I'll update the FLINK-5384 with the status of the issues. > >>> > >>> Best, Fabian > >>> > >>> 2016-12-21 19:01 GMT+01:00 Aljoscha Krettek <aljos...@apache.org>: > >>> > >>> Thanks a lot for going through the issues and preparing this list! > >>>> > >>>> From a first glance some can definitely be closed. I didn't yet find > >>>> the > >>>> time to look through all of them but we should definitely work and > >>>> > >>> cleaning > >>> > >>>> up our Jira. > >>>> > >>>> Cheers, > >>>> Aljoscha > >>>> > >>>> On Wed, 21 Dec 2016 at 18:19 Anton Solovev <anton_solo...@epam.com> > >>>> > >>> wrote: > >>> > >>>> Hi folks > >>>>> > >>>>> I found a lot of non-relevant issues: > >>>>> > >>>>> https://issues.apache.org/jira/browse/FLINK-37 -> from stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-87 -> from stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-481 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-605 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-639 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-650 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-735 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-456 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-788 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-796 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-805 -> from > stratosphere ; > >>>>> https://issues.apache.org/jira/browse/FLINK-867 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-879 -> from > stratosphere; > >>>>> https://issues.apache.org/jira/browse/FLINK-1055 ; > >>>>> https://issues.apache.org/jira/browse/FLINK-1098 -> create other > issue > >>>>> > >>>> to > >>>> > >>>>> add a colectEach(); > >>>>> https://issues.apache.org/jira/browse/FLINK-1100 ; > >>>>> https://issues.apache.org/jira/browse/FLINK-1166 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-1146 ; > >>>>> https://issues.apache.org/jira/browse/FLINK-1335 -> maybe rename?; > >>>>> https://issues.apache.org/jira/browse/FLINK-1439 ; > >>>>> https://issues.apache.org/jira/browse/FLINK-1447 -> firefox > problem?; > >>>>> https://issues.apache.org/jira/browse/FLINK-1521 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-1538 -> gsoc2015, is it > >>>>> solved?; > >>>>> https://issues.apache.org/jira/browse/FLINK-1541 -> gsoc2015, is it > >>>>> solved?; > >>>>> https://issues.apache.org/jira/browse/FLINK-1723 -> almost done? ; > >>>>> https://issues.apache.org/jira/browse/FLINK-1814 ; > >>>>> https://issues.apache.org/jira/browse/FLINK-1858 -> is QA bot > >>>>> > >>>> deleted?; > >>> > >>>> https://issues.apache.org/jira/browse/FLINK-1926 -> all subtasks > done; > >>>>> https://issues.apache.org/jira/browse/FLINK-1946 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2023 -> does not block > >>>>> > >>>> Scala > >>> > >>>> Graph API; > >>>>> https://issues.apache.org/jira/browse/FLINK-2032 -> all subtasks > done; > >>>>> https://issues.apache.org/jira/browse/FLINK-2108 -> almost done? ; > >>>>> https://issues.apache.org/jira/browse/FLINK-2119 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2157 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2220 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2309 -> maybe it's worth > >>>>> > >>>> to > >>> > >>>> merge with https://issues.apache.org/jira/browse/FLINK-2316 ? ; > >>>>> https://issues.apache.org/jira/browse/FLINK-2319 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2363 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2399 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2428 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2472 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2480 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2609 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-2823 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-3109 -> its PR is stuck; > >>>>> https://issues.apache.org/jira/browse/FLINK-3154 -> must be > addressed > >>>>> > >>>> as > >>> > >>>> part of a bigger initiative; > >>>>> https://issues.apache.org/jira/browse/FLINK-3155 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-3297 -> solved as third > >>>>> > >>>> party > >>>> > >>>>> lib; > >>>>> https://issues.apache.org/jira/browse/FLINK-3331 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-3613 -> close this in > >>>>> > >>>> favor > >>> > >>>> of https://issues.apache.org/jira/browse/FLINK-4604 ; > >>>>> https://issues.apache.org/jira/browse/FLINK-3827 -> need check > status > >>>>> again > >>>>> https://issues.apache.org/jira/browse/FLINK-3964 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-4195 -> is it solved > with > >>>>> https://issues.apache.org/jira/browse/FLINK-4170 ? > >>>>> https://issues.apache.org/jira/browse/FLINK-4653 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-4338 -> all subtasks > done; > >>>>> https://issues.apache.org/jira/browse/FLINK-4717 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-4829 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-4834 -> all subtasks > done; > >>>>> https://issues.apache.org/jira/browse/FLINK-4837 -> solved on Bahir > >>>>> > >>>> side; > >>>> > >>>>> https://issues.apache.org/jira/browse/FLINK-5016 -> closed on > github; > >>>>> https://issues.apache.org/jira/browse/FLINK-5175 -> closed on > github, > >>>>> > >>>> but > >>>> > >>>>> for version 2.0; > >>>>> > >>>>> > >>>>> Or I I'm wrong, some issues steel is relevant, or maybe I missed > >>>>> something, correct me please > >>>>> What should we do with it? Should we close? > >>>>> > >>>>> > >>>>> > > >
