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 i
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
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
Am 03/31/2016 01:54 AM, schrieb Kay Schenk:
Well a few days ago, I changed a bunch of RESOLVED-FIXED to
4.2.0 milestone so I just assumed it was available for all
issues:
https://bz.apache.org/ooo/buglist.cgi?query_format=advanced&resolution=---&target_milestone=4.2.0
So confusing to say the le
Hi --
Well a few days ago, I changed a bunch of RESOLVED-FIXED to
4.2.0 milestone so I just assumed it was available for all
issues:
https://bz.apache.org/ooo/buglist.cgi?query_format=advanced&resolution=---&target_milestone=4.2.0
So confusing to say the least.
Anyway, thank you.
On 03/30/2016
Target milestones depend on the product in BZ. There is no 4.2.0 target
right now (except for "gsl"). Targets have to be created manually for
every product. I'll do this tomorrow as it's already late here.
But now there is a new flag "4.2.0_release_blocker" which can maybe help
in the meantime
I'm not sure how this happened but it seems not all issues
can access 4.2.0 as Target Milestone. I would think all
issues could access the same Target Milestone menu.
I hope this can be corrected. Thanks.
--
MzK
"Time spent with cats is never wasted."