You are viewing a plain text version of this content. The canonical link for it is here.
Posted to qa@openoffice.apache.org by Kay Schenk <ka...@gmail.com> on 2016/04/07 00:43:13 UTC
[DISCUSS] Cleanup needed for RESOLVED-FIXED issues
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?
--
--------------------------------------------
MzK
"Time spent with cats is never wasted."
-- Sigmund Freud
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/09/2016 11:36 PM, schrieb Kay Schenk:
> On Sat, Apr 9, 2016 at 3:01 AM, Marcus<ma...@wtnet.de> wrote:
>
>> Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
>>
>>> [...]
>>>
>>> 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?
>>>
>>
>> many issues are commented with "fixed in CMS xyz" but there are no real
>> commits visible. Not every CWS was committed into Trunk before the project
>> and software was transferred to Apache.
>
>
>> So, do we have a list of outstanding CWS from 2011 that were not
>> transferred to Apache?
>>
>> Thanks
>
>
> As far as I know, NONE of the CWS (child workspaces) were ported when the
> project was brought into Apache.
hm, I remember that some were integrated. But I'm not really sure. It's
too long ago. ;-)
@all:
Does anybody else remember a list of these CWS? Integrated or not? It
would be very helpful.
> For a while, these were "available" somewhere, but that archive
> disappeared at some point, at least from its original location.
Too bad.
> I
> also believe looking at the activity when OpenOffice was brought in the
> ASF, that some of this code may have been committed to /trunk by
> individuals, but the spaces where not merged in their entirety.
> Generally, these kinds of changes you find referenced in BZ may as well be
> considered OBSOLETE I guess.
Knowing which CWS was integrated and which not is important to set the
correct status. If the fix was never committed into Trunk then OBSOLETE
seems not the right thing as the issue may still be occurring.
> You're doing a considerable job on all this byt the way! :) Thanks.
:-)
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Kay Schenk <ka...@gmail.com>.
On Sat, Apr 9, 2016 at 3:01 AM, Marcus <ma...@wtnet.de> wrote:
> Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
>
>> [...]
>>
>> 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?
>>
>
> many issues are commented with "fixed in CMS xyz" but there are no real
> commits visible. Not every CWS was committed into Trunk before the project
> and software was transferred to Apache.
> So, do we have a list of outstanding CWS from 2011 that were not
> transferred to Apache?
>
> Thanks
As far as I know, NONE of the CWS (child workspaces) were ported when the
project was brought into Apache.
For a while, these were "available" somewhere, but that archive
disappeared at some point, at least from its original location.
I
also believe looking at the activity when OpenOffice was brought in the
ASF, that some of this code may have been committed to /trunk by
individuals, but the spaces where not merged in their entirety.
Generally, these kinds of changes you find referenced in BZ may as well be
considered OBSOLETE I guess.
You're doing a considerable job on all this byt the way! :) Thanks.
>
>
> Marcus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
----------------------------------------------------------------------
MzK
"Time spent with cats is never wasted."
-- Sigmund Freud
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
> [...]
>
> 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?
many issues are commented with "fixed in CMS xyz" but there are no real
commits visible. Not every CWS was committed into Trunk before the
project and software was transferred to Apache.
So, do we have a list of outstanding CWS from 2011 that were not
transferred to Apache?
Thanks
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/08/2016 07:04 PM, schrieb Kay Schenk:
> On Thu, Apr 7, 2016 at 3:58 PM, Kay Schenk<ka...@gmail.com> wrote:
>>
>> On Thu, Apr 7, 2016 at 9:59 AM, Marcus<ma...@wtnet.de> wrote:
>>
>>> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
>>>
>>>> My only concern is that this is a giant CTR and pretty much assures that
>>>> the "R" will not happen.
>>>>
>>>
>>> yes, but especially with old issues I don't see a big problem here. Maybe
>>> for single issues. But IMHO this is no argument to keep every issue open
>>> and inspect them in all details. Then it's better to reopen some of them.
>>>
>>
>> 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.
>>
>>
>> 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. Sorry for the misunderstanding.
>>
>>
>>> When it's "RESOLVED - FIXED", then I trust the status somehow and will
>>> only do some checks. But I don't put the resolution "FIXED" into doubt and
>>> do everything again that is listed in the issue.
>>>
>>> So be it.
>>>>
>>>> However, do not disable the issues mails for any reason. There is a
>>>> difference between R not happening and R not being possible.
>>>>
>>>
>>> That's right.
>>>
>>
>> The search I referenced in the first post has more than 1500 issues in
>> the RESOLVED-FIXED category.
>>
>> Of these, some percentage should be CLOSEd. And yes, it's a bit of an
>> annoyance to get the emails, but I think it's worth it to keep better
>> records.
>>
>>
>>>
>>> Marcus
>>
>>
> A great big THANK YOU for the work done on this cleanup business so far.
>
> SUPER!!!!!
please, no. ;-)
Judging for these issues is easy without fixes for any OpenOffice code.
I'll answer your other mail later. And try to close more issues in the
next days.
Marcus
>>> -----Original Message-----
>>>>> From: Marcus [mailto:marcus.mail@wtnet.de]
>>>>> Sent: Thursday, April 7, 2016 02:10
>>>>> To: dev@openoffice.apache.org
>>>>> Cc: qa@openoffice.apache.org
>>>>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>>>>
>>>>> [ ... ]
>>>>
>>>>> 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-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/08/2016 07:04 PM, schrieb Kay Schenk:
> On Thu, Apr 7, 2016 at 3:58 PM, Kay Schenk<ka...@gmail.com> wrote:
>>
>> On Thu, Apr 7, 2016 at 9:59 AM, Marcus<ma...@wtnet.de> wrote:
>>
>>> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
>>>
>>>> My only concern is that this is a giant CTR and pretty much assures that
>>>> the "R" will not happen.
>>>>
>>>
>>> yes, but especially with old issues I don't see a big problem here. Maybe
>>> for single issues. But IMHO this is no argument to keep every issue open
>>> and inspect them in all details. Then it's better to reopen some of them.
>>>
>>
>> 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.
>>
>>
>> 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. Sorry for the misunderstanding.
>>
>>
>>> When it's "RESOLVED - FIXED", then I trust the status somehow and will
>>> only do some checks. But I don't put the resolution "FIXED" into doubt and
>>> do everything again that is listed in the issue.
>>>
>>> So be it.
>>>>
>>>> However, do not disable the issues mails for any reason. There is a
>>>> difference between R not happening and R not being possible.
>>>>
>>>
>>> That's right.
>>>
>>
>> The search I referenced in the first post has more than 1500 issues in
>> the RESOLVED-FIXED category.
>>
>> Of these, some percentage should be CLOSEd. And yes, it's a bit of an
>> annoyance to get the emails, but I think it's worth it to keep better
>> records.
>>
>>
>>>
>>> Marcus
>>
>>
> A great big THANK YOU for the work done on this cleanup business so far.
>
> SUPER!!!!!
please, no. ;-)
Judging for these issues is easy without fixes for any OpenOffice code.
I'll answer your other mail later. And try to close more issues in the
next days.
Marcus
>>> -----Original Message-----
>>>>> From: Marcus [mailto:marcus.mail@wtnet.de]
>>>>> Sent: Thursday, April 7, 2016 02:10
>>>>> To: dev@openoffice.apache.org
>>>>> Cc: qa@openoffice.apache.org
>>>>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>>>>
>>>>> [ ... ]
>>>>
>>>>> 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: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Kay Schenk <ka...@gmail.com>.
On Thu, Apr 7, 2016 at 3:58 PM, Kay Schenk <ka...@gmail.com> wrote:
>
> On Thu, Apr 7, 2016 at 9:59 AM, Marcus <ma...@wtnet.de> wrote:
>
>> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
>>
>>> My only concern is that this is a giant CTR and pretty much assures that
>>> the "R" will not happen.
>>>
>>
>> yes, but especially with old issues I don't see a big problem here. Maybe
>> for single issues. But IMHO this is no argument to keep every issue open
>> and inspect them in all details. Then it's better to reopen some of them.
>>
>
> 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.
>
>
> 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. Sorry for the misunderstanding.
>
>
>> When it's "RESOLVED - FIXED", then I trust the status somehow and will
>> only do some checks. But I don't put the resolution "FIXED" into doubt and
>> do everything again that is listed in the issue.
>>
>> So be it.
>>>
>>> However, do not disable the issues mails for any reason. There is a
>>> difference between R not happening and R not being possible.
>>>
>>
>> That's right.
>>
>
> The search I referenced in the first post has more than 1500 issues in
> the RESOLVED-FIXED category.
>
> Of these, some percentage should be CLOSEd. And yes, it's a bit of an
> annoyance to get the emails, but I think it's worth it to keep better
> records.
>
>
>>
>> Marcus
>
>
A great big THANK YOU for the work done on this cleanup business so far.
SUPER!!!!!
>
>>
>>
>>
>> -----Original Message-----
>>>> From: Marcus [mailto:marcus.mail@wtnet.de]
>>>> Sent: Thursday, April 7, 2016 02:10
>>>> To: dev@openoffice.apache.org
>>>> Cc: qa@openoffice.apache.org
>>>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>>>
>>>> [ ... ]
>>>
>>>> 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-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> ----------------------------------------------------------------------
> MzK
>
> "Time spent with cats is never wasted."
> -- Sigmund Freud
>
>
--
----------------------------------------------------------------------
MzK
"Time spent with cats is never wasted."
-- Sigmund Freud
RE: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by "Dennis E. Hamilton" <de...@acm.org>.
> -----Original Message-----
> From: Marcus [mailto:marcus.mail@wtnet.de]
> Sent: Saturday, April 9, 2016 00:01
> To: dev@openoffice.apache.org
> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>
> Am 04/08/2016 12:58 AM, schrieb Kay Schenk:
> > On Thu, Apr 7, 2016 at 9:59 AM, Marcus<ma...@wtnet.de> wrote:
> >
> >> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
> >>
> >>> My only concern is that this is a giant CTR and pretty much assures
> that
> >>> the "R" will not happen.
> >>
> >> yes, but especially with old issues I don't see a big problem here.
> Maybe
> >> for single issues. But IMHO this is no argument to keep every issue
> open
> >> and inspect them in all details. Then it's better to reopen some of
> them.
> >
> > 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.
>
> Sure, I think I've understood your intension. I just wanted to point out
> that there are also non-code issues. These could be simple and can be
> closed when the solution is commented in the issue (you know, the
> typical user how-to's, etc.).
[orcmid]
In some cases, these bring out the need for some documentation or other places to point users to that may not be well-known. I think of that as something that remains open so it shows on searches and is a reminder that something useful would be helpful somewhere. Then the issue could link to that before RESOLVED - FIXED_WITHOUT_CODE is set.
I think this is very much on an individual case basis.
[ ... ]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/08/2016 12:58 AM, schrieb Kay Schenk:
> On Thu, Apr 7, 2016 at 9:59 AM, Marcus<ma...@wtnet.de> wrote:
>
>> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
>>
>>> My only concern is that this is a giant CTR and pretty much assures that
>>> the "R" will not happen.
>>
>> yes, but especially with old issues I don't see a big problem here. Maybe
>> for single issues. But IMHO this is no argument to keep every issue open
>> and inspect them in all details. Then it's better to reopen some of them.
>
> 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.
Sure, I think I've understood your intension. I just wanted to point out
that there are also non-code issues. These could be simple and can be
closed when the solution is commented in the issue (you know, the
typical user how-to's, etc.).
All others need indeed some more inspection.
> 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. Sorry for the misunderstanding.
Yes, we shouldn't close issues when the fix is not yet in the code.
>> When it's "RESOLVED - FIXED", then I trust the status somehow and will
>> only do some checks. But I don't put the resolution "FIXED" into doubt and
>> do everything again that is listed in the issue.
>>
>> So be it.
>>>
>>> However, do not disable the issues mails for any reason. There is a
>>> difference between R not happening and R not being possible.
>>
>> That's right.
>
> The search I referenced in the first post has more than 1500 issues in the
> RESOLVED-FIXED category.
>
> Of these, some percentage should be CLOSEd. And yes, it's a bit of an
> annoyance to get the emails, but I think it's worth it to keep better
> records.
OK. Dennis brought the good argument that CTR (first commit then review)
is not possible when it is not known that C has already happened.
Marcus
>> -----Original Message-----
>>>> From: Marcus [mailto:marcus.mail@wtnet.de]
>>>> Sent: Thursday, April 7, 2016 02:10
>>>> To: dev@openoffice.apache.org
>>>> Cc: qa@openoffice.apache.org
>>>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>>>
>>>> [ ... ]
>>>
>>>> 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-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
--
Ciao
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Kay Schenk <ka...@gmail.com>.
On Thu, Apr 7, 2016 at 3:58 PM, Kay Schenk <ka...@gmail.com> wrote:
>
> On Thu, Apr 7, 2016 at 9:59 AM, Marcus <ma...@wtnet.de> wrote:
>
>> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
>>
>>> My only concern is that this is a giant CTR and pretty much assures that
>>> the "R" will not happen.
>>>
>>
>> yes, but especially with old issues I don't see a big problem here. Maybe
>> for single issues. But IMHO this is no argument to keep every issue open
>> and inspect them in all details. Then it's better to reopen some of them.
>>
>
> 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.
>
>
> 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. Sorry for the misunderstanding.
>
>
>> When it's "RESOLVED - FIXED", then I trust the status somehow and will
>> only do some checks. But I don't put the resolution "FIXED" into doubt and
>> do everything again that is listed in the issue.
>>
>> So be it.
>>>
>>> However, do not disable the issues mails for any reason. There is a
>>> difference between R not happening and R not being possible.
>>>
>>
>> That's right.
>>
>
> The search I referenced in the first post has more than 1500 issues in
> the RESOLVED-FIXED category.
>
> Of these, some percentage should be CLOSEd. And yes, it's a bit of an
> annoyance to get the emails, but I think it's worth it to keep better
> records.
>
>
>>
>> Marcus
>
>
A great big THANK YOU for the work done on this cleanup business so far.
SUPER!!!!!
>
>>
>>
>>
>> -----Original Message-----
>>>> From: Marcus [mailto:marcus.mail@wtnet.de]
>>>> Sent: Thursday, April 7, 2016 02:10
>>>> To: dev@openoffice.apache.org
>>>> Cc: qa@openoffice.apache.org
>>>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>>>
>>>> [ ... ]
>>>
>>>> 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-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> ----------------------------------------------------------------------
> MzK
>
> "Time spent with cats is never wasted."
> -- Sigmund Freud
>
>
--
----------------------------------------------------------------------
MzK
"Time spent with cats is never wasted."
-- Sigmund Freud
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Andrea Pescetti <pe...@apache.org>.
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-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Kay Schenk <ka...@gmail.com>.
On Thu, Apr 7, 2016 at 9:59 AM, Marcus <ma...@wtnet.de> wrote:
> Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
>
>> My only concern is that this is a giant CTR and pretty much assures that
>> the "R" will not happen.
>>
>
> yes, but especially with old issues I don't see a big problem here. Maybe
> for single issues. But IMHO this is no argument to keep every issue open
> and inspect them in all details. Then it's better to reopen some of them.
>
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.
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. Sorry for the misunderstanding.
> When it's "RESOLVED - FIXED", then I trust the status somehow and will
> only do some checks. But I don't put the resolution "FIXED" into doubt and
> do everything again that is listed in the issue.
>
> So be it.
>>
>> However, do not disable the issues mails for any reason. There is a
>> difference between R not happening and R not being possible.
>>
>
> That's right.
>
The search I referenced in the first post has more than 1500 issues in the
RESOLVED-FIXED category.
Of these, some percentage should be CLOSEd. And yes, it's a bit of an
annoyance to get the emails, but I think it's worth it to keep better
records.
>
> Marcus
>
>
>
>
> -----Original Message-----
>>> From: Marcus [mailto:marcus.mail@wtnet.de]
>>> Sent: Thursday, April 7, 2016 02:10
>>> To: dev@openoffice.apache.org
>>> Cc: qa@openoffice.apache.org
>>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>>
>>> [ ... ]
>>
>>> 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-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
----------------------------------------------------------------------
MzK
"Time spent with cats is never wasted."
-- Sigmund Freud
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton:
> My only concern is that this is a giant CTR and pretty much assures that the "R" will not happen.
yes, but especially with old issues I don't see a big problem here.
Maybe for single issues. But IMHO this is no argument to keep every
issue open and inspect them in all details. Then it's better to reopen
some of them.
When it's "RESOLVED - FIXED", then I trust the status somehow and will
only do some checks. But I don't put the resolution "FIXED" into doubt
and do everything again that is listed in the issue.
> So be it.
>
> However, do not disable the issues mails for any reason. There is a difference between R not happening and R not being possible.
That's right.
Marcus
>> -----Original Message-----
>> From: Marcus [mailto:marcus.mail@wtnet.de]
>> Sent: Thursday, April 7, 2016 02:10
>> To: dev@openoffice.apache.org
>> Cc: qa@openoffice.apache.org
>> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>>
> [ ... ]
>> 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-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by "Dennis E. Hamilton" <de...@acm.org>.
My only concern is that this is a giant CTR and pretty much assures that the "R" will not happen.
So be it.
However, do not disable the issues mails for any reason. There is a difference between R not happening and R not being possible.
- Dennis
> -----Original Message-----
> From: Marcus [mailto:marcus.mail@wtnet.de]
> Sent: Thursday, April 7, 2016 02:10
> To: dev@openoffice.apache.org
> Cc: qa@openoffice.apache.org
> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>
[ ... ]
> 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-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
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: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Carl Marcum <cm...@apache.org>.
On 04/06/2016 06:43 PM, Kay Schenk wrote:
> 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?
Off topic...
I started going through some of the NetBeans related issues last evening.
Most are very old. In some cases I found the proposed code changes had
been made but I couldn't tell when because it was prior to the Apache
migration.
I RESOLVED-OBSOLETE very old ones I could not verify and RESOLVED-FIXED
ones I could.
Thanks,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
> [...]
>
> 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?
many issues are commented with "fixed in CMS xyz" but there are no real
commits visible. Not every CWS was committed into Trunk before the
project and software was transferred to Apache.
So, do we have a list of outstanding CWS from 2011 that were not
transferred to Apache?
Thanks
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
Posted by Marcus <ma...@wtnet.de>.
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-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org