Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 543320 - Migrate PolarSys Bugzilla to Eclipse Bugzilla
Summary: Migrate PolarSys Bugzilla to Eclipse Bugzilla
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Bugzilla (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Denis Roy CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 543322
Blocks: 541051
  Show dependency tree
 
Reported: 2019-01-09 14:46 EST by Wayne Beaton CLA
Modified: 2020-01-23 13:54 EST (History)
4 users (show)

See Also:


Attachments
Links and Shortcuts (30.84 KB, image/png)
2019-12-10 13:47 EST, Denis Roy CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2019-01-09 14:46:10 EST
I believe that this is possible. Webmaster, please correct me if I'm wrong.

The desired result is that we have a "PolarSys" Classification and that all existing products and components are moved in their current form. 

Is there anything that prevents this?

Assuming that this is possible, does such a move preserve relationships between bugs (e.g. blocker references).
Comment 1 Denis Roy CLA 2019-12-04 16:36:49 EST
> The desired result is that we have a "PolarSys" Classification and that all
> existing products and components are moved in their current form. 

Correct.

> Assuming that this is possible, does such a move preserve relationships
> between bugs (e.g. blocker references).

The move is at the SQL level and aligning data is manual. I do note the original polarsys bug number in the Status Whiteboard prior to the migration, and I try to preserve as many relationships I can.
Comment 2 Philippe Dul CLA 2019-12-09 09:50:24 EST
Hi, 

We have seen that many of polarsys issues have been migrated to Eclipse bugzilla, but there is some issues missing.

For instance, the query looking for Polarsys issues with a Whiteboard field retrieve only 875 bugs instead of around 2690.

https://bugs.eclipse.org/bugs/buglist.cgi?classification=Polarsys&f1=status_whiteboard&list_id=19103839&o1=isnotempty&query_format=advanced


Our mapping query is :
https://bugs.polarsys.org/show_bug.cgi?id=2669
=>
https://bugs.eclipse.org/bugs/buglist.cgi?f1=status_whiteboard&o1=equals&query_format=advanced&v1=2669


Did the migration is finished ? succeeded?

Thanks
Regards
Comment 3 Denis Roy CLA 2019-12-09 13:51:41 EST
2467 bugs were migrated. The default search query is limited, try this one:

https://bugs.eclipse.org/bugs/buglist.cgi?classification=Polarsys&f1=status_whiteboard&limit=0&list_id=19104816&o1=isnotempty&order=bug_id&query_format=advanced

There are several bugs that I will have to do in a more manual fashion in the next few hours, as they must be reassigned to Eclipse Foundation > Community, not "Polarsys". Those are mostly Infra bugs and requests.
Comment 4 Philippe Dul CLA 2019-12-09 14:17:26 EST
Thank you !

Regards
Philippe
Comment 5 Denis Roy CLA 2019-12-10 11:37:14 EST
I've migrated the remaining 125 Polarsys "Community" bugs into Eclipse Foundation > Community > Infrastructure:

https://bugs.eclipse.org/bugs/buglist.cgi?classification=Eclipse%20Foundation&component=Infrastructure&list_id=19106564&product=Community&query_format=advanced&status_whiteboard=%5E%5B0-9%5D%2B%24&status_whiteboard_type=regexp


That concludes our migration! Thank you for your support.
Comment 6 Denis Roy CLA 2019-12-10 13:47:05 EST
Created attachment 281193 [details]
Links and Shortcuts

I've added some links and shortcuts to the Polarsys classification, from bugs.polarsys.org, to make finding things easier.
Comment 7 Wayne Beaton CLA 2019-12-13 14:28:52 EST
I've noticed that at least some of the Bugzilla products do not have dummy inboxes set up. Can you add those so that the project teams can set themselves up to share in communication?
Comment 8 Eclipse Webmaster CLA 2020-01-23 13:54:57 EST
I believe we're done here.

-M.