Launchpad itself

Oops-tools branch should be managed through pqm

Bug #174439 reported by Diogo Matsubara
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Diogo Matsubara

Bug Description

The oops-tools branch should be managed by pqm, similar to how we manage cscvs inside the rocketfuel tree.
Currently that branch has no tests and there's no code review for it.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Spec https://blueprints.edge.launchpad.net/launchpad/+spec/oops-tools-improvements-tests needs to be implemented before this bug is fixed.

Diogo Matsubara (matsubara)
Changed in launchpad:
importance: Undecided → Medium
milestone: none → 1.2.5
status: New → Confirmed
Diogo Matsubara (matsubara)
Changed in launchpad:
status: Confirmed → In Progress
assignee: nobody → matsubara
Revision history for this message
Diogo Matsubara (matsubara) wrote :

This is now fixed. the oops-tools branch is now managed by pqm. <bzr+ssh://devpad.canonical.com/code/rocketfuel/oops-tools/devel> and I've setup a cronjob to update the working tree every 15 mins on devpad, which makes the changes rollout automatically. Thanks to Tom Haddon for setting up everything on the pqm side.

Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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