Re: Issues need 4.2.0 as Target Milestone
Marcus wrote: Target milestones depend on the product in BZ. There is no 4.2.0 target right now (except for "gsl"). I marked (in the past) several issues as target 4.2.0, not only in gsl. Now I see that in https://bz.apache.org/ooo/query.cgi the Target Milestone box contains both "4.2.0" and "AOO 4.2.0". The latter should not be there, whatever product one chooses. But now there is a new flag "4.2.0_release_blocker" which can maybe help in the meantime. Thanks! Of course, for a 4.2.0 release, the meaning is different than in the past. It will mean "something that is not fixed yet and that it must fixed by 4.2.0" (and it will make sense to use it when closer to the RC). Since we have no branch for 4.2.0 yet, and we won't until we are close to the release, it will not mean "something that is fixed in trunk and should ported to the release branch" for the moment. Regards, Andrea. - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Can we add the value "N/A" to the Target Milestone field
[Top-Posting] OK, as there were no further comments and no real disagree I'll create a new RESOLVED - NOCODEFIX resolution status. This status should be set when an issue was solved with no change in the source code (e.g., user requests or how-to questions). For every fix that touches the source code please use as always the RESOLVED - FIXED resolution status. Marcus Am 03/26/2016 10:58 AM, schrieb Marcus: Am 03/26/2016 10:50 AM, schrieb Andrea Pescetti: Marcus wrote: Am 03/26/2016 12:13 AM, schrieb Andrea Pescetti: If the aim is to create less confusion, all proposals I've seen have the result of bringing more confusion! So: I don't see why this brings more confusion. It's the opposite, one status for "resolved with a code fix" and the other for "resolved somehow else". It brings more confusion since it would need to be explained explicitly (because DONE or MANAGED would apply, looking purely at their meaning, to a code fix too, and it's only a convention that we use them for "no-code" fixes only). maybe, but the whole BZ can be confusing - especially for normal users. ;-) > And if we have more intuitive options I feel this would be better. Do you have any idea in mind? It doesn't have to be "NOCODE", but it should be something that means "nothing to do with code", and DONE does not really convey the right meaning here. Then NOCODEFIX sounds more concrete. Yes, NOCODEFIX sounds good too. Again, so long as it is a word that a developer cannot be mistaken into choosing instead of FIXED, it will be OK for me. What we want to avoid is that a developer accidentally uses DONE for a code fix and the issue is suddenly not listed in QA and similar. I got the idea to rename FIXED into FIXEDINCODE. Unfortunatelly, it's a default and therefore a non-changeable name. :-( - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Issues need 4.2.0 as Target Milestone
Am 03/31/2016 07:19 PM, schrieb Andrea Pescetti: Marcus wrote: Target milestones depend on the product in BZ. There is no 4.2.0 target right now (except for "gsl"). I marked (in the past) several issues as target 4.2.0, not only in gsl. Now I see that in https://bz.apache.org/ooo/query.cgi the Target Milestone box contains both "4.2.0" and "AOO 4.2.0". The latter should not be there, whatever product one chooses. the "AOO ..." targerts are coming from disabled products. Issues cannot be created within these products. However with a query they are of course reachable. It seems I need some more time to fix this also. Then we should be so consequent and do the same for the version values. But now there is a new flag "4.2.0_release_blocker" which can maybe help in the meantime. Thanks! Of course, for a 4.2.0 release, the meaning is different than in the past. It will mean "something that is not fixed yet and that it must fixed by 4.2.0" (and it will make sense to use it when closer to the RC). Since we have no branch for 4.2.0 yet, and we won't until we are close to the release, it will not mean "something that is fixed in trunk and should ported to the release branch" for the moment. So, you mean it would be better to disable the flag for the time being? Marcus - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Can we add the value "N/A" to the Target Milestone field
Am 03/31/2016 07:40 PM, schrieb Andrea Pescetti: Marcus wrote: OK, as there were no further comments and no real disagree I'll create a new RESOLVED - NOCODEFIX resolution status. This status should be set when an issue was solved with no change in the source code (e.g., user requests or how-to questions). What's the maximum length? Maybe FIXED_WITHOUT_CODE is even more intuitive (but OK for me with the other option too!). I've created both and got no problem or error message. OK, you won ;- ) : New status is FIXED_WITHOUT_CODE. Marcus - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Issues need 4.2.0 as Target Milestone
Am 03/31/2016 08:26 PM, schrieb Marcus: Am 03/31/2016 07:19 PM, schrieb Andrea Pescetti: Marcus wrote: Target milestones depend on the product in BZ. There is no 4.2.0 target right now (except for "gsl"). I marked (in the past) several issues as target 4.2.0, not only in gsl. Now I see that in https://bz.apache.org/ooo/query.cgi the Target Milestone box contains both "4.2.0" and "AOO 4.2.0". The latter should not be there, whatever product one chooses. the "AOO ..." targerts are coming from disabled products. Issues cannot be created within these products. However with a query they are of course reachable. It seems I need some more time to fix this also. Then we should be so consequent and do the same for the version values. Done: target milestones Todo: versions But now there is a new flag "4.2.0_release_blocker" which can maybe help in the meantime. Thanks! Of course, for a 4.2.0 release, the meaning is different than in the past. It will mean "something that is not fixed yet and that it must fixed by 4.2.0" (and it will make sense to use it when closer to the RC). Since we have no branch for 4.2.0 yet, and we won't until we are close to the release, it will not mean "something that is fixed in trunk and should ported to the release branch" for the moment. So, you mean it would be better to disable the flag for the time being? Marcus - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
