Ubuntu Developer Tools

Next steps for ubuntu-dev-tools

Registered by Stefano Rivera on 2011-05-02

What needs to be done for ubuntu-dev-tools. Some tools need to be upstreamed to devscripts. Some elsewhere. What to do about python-based tools & devscripts.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

[stefanor] Move some launchpad stuff into lptools: DONE
[poolie] Move some launchpad stuff into lptools: DONE
[persia] Talk to whoever it was trying to get pbuilder-dist accepted: TODO
[stefanor] Find someone for: Make get-build-deps behave like sbuild / share a common tool (removed in favor of mk-build-deps): DONE
[stefanor] Run merge-changelog via derivatives front desk: TODO
[persia] Sort out mk-sbuild: TODO
[bdrung] Push bash scripts into devscripts: add-patch, edit-patch, what-patch: DONE
[bdrung] Push bash script check-symbols into devscripts: TODO
[stefanor] pull-debian-source: TODO
[stefanor] run pull-*-source by derivatives front desk: TODO
[bdrung] wrap-and-sort + suspicious-source branch in devtools: DONE
[stefanor] Find someone for: reverse-build-depends: TODO
[bdrung] Try distro-info again: DONE
[stefanor] Ask derivatives front desk for distro-info naming help: DONE

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.