Thanks to all, I get the point now.
On Thu, Dec 26, 2013 at 4:04 PM, Flavio Junqueira <fpjunque...@yahoo.com>wrote: > Thanks for the comments! Giving time for people to respond sounds like > what we typically do. The same holds for telling people to reopen if needed. > > Before closing (or proposing to close) an issue that has been idle, it is > a good idea to do some investigation to see if it has been overlooked and > it is something we need to address. As you say, contributors come and go, > and the process of characterizing an issue, including severity, is not > perfect; it is not unusual to miss important issues if we simply rely on > people responding. We try hard not to miss important issues, though. > > -Flavio > > -----Original Message----- > From: Rumesh Eranga [mailto:rehrum...@gmail.com] > Sent: Wednesday, December 25, 2013 3:00 AM > To: dev@zookeeper.apache.org > Subject: RE: backlog clean-up > > Vetoshkin's idea is a better way to priceed I guess. Giving others some > time and then closing the issue. > > -----Original Message----- > From: "Vetoshkin Nikita" <nikita.vetosh...@gmail.com> > Sent: 12/24/2013 6:29 PM > To: "dev@zookeeper.apache.org" <dev@zookeeper.apache.org> > Subject: Re: backlog clean-up > > Sorry for interfering, just a thought based on my experience. > I usually prefer to run over a list of open issues, ask for comments, > (optionally) wait for a week or two and then close issue saying "Please, > feel free to reopen the issue if it still persists". I does usually work in > such environment, when reporters are not interested in your project anymore > or the issue has gone and they are a bit lazy to tell you that. But if the > issue does exist and is really itching - they usually come back, reopen and > clarify there view and answer the questions. > > > On Tue, Dec 24, 2013 at 12:50 PM, Flavio Junqueira <fpjunque...@yahoo.com > >wrote: > > > There is no concrete procedure afaik. Every now and then one of us > > goes over the list and cleans it up a bit. One key problem is that > > sometimes the people who have created the jira or contributed a patch > > do not responded, so the jira remains open because we shouldn´t > > resolve or close an issue without reaching agreement on whether it > > should be closed. > > > > Feel free to close issues that you understand as not being a problem, > > duplicate, etc. In the worst case, we will open it again. > > > > -Flavio > > > > -----Original Message----- > > From: German Blanco [mailto:german.blanco.bla...@gmail.com] > > Sent: Tuesday, December 24, 2013 6:34 AM > > To: dev@zookeeper.apache.org > > Subject: backlog clean-up > > > > The project has a large backlogs of JIRAs, but many of them do not > > reflect issues in the current versions. > > Wouldn't it make sense to spend a little time closing obsolete JIRAs? > > E.g. this one: > > https://issues.apache.org/jira/browse/ZOOKEEPER-1392 > > Seems to be "Not a problem". > > May I just go through the list and start resolving those that are > obvious? > > Or is there a better procedure to do this? > > > > > >
