Bug 380489

Description Wayne Beaton 2012-05-23 21:22:47 EDT

With our current system, when a project moves, we create a new project record and retire the old one. Committer records have to be recreated and manually modified to correctly set the active date. Previously retired committers are not moved at all.

This leads to inconsistencies in IP logs (for example), as commits from retired committers may be incorrectly recorded as contributions.

With the new PMI, we're changing the way that this is done. Project moves can be implemented by simply changing the parent project and project id in the project record. All information connected to the project (releases, members, etc.) are connected to the record by node id, not name, and so will "move" automatically. Revision tracking will keep track of the history/change.

This bug exists primarily to capture the design change/decision and invite comment.

The one thing that we need to consider is to make sure that all historical information for projects that have moved is captured and brought forward. There are some hacks in the current system to copy things like release records for some moved projects, but we'll need to review the information being captured and make sure that it's complete.