On 08/04/2016 Kay Schenk wrote:
Ok, perhaps some misunderstanding here. What I'm asking for is assistance
is finding the RESOLVED-FIXED issues that actually were incorporated in a
release, and CLOSE them.
Well, RESOLVED-FIXED issues are:
- either non-code fixes as discussed, and in this case they are not in
any release by definition and can be set to CLOSED.
- or code fixes made on trunk. Since trunk will become 4.2.0, we expect
to be able to mark them CLOSED when 4.2.0 is released.
What you would find above is:
1) issues that were fixed after 4.1.0 (note: 4.1.0, not 4.1.2) and are
fixed on trunk for 4.2.0.
2) issues that were fixed before 4.1.0 (or cherry-picked for 4.1.1 or
4.1.2, but in this case the fix should appear both on trunk and on the
AOO410 branch) and that we forgot to mark CLOSED. This does not seem
very relevant for future QA. But it should be safe to mass-close them
with a message saying that we believe they can be closed and that a fix
can be found in 4.1.2.
Some of them even have comments that the issue was checked against a
release, but they were not CLOSEd. I am NOT requesting that RESOLVED-FIXED
issues that did not make it to a release be closed. This would be
premature.
Yes, this would definitely be premature until 4.2.0 is released.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
