You are viewing a plain text version of this content. The canonical link for it is here.
Posted to qa@openoffice.apache.org by dhyanendra singh <si...@gmail.com> on 2014/10/03 07:59:03 UTC
to get bug repositories
Hello,
I am Dhyanandra Singh. I am pursuing M. Tech. from Jaypee Institute
of Information Technology. As my thesis Work I have chosen Automatic
Duplicate bug Detection and want to use bug repository of Apache open
office for that.
I am very thankful to you if you will share your bug repository with me.
Re: to get bug repositories
Posted by dhyanendra singh <si...@gmail.com>.
Rob ,
i can access bug reports now but as my requirement i need one more field
i.e. description/comment by user for each report which is not available to
me as a column.
On Fri, Oct 3, 2014 at 8:02 PM, Rob Weir <ro...@robweir.com> wrote:
> On Fri, Oct 3, 2014 at 7:56 AM, Andrea Pescetti <pe...@apache.org>
> wrote:
> > On 03/10/2014 dhyanendra singh wrote:
> >>
> >> i have created an account with username singh.cs.ind@gmail.com
> >> <ma...@gmail.com> at https://issues.apache.org/ooo/ as
> you
> >> suggested.
> >> now tell me how can get access to the repositories.
> >
> >
> > What do you need exactly? You already have access to all bugs by
> registering
> > (I mean: from the website you can access every bug and make queries). Do
> you
> > want to be able to download the full Bugzilla database as one file? In
> that
> > case, what information can be anonymized? I'm not sure this can be done
> and
> > for sure I can't do it since I don't have the required permissions, but
> if
> > the request is clear we can investigate and see what's possible.
> >
>
> As Andrea mentions we're unlikely to give you a copy of the underlying
> Bugzilla database, since that has personal information like login
> records, hashed passwords, email addresses, etc.
>
> However, in addition to browsing Bugzilla through the UI there is also
> a REST API that you can call to extract BZ records in XML format.
> This makes it easier (assuming you can do some simple scripting to
> process the XML) to automate some analysis.
>
> For example, to retrieve issue number 60129 you would make this request:
>
> https://issues.apache.org/ooo/show_bug.cgi?ctype=xml&id=60129
>
> And you would receive back this XML:
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
> <!DOCTYPE bugzilla SYSTEM
> "https://issues.apache.org/ooo/page.cgi?id=bugzilla.dtd">
>
> <bugzilla version="4.4.1"
> urlbase="https://issues.apache.org/ooo/"
>
> maintainer="aoo-bugzilla-admin@apache.org"
> >
>
> <bug>
> <bug_id>60129</bug_id>
>
> <creation_ts>2006-01-06 12:51:00 +0000</creation_ts>
> <short_desc>initial table formatting is broken: table does
> not split</short_desc>
> <delta_ts>2013-08-07 14:44:35 +0000</delta_ts>
> <reporter_accessible>1</reporter_accessible>
> <cclist_accessible>1</cclist_accessible>
> <classification_id>2</classification_id>
> <classification>Application</classification>
> <product>Writer</product>
> <component>formatting</component>
> <version>OOo 1.0.0</version>
> <rep_platform>All</rep_platform>
> <op_sys>All</op_sys>
> <bug_status>CONFIRMED</bug_status>
> <resolution></resolution>
>
>
> <bug_file_loc></bug_file_loc>
> <status_whiteboard></status_whiteboard>
> <keywords></keywords>
> <priority>P2</priority>
> <bug_severity>trivial</bug_severity>
> <target_milestone>---</target_milestone>
>
>
> <everconfirmed>1</everconfirmed>
> <reporter>jsc</reporter>
> <assigned_to name="AOO issues mailing list">issues</assigned_to>
> <cc>issues</cc>
>
> <cc>jsc</cc>
>
> <cf_bug_type>DEFECT</cf_bug_type>
> <cf_lastconfirmedver>---</cf_lastconfirmedver>
> <cf_fix_difficulty>---</cf_fix_difficulty>
> <votes>0</votes>
>
> <comment_sort_order>oldest_to_newest</comment_sort_order>
> <long_desc isprivate="0" >
> <commentid>1658113</commentid>
> <comment_count>0</comment_count>
> <who name="">jsc</who>
> <bug_when>2006-01-06 12:51:58 +0000</bug_when>
> <thetext>initial table formatting is broken: table does not split
> after first load</thetext>
> </long_desc><long_desc isprivate="0" >
> <commentid>1658114</commentid>
> <comment_count>1</comment_count>
> <who name="">Mathias_Bauer</who>
> <bug_when>2006-01-20 16:57:21 +0000</bug_when>
> <thetext>We will not finish this until 2.0.2 code freeze ->
> retargetting to 2.0.3</thetext>
> </long_desc><long_desc isprivate="0" >
> <commentid>1658115</commentid>
> <comment_count>2</comment_count>
> <who name="">frank.meies</who>
> <bug_when>2006-04-26 10:48:39 +0000</bug_when>
> <thetext>FME: I discussed this issue with KSO. The code changes
> for this fix will require
> a lot of testing resources, since the code in this area is quite fragile.
> Since
> the time frame for 2.0.3 release is very thight and ressources are
> limited, I
> re-target this issue to 2.0.4.</thetext>
> </long_desc><long_desc isprivate="0" >
> <commentid>1658116</commentid>
> <comment_count>3</comment_count>
> <who name="">frank.meies</who>
> <bug_when>2006-05-15 12:09:33 +0000</bug_when>
> <thetext>.</thetext>
> </long_desc><long_desc isprivate="0" >
> <commentid>1658117</commentid>
> <comment_count>4</comment_count>
> <who name="">frank.meies</who>
> <bug_when>2008-01-14 09:35:31 +0000</bug_when>
> <thetext>Cannot be implemented until code freeze => target
> 3.x</thetext>
> </long_desc>
>
> </bug>
>
> </bugzilla>
>
>
>
> One approach I've used is to narrow down which issues you are
> interested in, via the UI, maybe filter by component or date range or
> status, and from that determine a list of issue numbers. Then you can
> retrieve the XML via calls to the REST API. I have a python script
> that helps with that part of things, if you are interested.
>
>
> Regards,
>
> -Rob
>
>
>
>
> >
> > Regards,
> > Andrea.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: qa-help@openoffice.apache.org
> >
>
Re: to get bug repositories
Posted by Rob Weir <ro...@robweir.com>.
On Fri, Oct 3, 2014 at 7:56 AM, Andrea Pescetti <pe...@apache.org> wrote:
> On 03/10/2014 dhyanendra singh wrote:
>>
>> i have created an account with username singh.cs.ind@gmail.com
>> <ma...@gmail.com> at https://issues.apache.org/ooo/ as you
>> suggested.
>> now tell me how can get access to the repositories.
>
>
> What do you need exactly? You already have access to all bugs by registering
> (I mean: from the website you can access every bug and make queries). Do you
> want to be able to download the full Bugzilla database as one file? In that
> case, what information can be anonymized? I'm not sure this can be done and
> for sure I can't do it since I don't have the required permissions, but if
> the request is clear we can investigate and see what's possible.
>
As Andrea mentions we're unlikely to give you a copy of the underlying
Bugzilla database, since that has personal information like login
records, hashed passwords, email addresses, etc.
However, in addition to browsing Bugzilla through the UI there is also
a REST API that you can call to extract BZ records in XML format.
This makes it easier (assuming you can do some simple scripting to
process the XML) to automate some analysis.
For example, to retrieve issue number 60129 you would make this request:
https://issues.apache.org/ooo/show_bug.cgi?ctype=xml&id=60129
And you would receive back this XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM
"https://issues.apache.org/ooo/page.cgi?id=bugzilla.dtd">
<bugzilla version="4.4.1"
urlbase="https://issues.apache.org/ooo/"
maintainer="aoo-bugzilla-admin@apache.org"
>
<bug>
<bug_id>60129</bug_id>
<creation_ts>2006-01-06 12:51:00 +0000</creation_ts>
<short_desc>initial table formatting is broken: table does
not split</short_desc>
<delta_ts>2013-08-07 14:44:35 +0000</delta_ts>
<reporter_accessible>1</reporter_accessible>
<cclist_accessible>1</cclist_accessible>
<classification_id>2</classification_id>
<classification>Application</classification>
<product>Writer</product>
<component>formatting</component>
<version>OOo 1.0.0</version>
<rep_platform>All</rep_platform>
<op_sys>All</op_sys>
<bug_status>CONFIRMED</bug_status>
<resolution></resolution>
<bug_file_loc></bug_file_loc>
<status_whiteboard></status_whiteboard>
<keywords></keywords>
<priority>P2</priority>
<bug_severity>trivial</bug_severity>
<target_milestone>---</target_milestone>
<everconfirmed>1</everconfirmed>
<reporter>jsc</reporter>
<assigned_to name="AOO issues mailing list">issues</assigned_to>
<cc>issues</cc>
<cc>jsc</cc>
<cf_bug_type>DEFECT</cf_bug_type>
<cf_lastconfirmedver>---</cf_lastconfirmedver>
<cf_fix_difficulty>---</cf_fix_difficulty>
<votes>0</votes>
<comment_sort_order>oldest_to_newest</comment_sort_order>
<long_desc isprivate="0" >
<commentid>1658113</commentid>
<comment_count>0</comment_count>
<who name="">jsc</who>
<bug_when>2006-01-06 12:51:58 +0000</bug_when>
<thetext>initial table formatting is broken: table does not split
after first load</thetext>
</long_desc><long_desc isprivate="0" >
<commentid>1658114</commentid>
<comment_count>1</comment_count>
<who name="">Mathias_Bauer</who>
<bug_when>2006-01-20 16:57:21 +0000</bug_when>
<thetext>We will not finish this until 2.0.2 code freeze ->
retargetting to 2.0.3</thetext>
</long_desc><long_desc isprivate="0" >
<commentid>1658115</commentid>
<comment_count>2</comment_count>
<who name="">frank.meies</who>
<bug_when>2006-04-26 10:48:39 +0000</bug_when>
<thetext>FME: I discussed this issue with KSO. The code changes
for this fix will require
a lot of testing resources, since the code in this area is quite fragile. Since
the time frame for 2.0.3 release is very thight and ressources are limited, I
re-target this issue to 2.0.4.</thetext>
</long_desc><long_desc isprivate="0" >
<commentid>1658116</commentid>
<comment_count>3</comment_count>
<who name="">frank.meies</who>
<bug_when>2006-05-15 12:09:33 +0000</bug_when>
<thetext>.</thetext>
</long_desc><long_desc isprivate="0" >
<commentid>1658117</commentid>
<comment_count>4</comment_count>
<who name="">frank.meies</who>
<bug_when>2008-01-14 09:35:31 +0000</bug_when>
<thetext>Cannot be implemented until code freeze => target 3.x</thetext>
</long_desc>
</bug>
</bugzilla>
One approach I've used is to narrow down which issues you are
interested in, via the UI, maybe filter by component or date range or
status, and from that determine a list of issue numbers. Then you can
retrieve the XML via calls to the REST API. I have a python script
that helps with that part of things, if you are interested.
Regards,
-Rob
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: qa-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: to get bug repositories
Posted by Andrea Pescetti <pe...@apache.org>.
On 03/10/2014 dhyanendra singh wrote:
> i have created an account with username singh.cs.ind@gmail.com
> <ma...@gmail.com> at https://issues.apache.org/ooo/ as you
> suggested.
> now tell me how can get access to the repositories.
What do you need exactly? You already have access to all bugs by
registering (I mean: from the website you can access every bug and make
queries). Do you want to be able to download the full Bugzilla database
as one file? In that case, what information can be anonymized? I'm not
sure this can be done and for sure I can't do it since I don't have the
required permissions, but if the request is clear we can investigate and
see what's possible.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: to get bug repositories
Posted by dhyanendra singh <si...@gmail.com>.
i have created an account with username singh.cs.ind@gmail.com at
https://issues.apache.org/ooo/ as you suggested.
now tell me how can get access to the repositories.
On Fri, Oct 3, 2014 at 12:22 PM, Andrea Pescetti <pe...@apache.org>
wrote:
> dhyanendra singh wrote:
>
>> I am Dhyanandra Singh. I am pursuing M. Tech. from Jaypee Institute
>> of Information Technology. As my thesis Work I have chosen Automatic
>> Duplicate bug Detection and want to use bug repository of Apache open
>> office for that.
>> I am very thankful to you if you will share your bug repository with me.
>>
>
> Welcome! Indeed the OpenOffice Bugzilla is full of duplicate reports, even
> if this has improved a lot with the heuristics that suggests possible
> duplicates when one enters a bug.
>
> What kind of access do you need? I'm not a Bugzilla admin, but this is
> important to know. Bugzilla is at https://issues.apache.org/ooo/ and you
> can register there; you will need to be assigned privileges for advanced
> operations, ask here in case; I'm not sure we can provide a full database
> dump (there are occasional security-relevant bugs that are not publicly
> visible). But say what you need exactly and then the admins can look at it.
>
> Regards,
> Andrea.
>
Re: to get bug repositories
Posted by Andrea Pescetti <pe...@apache.org>.
dhyanendra singh wrote:
> I am Dhyanandra Singh. I am pursuing M. Tech. from Jaypee Institute
> of Information Technology. As my thesis Work I have chosen Automatic
> Duplicate bug Detection and want to use bug repository of Apache open
> office for that.
> I am very thankful to you if you will share your bug repository with me.
Welcome! Indeed the OpenOffice Bugzilla is full of duplicate reports,
even if this has improved a lot with the heuristics that suggests
possible duplicates when one enters a bug.
What kind of access do you need? I'm not a Bugzilla admin, but this is
important to know. Bugzilla is at https://issues.apache.org/ooo/ and you
can register there; you will need to be assigned privileges for advanced
operations, ask here in case; I'm not sure we can provide a full
database dump (there are occasional security-relevant bugs that are not
publicly visible). But say what you need exactly and then the admins can
look at it.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org
Re: to get bug repositories
Posted by Alexandro Colorado <jz...@oooes.org>.
Welcome, please let us know how we can better help you with your project.
Feel free to ask questions and visit our Bugzilla to get a list of
documented bugs.
On Fri, Oct 3, 2014 at 12:59 AM, dhyanendra singh <si...@gmail.com>
wrote:
> Hello,
> I am Dhyanandra Singh. I am pursuing M. Tech. from Jaypee Institute
> of Information Technology. As my thesis Work I have chosen Automatic
> Duplicate bug Detection and want to use bug repository of Apache open
> office for that.
> I am very thankful to you if you will share your bug repository with me.
>
--
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614