You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Dave Fisher <da...@comcast.net> on 2011/06/16 20:42:54 UTC

Fwd: Moving OOo Bugzilla Database into ASF Infrastructure

Hi -

I queried the infrastructure list about what is possible, and Mark Thomas replied. He might have a preference based on the details of the current, customized OOo issue tracker.

Whoever knows the details, please reply.

Regards,
Dave

Begin forwarded message:

> From: Mark Thomas <ma...@apache.org>
> Date: June 16, 2011 10:56:45 AM PDT
> To: Dave Fisher <da...@comcast.net>
> Cc: Apache Infrastructure <in...@apache.org>
> Subject: Re: Moving OOo Bugzilla Database into ASF Infrastructure
> 
> On 16/06/2011 18:11, Dave Fisher wrote:
>> Hi Guys,
> 
> Hi. I'm replying as I'm the person who currently looks after our issue
> trackers.
> 
>> One of the big issues in moving OOo into the podling is getting an Issue tracker functional.
>> 
>> There are over 100,000 issues.
> 
> That is a reasonable number. Currently the ASF Jira has ~200k, main BZ
> ~50k and SABZ ~7k. Another 100k shouldn't be an issue unless that
> database is huge.
> 
>> The database is currently active.
>> 
>> The most critical migration factor is preserving the Bugzilla IDs.
> 
> No problem. Whatever route we take, that is do-able.
> 
>> There is no preference one way or another on JIRA vs. Bugzilla.
> 
> I may have a preference depending on the answer to the following questions:
> 
> How much customization has been applied to the OOo bugzilla. To put it
> another way, how painful is it going to be up upgrade to BZ 4.0.x? If it
> is going to be painful is there anyone from OOo that is willing to do
> the work and support it going forward?
> 
> What database is currently used for the BZ instance?
> 
> How big is a current full backup?
> 
>> OOo issue tracker link - http://qa.openoffice.org/issue_handling/pre_submission.html
>> 
>> Language is an issue. A user facing bug tracker needs to allow for other languages -http://qa.openoffice.org/issue_handling/submission_gateway.html
> 
> I believe BZ and Jira both support that. Is there anything you need that
> isn't available out of the box?
> 
>> One suggestion was to have a separate Bugzilla for OOo which would automatically preserve the IDs. I notice that SpamAssassin has a separate bugzilla.
> 
> That is certainly an option. Importing into Jira is the other.
> 
>> One negative to JIRA expressed on the list is that someone is labeled as "Project Lead". I've used JIRA at work for 9 years. and we could have an email list be the lead can't we?
> 
> No. The ASF does not permit mailing lists to be used that way due to
> security concerns with password resets and public mailing lists. There
> are simple ways around this.
> 
>> What does Infrastructure prefer? Are there already solutions available?
> 
> That depends on the answer to the questions above.
> 
> Mark
> 
> 


Re: Moving OOo Bugzilla Database into ASF Infrastructure

Posted by Raphael Bircher <r....@gmx.ch>.
Hi at all

Am 16.06.11 20:58, schrieb Stephan Bergmann:
> On Thu, Jun 16, 2011 at 8:42 PM, Dave Fisher<da...@comcast.net>  wrote:
>
>>> From: Mark Thomas<ma...@apache.org>
>>> On 16/06/2011 18:11, Dave Fisher wrote:
>>>> Language is an issue. A user facing bug tracker needs to allow for other
>> languages -http://qa.openoffice.org/issue_handling/submission_gateway.html
>
> Do you mean the "By Language" section on that page leads to bugzilla user
> interface in the respective languages?  That is not the case.  Rather, it
> merely leads to entering a new issue with an appropriately preset
> "component" field etc.  AFAIK, the OOo bugzilla user interface is always in
> English.
>
> (And, sorry, I do not know any answers for the more pressing questions about
> customization, database, etc.)
I will try to find out all this, I'm also registred at the infra-dev 
from Apache. If sameone of Oracle have internal knowage of the kenai 
infrastructure, then it's maybe better to register at 
infrastructure@apache.org. So we have all the discussions at the right 
place.

Greetings Raphael

-- 
My private Homepage: http://www.raphaelbircher.ch/

Re: Moving OOo Bugzilla Database into ASF Infrastructure

Posted by Stephan Bergmann <st...@googlemail.com>.
On Thu, Jun 16, 2011 at 9:27 PM, Dave Fisher <da...@comcast.net> wrote:

>
> On Jun 16, 2011, at 11:58 AM, Stephan Bergmann wrote:
>
> > On Thu, Jun 16, 2011 at 8:42 PM, Dave Fisher <da...@comcast.net>
> wrote:
> >
> >>> From: Mark Thomas <ma...@apache.org>
> >>> On 16/06/2011 18:11, Dave Fisher wrote:
> >>>> Language is an issue. A user facing bug tracker needs to allow for
> other
> >> languages -
> http://qa.openoffice.org/issue_handling/submission_gateway.html
> >
> >
> > Do you mean the "By Language" section on that page leads to bugzilla user
> > interface in the respective languages?  That is not the case.  Rather, it
> > merely leads to entering a new issue with an appropriately preset
> > "component" field etc.  AFAIK, the OOo bugzilla user interface is always
> in
> > English.
> >
> > (And, sorry, I do not know any answers for the more pressing questions
> about
> > customization, database, etc.)
>
> Thanks, that was helpful. One less consideration.
>
> I gather that there are so many differing component combinations that this
> form makes sure that issues go towards the correct OOo "project"?


Exactly.

-Stephan

Re: Moving OOo Bugzilla Database into ASF Infrastructure

Posted by Dave Fisher <da...@comcast.net>.
On Jun 16, 2011, at 11:58 AM, Stephan Bergmann wrote:

> On Thu, Jun 16, 2011 at 8:42 PM, Dave Fisher <da...@comcast.net> wrote:
> 
>>> From: Mark Thomas <ma...@apache.org>
>>> On 16/06/2011 18:11, Dave Fisher wrote:
>>>> Language is an issue. A user facing bug tracker needs to allow for other
>> languages -http://qa.openoffice.org/issue_handling/submission_gateway.html
> 
> 
> Do you mean the "By Language" section on that page leads to bugzilla user
> interface in the respective languages?  That is not the case.  Rather, it
> merely leads to entering a new issue with an appropriately preset
> "component" field etc.  AFAIK, the OOo bugzilla user interface is always in
> English.
> 
> (And, sorry, I do not know any answers for the more pressing questions about
> customization, database, etc.)

Thanks, that was helpful. One less consideration.

I gather that there are so many differing component combinations that this form makes sure that issues go towards the correct OOo "project"?

Regards,
Dave



Re: Moving OOo Bugzilla Database into ASF Infrastructure

Posted by Stephan Bergmann <st...@googlemail.com>.
On Thu, Jun 16, 2011 at 8:42 PM, Dave Fisher <da...@comcast.net> wrote:

> > From: Mark Thomas <ma...@apache.org>
> > On 16/06/2011 18:11, Dave Fisher wrote:
> >> Language is an issue. A user facing bug tracker needs to allow for other
> languages -http://qa.openoffice.org/issue_handling/submission_gateway.html


Do you mean the "By Language" section on that page leads to bugzilla user
interface in the respective languages?  That is not the case.  Rather, it
merely leads to entering a new issue with an appropriately preset
"component" field etc.  AFAIK, the OOo bugzilla user interface is always in
English.

(And, sorry, I do not know any answers for the more pressing questions about
customization, database, etc.)

-Stephan

Re: Fwd: Moving OOo Bugzilla Database into ASF Infrastructure

Posted by Marcus Lange <ma...@wtnet.de>.
Hi,

not a big or critical thing at the beginning, but ...

There is one thing that was customized after the migration to Kenai was 
done.

Normally you have to add, rename, delete new milestone targets and 
versions for every product that is available. OOo has dozends (it's not 
only Writer, Calc, Impress, it's also every language code). A lot of 
manual work; especially when we have released every 1-2 weeks a new 
developer snapshot.

So, there is now a little mask to:

* add a new target and version
* or rename an existing one
* or to delete a target and version

This permission was only granted to some people. When logging into BZ 
and opening the admin webpage, there is a link to a "targetadmin.cgi" 
file that does the stuff described above:

Adjust bug targets

* Adjust milestone targets and versions for all products at once.

It would be great if this could be implemented into the new instance, 
too. Currently it seems that BZ 3.2.10 is running. Sorry, I haven't 
found any documentation if this special thing is already implemented in 
newer releases.

Marcus



Am 06/16/2011 08:42 PM, schrieb Dave Fisher:
>> How much customization has been applied to the OOo bugzilla. To put it
>> another way, how painful is it going to be up upgrade to BZ 4.0.x? If it
>> is going to be painful is there anyone from OOo that is willing to do
>> the work and support it going forward?


-- 

Ciao

Marcus