Hi,
On 22.06.2013 09:55, Oliver-Rainer Wittmann wrote:
Hi,
Am 20.06.2013 um 17:09 schrieb Oliver-Rainer Wittmann
:
Hi,
On 06.06.2013 13:54, Yuzhen Fan wrote:
Hi All,
Here is the list of identified candidates[1]/[2] which are proposed to
be 4.0.0 release blockers. Please indicate your sele
Hi,
Am 20.06.2013 um 17:09 schrieb Oliver-Rainer Wittmann
:
> Hi,
>
> On 06.06.2013 13:54, Yuzhen Fan wrote:
>> Hi All,
>>
>> Here is the list of identified candidates[1]/[2] which are proposed to
>> be 4.0.0 release blockers. Please indicate your selections for release
>> blockers by giving 1
>IMHO there are no bad ideas here. They are just mistimed ;-)
It would be mad to change the bug policy now, but for the future it might
have an impact.
2013/6/21 Rob Weir
> On Fri, Jun 21, 2013 at 11:09 AM, Sub Phil wrote:
> > Bug policy debate and so on..
> >
> > Well, just sharing experienc
On Fri, Jun 21, 2013 at 11:09 AM, Sub Phil wrote:
> Bug policy debate and so on..
>
> Well, just sharing experience from as a past developper and notorious bug
> fighter.
>
> There is no other point in creating a database of bugs and not treating
> them, than to have an ultra-complicated list of k
Bug policy debate and so on..
Well, just sharing experience from as a past developper and notorious bug
fighter.
There is no other point in creating a database of bugs and not treating
them, than to have an ultra-complicated list of known issues (so complex
that users report are duplicated) and f
On 21.06.2013 13:42, Edwin Sharp wrote:
Dear Andre
This is exactly the problem!
When you grab a bug from the top and critical bugs continuously enter the list -
The minor bugs at the bottom will never get attention.
You make that sound like it where a bad thing.
A bug is critical because it affe
On Thu, Jun 20, 2013 at 2:01 PM, Edwin Sharp wrote:
> Yes.
> please allow to share the following objections:
> 1. in general, bugs shouldn't be rated
> 2. most are crashes - "release blocker" can be other than crash - i.e. copy
> chart from Calc into Writer results in chart area without curve. th
Dear Andre
This is exactly the problem!
When you grab a bug from the top and critical bugs continuously enter the list
-
The minor bugs at the bottom will never get attention.
On Fri, Jun 21, 2013, at 14:24, Andre Fischer wrote:
>
>
> All good ideas.
>
> I would like to add another one. I a
On 21.06.2013 13:09, Sub Phil wrote:
Regarding "classification" of bugs (critical, etc.) and bug fixing.
The core question is how to increase the throughput of bug fixing, i.e.
increase the number of fixes?
If one analyse bug reporting process & fixing, it is usually done as
1/ User report bug
On 21.06.2013 12:39, Edwin Sharp wrote:
My meaning is, respecting current users of OpenOffice who reported bugs and see
those bugs not resolved while new features (sidebar) are being introduced.
I think they deserve at least an explanation how introducing new features is
more important from fix
Regarding "classification" of bugs (critical, etc.) and bug fixing.
The core question is how to increase the throughput of bug fixing, i.e.
increase the number of fixes?
If one analyse bug reporting process & fixing, it is usually done as
1/ User report bug
2/ Tester try to reproduce it, then
2.1
My meaning is, respecting current users of OpenOffice who reported bugs and see
those bugs not resolved while new features (sidebar) are being introduced.
I think they deserve at least an explanation how introducing new features is
more important from fixing bugs that bothers them (after all, the
On 21.06.2013 08:57, Jürgen Schmidt wrote:
On 6/20/13 8:01 PM, Edwin Sharp wrote:
Yes.
please allow to share the following objections:
1. in general, bugs shouldn't be rated
I disagree here and you always rate issues starting with setting a
priority. And as always you can't fix them all with a
Thank you for this feedback.
On Fri, Jun 21, 2013, at 9:57, Jürgen Schmidt wrote:
> On 6/20/13 8:01 PM, Edwin Sharp wrote:
> > Yes.
> > please allow to share the following objections:
> > 1. in general, bugs shouldn't be rated
>
> I disagree here and you always rate issues starting with setting
Hi,
On 21.06.2013 08:57, Jürgen Schmidt wrote:
On 6/20/13 8:01 PM, Edwin Sharp wrote:
Yes. please allow to share the following objections: 1. in general,
bugs shouldn't be rated
I disagree here and you always rate issues starting with setting a
priority. And as always you can't fix them all w
On 6/20/13 8:01 PM, Edwin Sharp wrote:
> Yes.
> please allow to share the following objections:
> 1. in general, bugs shouldn't be rated
I disagree here and you always rate issues starting with setting a
priority. And as always you can't fix them all with a fix number of
developers. It simply doe
Yes.
please allow to share the following objections:
1. in general, bugs shouldn't be rated
2. most are crashes - "release blocker" can be other than crash - i.e. copy
chart from Calc into Writer results in chart area without curve. this is a huge
bug that doesn't involve a crash
3. with all the
Hi,
On 06.06.2013 13:54, Yuzhen Fan wrote:
Hi All,
Here is the list of identified candidates[1]/[2] which are proposed to
be 4.0.0 release blockers. Please indicate your selections for release
blockers by giving 1 vote to 1 bug (the vote field is beside the
importance field, in a bug form). We
On Fri, Jun 7, 2013 at 10:34 AM, I. Park wrote:
> Hello Rob,
>
> O.k., I'm not too sure if your "incorrectly marked CONFIRMED" topic
> mentioned below has to do with Bugzilla, but I noticed on couple
> occasions that when filling out new bugs the CONFIRMED is set by
> default. I had to go back a
Hello Rob,
O.k., I'm not too sure if your "incorrectly marked CONFIRMED" topic
mentioned below has to do with Bugzilla, but I noticed on couple
occasions that when filling out new bugs the CONFIRMED is set by
default. I had to go back a few times and change it to UNCONFIRMED.
Just my two-cents.
On Thu, Jun 6, 2013 at 8:47 AM, Jürgen Schmidt wrote:
> On 6/6/13 1:54 PM, Yuzhen Fan wrote:
>> Hi All,
>>
>> Here is the list of identified candidates[1]/[2] which are proposed to
>> be 4.0.0 release blockers. Please indicate your selections for release
>> blockers by giving 1 vote to 1 bug (the
Yes.
As long as we don't waste time implementing kindergarten user interfaces and
worrying about compatibility to propriety file formats.
On Thu, Jun 6, 2013, at 18:45, Peter Junge wrote:
> That implies all bugs will get fixed if their priority is above low?
---
That implies all bugs will get fixed if their priority is above low?
On 6/6/2013 11:32 PM, Edwin Sharp wrote:
Don't be naive.
A bug with a low priority will never get fixed.
On Thu, Jun 6, 2013, at 16:20, Jürgen Schmidt wrote:
On 6/6/13 2:13 PM, Edwin Sharp wrote:
you are correct but I belie
Don't be naive.
A bug with a low priority will never get fixed.
On Thu, Jun 6, 2013, at 16:20, Jürgen Schmidt wrote:
> On 6/6/13 2:13 PM, Edwin Sharp wrote:
>
>
> you are correct but I believe it is intended to get a priority list. We
> have long list of bugs and that can't be fixed all. We alway
On 6/6/13 2:13 PM, Edwin Sharp wrote:
> I can understand voting for a new logo.
>
> But voting for bugs?
>
> A bug is a bug and needs to be fixed.
you are correct but I believe it is intended to get a priority list. We
have long list of bugs and that can't be fixed all. We always get new
bugs an
On 6/6/13 1:54 PM, Yuzhen Fan wrote:
> Hi All,
>
> Here is the list of identified candidates[1]/[2] which are proposed to
> be 4.0.0 release blockers. Please indicate your selections for release
> blockers by giving 1 vote to 1 bug (the vote field is beside the
> importance field, in a bug form).
I can understand voting for a new logo.
But voting for bugs?
A bug is a bug and needs to be fixed.
On Thu, Jun 6, 2013, at 14:54, Yuzhen Fan wrote:
Hi All,
Here is the list of identified candidates[1]/[2] which are proposed to
be 4.0.0 release blockers. Please indicate your selections for re
Hi All,
Here is the list of identified candidates[1]/[2] which are proposed to be
4.0.0 release blockers. Please indicate your selections for release
blockers by giving 1 vote to 1 bug (the vote field is beside the importance
field, in a bug form). We hope to get the vote score this week, any bugs
28 matches
Mail list logo
