incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: [DISCUSS] Bug reporting, handling rules
Date Thu, 08 Sep 2011 18:03:31 GMT
There's some great material there.  I did not review closely.

It is my thinking that this material should be preserved in an appropriate way.

I agree that the top level should make it easy to file a bug and offer links to progressively-deeper
detail elsewhere.  Users with interest in knowing more can go there; others need not be distracted
by too much information in their way.

Many of the current links don't work and no discussion has occurred on what would replace
"QA team" and "QA project" if anything.  Also, is there a counterpart of the QA review of
issue postings in the Apache OOo Bugzilla handling?  Should there be?

Meanwhile, there is a disconnect between that material and the new Bugzilla.  

Since these pages and are going to be there for an indeterminate time, maybe
it is good to look into being more deliberate, seeking migration progressions that don't leave
so many broken or inappropriate connections.  

It is my thinking that some survey of interdependencies is appropriate so that damage-control
can be injected and the users are not disturbed.

QUESTION: Is it possible to perform maintenance on these pages where they now are or must
change of hosting occur so that repairs can be made?

 - Dennis

-----Original Message-----
From: Marcus (OOo) [] 
Sent: Thursday, September 08, 2011 06:42
Subject: Re: [DISCUSS] Bug reporting, handling rules

Am 09/08/2011 10:37 AM, schrieb Reizinger Zoltán:
> Hi all,
> Start again, the my earlier try was alienated.
> As a first builds starts, and OOo Bugzilla migrated to Apache, needs to
> think about how we will use it.
> On OOo QA site can be found three page which says about issues/bug
> issuing "rules" which the OOo project followed, and Bugzilla was
> customized accordingly:
> This time the bugzilla migrated, could stick to these rules, which
> worked in most cases.
> We want to change it?
> It is a time to start to think about.
> Regards,
> Zoltan

IMHO 3 pages are 2 too much. A single page that describes the howto 
should be enough, especially for non-dev's. Normally these just want to 
forward a bug, feature request, etc. to us.

I don't find a sentence that only English language is accepted to 
describe the problem. Surely a chance to add this.


View raw message