Re:Closing bug reports

I think that If I want to contribute to close issue at minimum I have to know which are really open issues and which are really closed issue.
Now we have near 200 issue open and at the moment we don't know which are open because someone is working or simple it was not closed or for some others reason.
This is why I want to close some issues.

In any case I would like to read a reccomendation from David about opening/closing issue.
Marco: I guess my process recommendations were not sufficiently clear. I'll go ahead and close this for now since you've already created a replacement issue, but what I said was to handle differently these 2 cases:

- if it is a replacement of a previous patch, put it in the same issue

- if it is in addition to a previous patch, and separate from it, then create a new issue





In this case I think it's an addition and so this issue can be closed.

So please tell us how we can proceed in a way or in the opposite way.

Marco

---------- Initial Header -----------

From      : "David Welton" [hidden email]
To          : [hidden email]
Cc          :
Date      : Fri, 20 Oct 2006 15:13:53 +0200
Subject : Closing bug reports

> > Marco Risaliti commented on OFBIZ-173:
> > --------------------------------------
> >
> > Why don't we close it for the moment and if Rodrigo will open a new issue when if he needs ?
>
> That is in response to:
> ----
> Rodrigo Aguinaga [23/Sep/06 09:15 PM]
> Hi Jacopo,
>   I plan to work on this issue as soon I've some time, so please do
> not close this issue yet, is just that I haven't got a lot of time
> since I change of work and my schedule it's a total mess rigth now.
> ----
>
> That isn't even a month ago!  I think that open source projects should
> not be so aggressive in their 'garbage collection' of old issues.
> There is no shame in having things open.
>
> --
> David N. Welton
>  - http://www.dedasys.com/davidw/
>
> Linux, Open Source Consulting
>  - http://www.dedasys.com/
>

------------------------------------------------------
Riascolta i tuoi 33 e 45 giri con un bellissimo Giradischi Retrò, tecnologia HI-FI, collegamento PC e design anni '60 !
http://click.libero.it/dmail3

[Yoav Shapira-2]

Hi,
My approach is three-fold.  This is just my personal preference, no
rule of any kind.

First, assign long-term issues to someone.  It doesn't have to be a
committer, any email address will work.  When looking at the open
issues list, if it's assigned leave it be.

Second, if you think an issue should be closed, ask on the mailing
list first.  Maybe someone's working on it and forgot to assign it,
maybe there's consensus to keep it open, or maybe you can close it.
But asking in advance tends to work better than explaining afterwards
;)

Third, establish some very long time frame (I usually give it about 2
years) before just closing down inactive issues, and even then only
after mailing list discussion.

Yoav

On 10/20/06, [hidden email] <[hidden email]> wrote:

> I think that If I want to contribute to close issue at minimum I have to know which are really open issues and which are really closed issue.
> Now we have near 200 issue open and at the moment we don't know which are open because someone is working or simple it was not closed or for some others reason.
> This is why I want to close some issues.
>
> In any case I would like to read a reccomendation from David about opening/closing issue.
> Marco: I guess my process recommendations were not sufficiently clear. I'll go ahead and close this for now since you've already created a replacement issue, but what I said was to handle differently these 2 cases:
>
> - if it is a replacement of a previous patch, put it in the same issue
>
> - if it is in addition to a previous patch, and separate from it, then create a new issue
>
>
>
>
>
> In this case I think it's an addition and so this issue can be closed.
>
> So please tell us how we can proceed in a way or in the opposite way.
>
> Marco
>
> ---------- Initial Header -----------
>
> From      : "David Welton" [hidden email]
> To          : [hidden email]
> Cc          :
> Date      : Fri, 20 Oct 2006 15:13:53 +0200
> Subject : Closing bug reports
>
>
>
>
>
>
>
> > > Marco Risaliti commented on OFBIZ-173:
> > > --------------------------------------
> > >
> > > Why don't we close it for the moment and if Rodrigo will open a new issue when if he needs ?
> >
> > That is in response to:
> > ----
> > Rodrigo Aguinaga [23/Sep/06 09:15 PM]
> > Hi Jacopo,
> >   I plan to work on this issue as soon I've some time, so please do
> > not close this issue yet, is just that I haven't got a lot of time
> > since I change of work and my schedule it's a total mess rigth now.
> > ----
> >
> > That isn't even a month ago!  I think that open source projects should
> > not be so aggressive in their 'garbage collection' of old issues.
> > There is no shame in having things open.
> >
> > --
> > David N. Welton
> >  - http://www.dedasys.com/davidw/
> >
> > Linux, Open Source Consulting
> >  - http://www.dedasys.com/
> >
>
>
> ------------------------------------------------------
> Riascolta i tuoi 33 e 45 giri con un bellissimo Giradischi Retrò, tecnologia HI-FI, collegamento PC e design anni '60 !
> http://click.libero.it/dmail3
>
>
>

[davidnwelton]

> - if it is a replacement of a previous patch, put it in the same issue
>
> - if it is in addition to a previous patch, and separate from it, then create a new issue

Yes, that's good advice.  What would probably be ideal in this case is
to create a 'subtask' in JIRA, but I don't know if that installation
supports them...?  In any case I think it's best to err on the side of
caution when closing things unless they're really old (years).  Just
my take on things though... reasonable people may have different
opinions.

--
David N. Welton
 - http://www.dedasys.com/davidw/

Linux, Open Source Consulting
 - http://www.dedasys.com/