Full_Name: Pierangelo Masarati Version: irrelevant OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (194.237.142.7) The ITS is polluted by issues opened, considered by developers, and pending feedback since ever. I suggest the ITS automatically closes issues not fed back after a reasonable amount of time. Closed issues can always be re-opened if issueers wake up and respond. p.
On 10/16/08 8:12 AM, ando@sys-net.it wrote: > The ITS is polluted by issues opened, considered by developers, and pending > feedback since ever. I suggest the ITS automatically closes issues not fed back > after a reasonable amount of time. Closed issues can always be re-opened if > issueers wake up and respond. > > As a user... I would completely agree with this and suggest that 30 days is a "reasonable amount of time" -- Frank Swasey | http://www.uvm.edu/~fcs Sr Systems Administrator | Always remember: You are UNIQUE, University of Vermont | just like everyone else. "I am not young enough to know everything." - Oscar Wilde (1854-1900)
Frank.Swasey@uvm.edu wrote: > On 10/16/08 8:12 AM, ando@sys-net.it wrote: >> The ITS is polluted by issues opened, considered by developers, and pending >> feedback since ever. I suggest the ITS automatically closes issues not fed back >> after a reasonable amount of time. Closed issues can always be re-opened if >> issueers wake up and respond. > > As a user... I would completely agree with this and suggest that 30 days > is a "reasonable amount of time" Although I try to keep up with testing sometimes 30 days could be a little bit short. Anyway I wonder what the state "Feedback" really means. I've checked if there are still open issues in this state submitted by me. The only one seems to be ITS#5574, but I can't resolve this since assigning the official OID needed in this case is not something I can do. I could only test something and give feedback. Ciao, Michael.
michael@stroeder.com wrote: > Although I try to keep up with testing sometimes 30 days could be a > little bit short. > > Anyway I wonder what the state "Feedback" really means. I've checked if > there are still open issues in this state submitted by me. The only one > seems to be ITS#5574, but I can't resolve this since assigning the > official OID needed in this case is not something I can do. I could only > test something and give feedback. It means some feedback is expected from the submitter. In ITS#5574 case, the most appropriate status is "suspended" (just changed). p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
--On Thursday, October 16, 2008 12:12 PM +0000 ando@sys-net.it wrote: > The ITS is polluted by issues opened, considered by developers, and > pending feedback since ever. I suggest the ITS automatically closes > issues not fed back after a reasonable amount of time. Closed issues can > always be re-opened if issueers wake up and respond. The problem I see with this is we have a number of ITS' that are open because the work was partially done, but there is work remaining to be done, and that needs to be tracked. I'm not sure if "Open" is the best state, but they definitely shouldn't be "closed" either. I feel what we really need is a much improved bug tracking system where we can do things like assign target releases to bugs, keywords, and have better-tuned states. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
quanah@zimbra.com wrote: >> The ITS is polluted by issues opened, considered by developers, and >> pending feedback since ever. I suggest the ITS automatically closes >> issues not fed back after a reasonable amount of time. Closed issues can >> always be re-opened if issueers wake up and respond. > > > The problem I see with this is we have a number of ITS' that are open > because the work was partially done, but there is work remaining to be > done, and that needs to be tracked. I'm not sure if "Open" is the best > state, but they definitely shouldn't be "closed" either. > > I feel what we really need is a much improved bug tracking system where we > can do things like assign target releases to bugs, keywords, and have > better-tuned states. I don't want to make the story too long. Changing the ITS system could be an option, but I don't see it as a priority. Your point about partially addressed issues could probably be fixed by: - adding a comment on what release saw what portion of the fix - adding a new "needswork" state My point is about tickets opened with only partial information, answered with a request for clarification that never comes in: 5712, 5652, 5651, ... p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
----- quanah@zimbra.com wrote: > --On Thursday, October 16, 2008 12:12 PM +0000 ando@sys-net.it wrote: > > > The ITS is polluted by issues opened, considered by developers, and > > pending feedback since ever. I suggest the ITS automatically > closes > > issues not fed back after a reasonable amount of time. Closed > issues can > > always be re-opened if issueers wake up and respond. > > > The problem I see with this is we have a number of ITS' that are open > > because the work was partially done, but there is work remaining to be > > done, and that needs to be tracked. I'm not sure if "Open" is the > best > state, but they definitely shouldn't be "closed" either. > > I feel what we really need is a much improved bug tracking system > where we > can do things like assign target releases to bugs, keywords, and have > > better-tuned states. http://www.mantisbt.org/ ? -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghenry@OpenLDAP.org Community developed LDAP software. http://www.openldap.org/project/
ando@sys-net.it writes: > My point is about tickets opened with only partial information, answered > with a request for clarification that never comes in: 5712, 5652, 5651, ... Hm, you've marked ITS#5651 Feedback even though it contains no feedback request. If you sent one privately, I suggest you re-send via ITS. -- Hallvard
----- Hallvard B Furuseth <h.b.furuseth@usit.uio.no> ha scritto: > ando@sys-net.it writes: > > My point is about tickets opened with only partial information, answered > > with a request for clarification that never comes in: 5712, 5652, 5651, ... > > Hm, you've marked ITS#5651 Feedback even though it contains no feedback > request. If you sent one privately, I suggest you re-send via ITS. No, the request was with ITS#5652: same poster, almost same problem, same feedback... p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
changed state Open to Closed