The Mozzila products / components info problem

 
Picture of Brito e Abreu Fernando
The Mozzila products / components info problem
by Brito e Abreu Fernando - mercredi, 19 décembre 2007, 10:41
 
This forum is to be used to provide feedback on the problem of obtaining / extracting information on the Mozilla's products and/or components, to enrich the Bugbase database.
 
Picture of LACOUTURE Mayleen
Re: The Mozzila products / components info problem
by LACOUTURE Mayleen - mercredi, 19 décembre 2007, 10:51
 
Download bugs takes to much time, also space.
It's no easy to store bugs information into the database because transformations are not that simple.
Picture of MALDONADO MOREIRA Walther Fernando
Re: The Mozzila products / components info problem
by MALDONADO MOREIRA Walther Fernando - Wednesday, 19 December 2007, 4:49 PM
 
I wonder if we can even finish getting these bugs on time. It seems we killed bugzilla some hours ago, all connections to the site time out.

The biggest concern is that even though the deadline is Dec 25, in practice it really is Dec 21, 12:00, since after most of us are gone on vacation, we will be unable to access this site (campusneo.mines-nantes.fr/campus) from outside of the campus from what I've discussed with my classmates, so even if we take our laptops with us and it somehow finishes downloading before Christmas, we will most likely be unable to upload the file from off-campus.
Picture of Brito e Abreu Fernando
Re: The Mozzila products / components info problem
by Brito e Abreu Fernando - Wednesday, 19 December 2007, 9:18 PM
 

OK, I am sensible to your concerns. I have extended that period until the end of the year.

FBA

Picture of LACOUTURE Mayleen
Re: The Mozzila products / components info problem
by LACOUTURE Mayleen - Thursday, 20 December 2007, 10:44 AM
 
Ok, that doesn't make much difference. We wont be here by then.
Picture of URIBE L
Re: The Mozzila products / components info problem
by URIBE L - Thursday, 20 December 2007, 7:40 AM
 
I think that the bugs database should include some information related to the geographical place from where the bugs are registered. This information could us let make hypothesis about, for instance, the more active mozilla communities around the word, or the places where a product is more used. 
Picture of CHARLOT J
Transformation Process
by CHARLOT J - Thursday, 20 December 2007, 9:16 AM
 
Notes :
---------
We have to insert some data in the Database (Classification Table)
TRUNCATE Classification CASCADE;
INSERT INTO Classification (classification_id, name) VALUES (1, 'Unclassified');
INSERT INTO Classification (classification_id, name) VALUES (2, 'Client Software');
INSERT INTO Classification (classification_id, name) VALUES (3, 'Components');
INSERT INTO Classification (classification_id, name) VALUES (4, 'Server Software');
INSERT INTO Classification (classification_id, name) VALUES (5, 'Client Supports');

Some bugs don't have priority (they use "--" bug 1104) So you have to update the Priority Domain to
CREATE DOMAIN Priority
      as text
      check (value in ('--', 'P1', 'P2', 'P3', 'P4', 'P5'));


Some bug reference duplicate bug that doesn't exist yet (Bug 81 and 82)

TODO
------
long_desc are not yet parsed (Table bugdetails)
attachment are not yet parsed (Table attachment)
flag
keyword

Works
--------
Bugs
Person
Classification
Status
Resolution
Priority
BugSeverity