Add SeaMonkey 2.0 and 2.0.1pre to crash-stats.m.c

RESOLVED FIXED

Status

RESOLVED FIXED
9 years ago
4 years ago

People

(Reporter: kairo, Assigned: fox2mike)

Tracking

Details

(Reporter)

Description

9 years ago
SeaMonkey is releasing 2.0 final this month (RC1 has already been built) and the 1.9.1-based builds will be changed to 2.0.1pre, so those versions should be added to crash-stats.m.c for people to search for them.

SQL statements:

insert into productdims(product,version,branch,release)
values('SeaMonkey','2.0','1.9.1','development');
insert into productdims(product,version,branch,release)
values('SeaMonkey','2.0.1pre','1.9.1','development');


I'm not 100% sure of the "release" column, as this is a stable version now, do we need a different value there for "2.0"?
(Assignee)

Comment 1

9 years ago
morgamic, please check sql and ack?
Assignee: server-ops → shyam
(Assignee)

Comment 2

9 years ago
morgamic, poke + D'oh ;)

Comment 3

9 years ago
Here's some examples from Firefox 3 to show how the release column is set:
 109 | Firefox     | 3.0       | 1.9.0  | major
 110 | Firefox     | 3.0.1     | 1.9.0  | major
 111 | Firefox     | 3.0.2     | 1.9.0  | major
 112 | Firefox     | 3.0.2pre  | 1.9.0  | development
 113 | Firefox     | 3.0.3     | 1.9.0  | major
 114 | Firefox     | 3.0a5     | 1.9.0  | milestone
 115 | Firefox     | 3.0a5pre  | 1.9.0  | development
 116 | Firefox     | 3.0a6     | 1.9.0  | milestone

It should be 'major' for SeaMonkey 2.0, judging by these.
(Reporter)

Comment 4

9 years ago
Right, and all the 2.0a* and 2.0b* version should be set to 'milestone', then.
(Reporter)

Updated

9 years ago
Blocks: 522409
(Reporter)

Updated

9 years ago
Blocks: 523167
The SQL is different now - we'll get it updated tomorrow.
(Reporter)

Comment 6

9 years ago
Different yet again? wow...

In any case, will you do the changes for the release field for the alphas/betas as well, or should I file another bug for those?

Oh, and I also wonder if we are missing data for the MTBF reports?
Frank or Lars can you provide the right SQL please?
(Reporter)

Comment 8

9 years ago
Standard8 just told me there's a doc for the SQL up at http://code.google.com/p/socorro/wiki/TrackNewProductVersion - he'll provide the statements.
Ok, this should be the SQL we want:

INSERT INTO productdims (product, version, branch, release) 
   VALUES ('SeaMonkey','2.0','1.9.1','major');

INSERT INTO productdims (product, version, branch, release)
   VALUES ('SeaMonkey','2.0.1pre','1.9.1','development');

INSERT INTO product_visibility (productdims_id,start_date,end_date) 
     SELECT id, '2009-10-10' as start_date, '2009-12-10' as end_date 
     FROM productdims 
     WHERE product = 'SeaMonkey' AND version = '2.0';

INSERT INTO product_visibility (productdims_id,start_date,end_date) 
     SELECT id, '2009-10-15' as start_date, '2009-12-15' as end_date 
     FROM productdims 
     WHERE product = 'SeaMonkey' AND version = '2.0.1pre';
(Assignee)

Comment 10

9 years ago
moragamic, ack?
Looks good.  Looking forward to having the admin panel soon!  :)
(Assignee)

Comment 12

9 years ago
hawsome!

breakpad=# INSERT INTO productdims (product, version, branch, release) 
breakpad-#    VALUES ('SeaMonkey','2.0','1.9.1','major');
INSERT 0 1
breakpad=# 
breakpad=# INSERT INTO productdims (product, version, branch, release)
breakpad-#    VALUES ('SeaMonkey','2.0.1pre','1.9.1','development');
INSERT 0 1
breakpad=# 
breakpad=# INSERT INTO product_visibility (productdims_id,start_date,end_date) 
breakpad-#      SELECT id, '2009-10-10' as start_date, '2009-12-10' as end_date 
breakpad-#      FROM productdims 
breakpad-#      WHERE product = 'SeaMonkey' AND version = '2.0';
INSERT 0 1
breakpad=# 
breakpad=# INSERT INTO product_visibility (productdims_id,start_date,end_date) 
breakpad-#      SELECT id, '2009-10-15' as start_date, '2009-12-15' as end_date 
breakpad-#      FROM productdims 
breakpad-#      WHERE product = 'SeaMonkey' AND version = '2.0.1pre';
INSERT 0 1

Done.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.