Automating DE processes

The DE workflow is (roughly) :

1. Developer branches package from P:DE:Trunk
2. Developer submits package to P:DE:Trunk:Testing
3. Boss runs checks on package
4. Boss creates branch of P:DE:Trunk
5. Boss submits package(s) to new branch

1. Boss rejects package
2. Boss notifies maintainers

1. Package is accepted to P:DE:Trunk
2. bz is updated

The DE bug lifecycle is (roughly):

1. Developer starts working on the bug/feature and sets to ASSIGNED
2. Developer submits package to P:DE:Trunk:Testing and documents changelog and/or commit properly (fixes bmc #1234;)
3. Bugzilla records the commit message with link to the repo and timestamp
4. Package is accepted to P:DE:Trunk
5. Bugzilla records acceptance with comment and bug status is automatically changed to FIXED if bug is still in OPEN status (New, assigned, needinfo, reopened, waiting)
6. Release is triggered
7. Bug status is automatically changed to RELEASED, a comment with a link to the image is created and the Target Build value is set to match appropriate release

Note that eventually, both FIXED and RELEASED statuses would require specific credentials to be modified.