You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Oliver-Rainer Wittmann <or...@googlemail.com> on 2012/03/02 14:38:47 UTC
[RELEASE] Bug 118098 - Text box filled with zeroes
Hi,
Issue - https://issues.apache.org/ooo/show_bug.cgi?id=118098 - is no AOO 3.4
release blocker from my point of view. I have reproduced this defect in OOo 3.1
and OOo 3.4
Best regards, Oliver.
P.S.: Sorry for the noise regarding our potential release blockers, but I am
trying to get an overview about the release blockers which we need to fix for
our AOO 3.4 release.
Re: [BZ] Disable the "release blocker" flag to be used only by everyone
(was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 3/3/12 12:02 AM, Dave Fisher wrote:
>
> On Mar 2, 2012, at 2:46 PM, Marcus (OOo) wrote:
>
>> Am 03/02/2012 11:30 PM, schrieb Rob Weir:
>>> On Fri, Mar 2, 2012 at 5:20 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>>>> Am 03/02/2012 10:49 PM, schrieb Rob Weir:
>>>>
>>>>> On Fri, Mar 2, 2012 at 4:34 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>>>>>>
>>>>>> In order prevent this cleanup task again and again (for the next weeks,
>>>>>> new
>>>>>> releases, etc.)
>>>>>>
>>>>>> -and-
>>>>>>
>>>>>> To take the discussions into this ML and out of our BZ.
>>>>>>
>>>>>> Is it possible to disable the "release blocker" flag for everyone's use?
>>>>>> When only a few people can set the flag to "+" then we can discuss first
>>>>>> on
>>>>>> the ML and when we have consensus it will be set to "+".
>>>>>>
>>>>>
>>>>> Right now only those in the "relman" group can +grant or -deny the
>>>>> "release blocker" flag. There are only 8 people in that group right
>>>>> now.
>>>>
>>>>
>>>> OK, then it was maybe just a subjective feeling that the flag was more
>>>> stressed than necessary in the last few days/weeks. Or there is at least a
>>>> difference between the "?" and the "+" / "-" status.
>>>>
>>>
>>> Many of us are working together for the first time. So it is likely
>>> that we don't even all agree on what a "release blocker" means. If we
>>> agreed on criteria, then I think there would be fewer issues like
>>> this. But maybe having these discussions is how we converge on an
>>> understanding of what a blocking issue is?
>>
>> Then there is short way out: ;-)
>>
>> http://wiki.services.openoffice.org/wiki/Stopper
>>
>> When we can agree on these criteria, the sorting of release blocker will be easier and faster.
>
> Looks like reasonable criteria to me.
>
> BTW - the part under "How to promote/nominate a Stopper issue" will need to be rewritten.
>
done, at least improved to cover the current procedure
Juergen
> Regards,
> Dave
>
>
>>
>> Marcus
>>
>>
>>
>>>>> Anyone in the "canconfirm" group is able to request this flag. Not
>>>>> everyone is a member of "canconfirm". There are only 559 members,
>>>>> mainly those who had elevated permissions in the legacy BZ instance.
>>>>> It also includes everyone with an Apache email address.
>>>>>
>>>>> So I think we're doing what you are suggesting. We're discussing the
>>>>> bugs where someone has requested "release blocker" status, and then
>>>>> decided whether to grant or deny that status.
>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>
>>>>> Discuss now, discuss later, it is all the same thing, right?
>>>>>
>>>>> -Rob
>>>>>
>>>>>> Marcus
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
>>>>>>>
>>>>>>>
>>>>>>> P.S.: Sorry for the noise regarding our potential release blockers, but
>>>>>>> I am trying to get an overview about the release blockers which we need
>>>>>>> to fix for our AOO 3.4 release.
>
Re: [BZ] Disable the "release blocker" flag to be used only by everyone (was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by Dave Fisher <da...@comcast.net>.
On Mar 2, 2012, at 2:46 PM, Marcus (OOo) wrote:
> Am 03/02/2012 11:30 PM, schrieb Rob Weir:
>> On Fri, Mar 2, 2012 at 5:20 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>>> Am 03/02/2012 10:49 PM, schrieb Rob Weir:
>>>
>>>> On Fri, Mar 2, 2012 at 4:34 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>>>>>
>>>>> In order prevent this cleanup task again and again (for the next weeks,
>>>>> new
>>>>> releases, etc.)
>>>>>
>>>>> -and-
>>>>>
>>>>> To take the discussions into this ML and out of our BZ.
>>>>>
>>>>> Is it possible to disable the "release blocker" flag for everyone's use?
>>>>> When only a few people can set the flag to "+" then we can discuss first
>>>>> on
>>>>> the ML and when we have consensus it will be set to "+".
>>>>>
>>>>
>>>> Right now only those in the "relman" group can +grant or -deny the
>>>> "release blocker" flag. There are only 8 people in that group right
>>>> now.
>>>
>>>
>>> OK, then it was maybe just a subjective feeling that the flag was more
>>> stressed than necessary in the last few days/weeks. Or there is at least a
>>> difference between the "?" and the "+" / "-" status.
>>>
>>
>> Many of us are working together for the first time. So it is likely
>> that we don't even all agree on what a "release blocker" means. If we
>> agreed on criteria, then I think there would be fewer issues like
>> this. But maybe having these discussions is how we converge on an
>> understanding of what a blocking issue is?
>
> Then there is short way out: ;-)
>
> http://wiki.services.openoffice.org/wiki/Stopper
>
> When we can agree on these criteria, the sorting of release blocker will be easier and faster.
Looks like reasonable criteria to me.
BTW - the part under "How to promote/nominate a Stopper issue" will need to be rewritten.
Regards,
Dave
>
> Marcus
>
>
>
>>>> Anyone in the "canconfirm" group is able to request this flag. Not
>>>> everyone is a member of "canconfirm". There are only 559 members,
>>>> mainly those who had elevated permissions in the legacy BZ instance.
>>>> It also includes everyone with an Apache email address.
>>>>
>>>> So I think we're doing what you are suggesting. We're discussing the
>>>> bugs where someone has requested "release blocker" status, and then
>>>> decided whether to grant or deny that status.
>>>>
>>>>> What do you think?
>>>>>
>>>>
>>>> Discuss now, discuss later, it is all the same thing, right?
>>>>
>>>> -Rob
>>>>
>>>>> Marcus
>>>>>
>>>>>
>>>>>
>>>>> Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
>>>>>>
>>>>>>
>>>>>> P.S.: Sorry for the noise regarding our potential release blockers, but
>>>>>> I am trying to get an overview about the release blockers which we need
>>>>>> to fix for our AOO 3.4 release.
Re: [BZ] Disable the "release blocker" flag to be used only by everyone
(was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 03/02/2012 11:30 PM, schrieb Rob Weir:
> On Fri, Mar 2, 2012 at 5:20 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>> Am 03/02/2012 10:49 PM, schrieb Rob Weir:
>>
>>> On Fri, Mar 2, 2012 at 4:34 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>>>>
>>>> In order prevent this cleanup task again and again (for the next weeks,
>>>> new
>>>> releases, etc.)
>>>>
>>>> -and-
>>>>
>>>> To take the discussions into this ML and out of our BZ.
>>>>
>>>> Is it possible to disable the "release blocker" flag for everyone's use?
>>>> When only a few people can set the flag to "+" then we can discuss first
>>>> on
>>>> the ML and when we have consensus it will be set to "+".
>>>>
>>>
>>> Right now only those in the "relman" group can +grant or -deny the
>>> "release blocker" flag. There are only 8 people in that group right
>>> now.
>>
>>
>> OK, then it was maybe just a subjective feeling that the flag was more
>> stressed than necessary in the last few days/weeks. Or there is at least a
>> difference between the "?" and the "+" / "-" status.
>>
>
> Many of us are working together for the first time. So it is likely
> that we don't even all agree on what a "release blocker" means. If we
> agreed on criteria, then I think there would be fewer issues like
> this. But maybe having these discussions is how we converge on an
> understanding of what a blocking issue is?
Then there is short way out: ;-)
http://wiki.services.openoffice.org/wiki/Stopper
When we can agree on these criteria, the sorting of release blocker will
be easier and faster.
Marcus
>>> Anyone in the "canconfirm" group is able to request this flag. Not
>>> everyone is a member of "canconfirm". There are only 559 members,
>>> mainly those who had elevated permissions in the legacy BZ instance.
>>> It also includes everyone with an Apache email address.
>>>
>>> So I think we're doing what you are suggesting. We're discussing the
>>> bugs where someone has requested "release blocker" status, and then
>>> decided whether to grant or deny that status.
>>>
>>>> What do you think?
>>>>
>>>
>>> Discuss now, discuss later, it is all the same thing, right?
>>>
>>> -Rob
>>>
>>>> Marcus
>>>>
>>>>
>>>>
>>>> Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
>>>>>
>>>>>
>>>>> P.S.: Sorry for the noise regarding our potential release blockers, but
>>>>> I am trying to get an overview about the release blockers which we need
>>>>> to fix for our AOO 3.4 release.
Re: [BZ] Disable the "release blocker" flag to be used only by
everyone (was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by Rob Weir <ro...@apache.org>.
On Fri, Mar 2, 2012 at 5:20 PM, Marcus (OOo) <ma...@wtnet.de> wrote:
> Am 03/02/2012 10:49 PM, schrieb Rob Weir:
>
>> On Fri, Mar 2, 2012 at 4:34 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>>>
>>> In order prevent this cleanup task again and again (for the next weeks,
>>> new
>>> releases, etc.)
>>>
>>> -and-
>>>
>>> To take the discussions into this ML and out of our BZ.
>>>
>>> Is it possible to disable the "release blocker" flag for everyone's use?
>>> When only a few people can set the flag to "+" then we can discuss first
>>> on
>>> the ML and when we have consensus it will be set to "+".
>>>
>>
>> Right now only those in the "relman" group can +grant or -deny the
>> "release blocker" flag. There are only 8 people in that group right
>> now.
>
>
> OK, then it was maybe just a subjective feeling that the flag was more
> stressed than necessary in the last few days/weeks. Or there is at least a
> difference between the "?" and the "+" / "-" status.
>
Many of us are working together for the first time. So it is likely
that we don't even all agree on what a "release blocker" means. If we
agreed on criteria, then I think there would be fewer issues like
this. But maybe having these discussions is how we converge on an
understanding of what a blocking issue is?
-Rob
> Marcus
>
>
>
>
>> Anyone in the "canconfirm" group is able to request this flag. Not
>> everyone is a member of "canconfirm". There are only 559 members,
>> mainly those who had elevated permissions in the legacy BZ instance.
>> It also includes everyone with an Apache email address.
>>
>> So I think we're doing what you are suggesting. We're discussing the
>> bugs where someone has requested "release blocker" status, and then
>> decided whether to grant or deny that status.
>>
>>> What do you think?
>>>
>>
>> Discuss now, discuss later, it is all the same thing, right?
>>
>> -Rob
>>
>>> Marcus
>>>
>>>
>>>
>>> Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
>>>>
>>>>
>>>> P.S.: Sorry for the noise regarding our potential release blockers, but
>>>> I am trying to get an overview about the release blockers which we need
>>>> to fix for our AOO 3.4 release.
Re: [BZ] Disable the "release blocker" flag to be used only by everyone
(was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 03/02/2012 10:49 PM, schrieb Rob Weir:
> On Fri, Mar 2, 2012 at 4:34 PM, Marcus (OOo)<ma...@wtnet.de> wrote:
>> In order prevent this cleanup task again and again (for the next weeks, new
>> releases, etc.)
>>
>> -and-
>>
>> To take the discussions into this ML and out of our BZ.
>>
>> Is it possible to disable the "release blocker" flag for everyone's use?
>> When only a few people can set the flag to "+" then we can discuss first on
>> the ML and when we have consensus it will be set to "+".
>>
>
> Right now only those in the "relman" group can +grant or -deny the
> "release blocker" flag. There are only 8 people in that group right
> now.
OK, then it was maybe just a subjective feeling that the flag was more
stressed than necessary in the last few days/weeks. Or there is at least
a difference between the "?" and the "+" / "-" status.
Marcus
> Anyone in the "canconfirm" group is able to request this flag. Not
> everyone is a member of "canconfirm". There are only 559 members,
> mainly those who had elevated permissions in the legacy BZ instance.
> It also includes everyone with an Apache email address.
>
> So I think we're doing what you are suggesting. We're discussing the
> bugs where someone has requested "release blocker" status, and then
> decided whether to grant or deny that status.
>
>> What do you think?
>>
>
> Discuss now, discuss later, it is all the same thing, right?
>
> -Rob
>
>> Marcus
>>
>>
>>
>> Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
>>>
>>> P.S.: Sorry for the noise regarding our potential release blockers, but
>>> I am trying to get an overview about the release blockers which we need
>>> to fix for our AOO 3.4 release.
Re: [BZ] Disable the "release blocker" flag to be used only by
everyone (was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by Rob Weir <ro...@apache.org>.
On Fri, Mar 2, 2012 at 4:34 PM, Marcus (OOo) <ma...@wtnet.de> wrote:
> In order prevent this cleanup task again and again (for the next weeks, new
> releases, etc.)
>
> -and-
>
> To take the discussions into this ML and out of our BZ.
>
> Is it possible to disable the "release blocker" flag for everyone's use?
> When only a few people can set the flag to "+" then we can discuss first on
> the ML and when we have consensus it will be set to "+".
>
Right now only those in the "relman" group can +grant or -deny the
"release blocker" flag. There are only 8 people in that group right
now.
Anyone in the "canconfirm" group is able to request this flag. Not
everyone is a member of "canconfirm". There are only 559 members,
mainly those who had elevated permissions in the legacy BZ instance.
It also includes everyone with an Apache email address.
So I think we're doing what you are suggesting. We're discussing the
bugs where someone has requested "release blocker" status, and then
decided whether to grant or deny that status.
> What do you think?
>
Discuss now, discuss later, it is all the same thing, right?
-Rob
> Marcus
>
>
>
> Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
>>
>> P.S.: Sorry for the noise regarding our potential release blockers, but
>> I am trying to get an overview about the release blockers which we need
>> to fix for our AOO 3.4 release.
[BZ] Disable the "release blocker" flag to be used only by everyone
(was Re: [RELEASE] Bug 118098 - Text box filled with zeroes)
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
In order prevent this cleanup task again and again (for the next weeks,
new releases, etc.)
-and-
To take the discussions into this ML and out of our BZ.
Is it possible to disable the "release blocker" flag for everyone's use?
When only a few people can set the flag to "+" then we can discuss first
on the ML and when we have consensus it will be set to "+".
What do you think?
Marcus
Am 03/02/2012 02:38 PM, schrieb Oliver-Rainer Wittmann:
> P.S.: Sorry for the noise regarding our potential release blockers, but
> I am trying to get an overview about the release blockers which we need
> to fix for our AOO 3.4 release.
Re: [RELEASE] Bug 118098 - Text box filled with zeroes
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 3/2/12 2:38 PM, Oliver-Rainer Wittmann wrote:
> Hi,
>
> Issue - https://issues.apache.org/ooo/show_bug.cgi?id=118098 - is no AOO
> 3.4 release blocker from my point of view. I have reproduced this defect
> in OOo 3.1 and OOo 3.4
I agree again
Juergen
>
> Best regards, Oliver.
>
> P.S.: Sorry for the noise regarding our potential release blockers, but
> I am trying to get an overview about the release blockers which we need
> to fix for our AOO 3.4 release.