Shipit dependencies on Launchpad should be isolated

Bug #616059 reported by Brad Crittenden
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Brad Crittenden

Bug Description

Shipit is now an external application to Launchpad but it maintains some dependencies that make it difficult for us to reorganize and refactor the code. We need to create a specific module that re-exports the items Shipit uses and then force it to only import from those spots. That allows us to move things around in the future without breaking Shipit.

Related branches

Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: In Progress → Fix Committed
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Revision history for this message
Brad Crittenden (bac) wrote :

The new lp.shipit module has landed in LP and the code to use it was pushed to lp:~launchpad-pqm/shipit/trunk but the revision number was not incremented in utilities/sourcecode.conf. So all of the parts are currently in place but not being used. I'll submit a branch to update the revno as used by Launchpad.

Brad Crittenden (bac)
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Curtis Hovey (sinzui)
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.