I am going to formally document our de facto resolve/close policy in our wiki pages.
I am going to switch it from always close at time of resolve to "resolve when fixed, close when released" since that is what we have been doing. On Fri, May 15, 2015 at 3:33 PM, Udo Schnurpfeil <[email protected]> wrote: > For Tobago we do it in the Same manner (like core) > > Gruß Udo > >> Am 15.05.2015 um 18:19 schrieb Mike Kienenberger <[email protected]>: >> >> We should update our documentation to reflect that change in policy. >> >> I have been following the documented practice of resolve and close at >> the same time. >> >>> On Fri, May 15, 2015 at 12:16 PM, Leonardo Uribe <[email protected]> wrote: >>> Hi >>> >>> In MyFaces Core project the strategy applied is mark the issue as >>> resolved and then before the release close all resolved issues in >>> bulk. If there is a issue that is not resolved as fixed (duplicate, >>> won't fix, invalid), it is closed immediately. >>> >>> regards, >>> >>> Leonardo Uribe >>> >>> 2015-05-15 10:42 GMT-05:00 Mike Kienenberger <[email protected]>: >>> >>>> Officially, our developer notes (hard to find currently!) state that >>>> we close issues at the same time as we resolve them. >>>> >>>> >>>> http://myfaces.apache.org/wiki/core/committer-and-pmc-guide/myfaces-developer-notes.html >>>> >>>> I don't know if Tobago is using a different methodology and I'm fine >>>> if we change or update what we do so long as it's consistent within a >>>> specific project and documented, but right now I'm seeing Tobago >>>> issues sometimes being closed and sometimes being resolved but not >>>> closed. I recommend that you pick something, document it above if it >>>> differs, and be consistent with it. >>>> >>>> Personally, I like to see issues resolved at the time of the fix, and >>>> closed at the time of a release with the fix, but that puts more work >>>> on the release manager. >>> >>>
