Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
I think typically the process for RESOLVED-FIXED (those
issues that were fixed by some kind of code change to
/trunk) issues is to:
* commit the change to a release build
* once the release build is out for testing, check that the
bug is fixed, and use RESOLVED-VERFIED, to verify the fix, then
* CLOSE the issue
Recently, when I was looking at some issues that we'd
targeted for 4.1.2, I came upon a number that had been
RESOLVED-FIXED, but some had been committed to a release and
some had not. For those that had, I skipped the
RESOLVED-VERIFIED step and just closed them.
Currently, I feel we could use some additional help with
a) closing out old issues that have been ported to a
release, and
b) resetting the Target Release information for those issues
that have been fixed but have not been "released".
The following query only looks at RESOLVED-FIXED issues
since 2011-01-01
https://bz.apache.org/ooo/buglist.cgi?bug_status=RESOLVED&chfield=resolution&chfieldfrom=2011-01-01&chfieldto=Now&chfieldvalue=Fixed&limit=0&order=priority%2Cbug_severity&query_format=advanced&resolution=FIXED&resolution=FIXED_WITHOUT_CODE
A warning -- unless you can see an SVN commit clearly
stating that the fix has been ported to one of our existing
releases, it may take a bit of investigation into the
release branch area to determine this.
release branch area--
http://svn.apache.org/viewvc/openoffice/branches/
Our new resolution of FIXED_WITHOUT_CODE should result in
CLOSING without any further investigation.
Thoughts on undertaking this cleanup?
I've closed all listed issues regarding our infrastructure (Website,
Bugzilla, etc.). As you can see every single change results in a mail
and will fill everybody's inbox - when you are subscribed to the issues@
mailing list.
There will be the possibility to disable mails when performing special
actions (e.g., bulk issue changes) but not before release 6.0 [1]. At
the moment we are at 5.0.2. So, it will take some more time. ;-(
For the time being we have only the way do disable completely sending
mails when we work on the issue. But this means that *absolutely no
mails will be sent* regardless what was done (new issue, change,
comments, closing, etc.).
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1062718
Sorry for the spam. ;-)
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
