MaloneBazaarIntegration

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2005-04-27 07:10:09 →
Size: 717
Editor: intern146
Comment: spec elsewhere
← Revision 2 as of 2005-04-27 07:10:38 → ⇥
Size: 2975
Editor: intern146
Comment: Initial use cases
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Malone-Bazaar integration = = MaloneBazaarIntegration =
Line 7: Line 7:
 * Created: 2005-04-27 by MatthewPaulThomas  * Created: [[Date(2005-04-27T07:10:38Z)]] by StuartBishop
Line 9: Line 9:
 * People: RobertCollinsLead, MartinPoolSecond
 * Contributors:		  * People: NeedsLead, NeedsSecond
 * Contributors: StuartBishop
Line 12: Line 12:
 * Status: BrainDump, UduBof, LaunchpadSpecification, SpecElsewhere  * Status: BrainDump, BreezyGoal, UduBof, DistroSpecification, NewSpec
 * Branch:
 * Malone Bug:
 * Packages:
 * Depends:
 * Dependents:
Line 14: Line 19:
 * UduSessions: none yet  * UduSessions: 1, 4, 8, etc
Line 16: Line 21:
== Summary == == Introduction ==
Line 18: Line 23:
There are various ways in which Malone and Bazaar can be integrated -- including registering branches that fix particular bugs, and automatically resolving tasks when those branches are merged into upstream or distributions. Many BugTasks require code changes. If these code changes are being made in a Bazaar branch, then it should be possible to set the status of the BugTask automatically on commit, attach a diff (or provide a link to the diff) of the relevant changes as an attachment to the bug, and a comment added containing the changelog of the changes.
Line 20: Line 25:
== Spec elsewhere == == Rationale ==
Line 22: Line 27:
https://wiki.launchpad.canonical.com/MaloneBazaarIntegration Developers are lazy, and any steps we can take to ensure that the Malone Bug database is gardened and curernt is good.
This integration will also provide more reasons for developers to use Bazaar and Malone in tandem, rather than alternative revision control or bug tracking systems.

== Scope and Use Cases ==

 - An upstream maintainer wants to fix Bug#66 in upstream product fnord-ng. They create a branch and add metadata to the branch stating in machine readable for 'This is a fix for Bug#66 in upstream product fnord-ng'. They fix the bug in a series of commits. The branch is flagged as finished (ie. sealed). When this branch is mirrored to the SuperMirror, the BugTask status is set to FIXED (the default), the changelog of the branch attached as a comment (in a low noise format) and a diff between base-0 and the tail attached to the bug as an attachment. A reference to the branch on the supermirror is also attached as a comment.

 - A package maintainer fixes a bug in an Ubuntu package using HCT. Meta data is added to the Bazaar branch created stating in machine readable form 'This is a fix for Bug#66 in Ubuntu Hoary sourcepackage fnord-ng'. The fix is made and committed. Metadata is added to the branch stating that the fix is PENDING UPLOAD. The branch is flagged as Done. When this branch is mirrored to the SuperMirror, the BugTask status is set to PENDINGUPLOAD, the changelog of the branch attached as a comment (in a low noise format) and a diff between base-0 and the tail attached to the bug as an attachment. A reference to the branch on the supermirror is also attached as a comment.

== Implementation Plan ==

=== Data Preservation and Migration ===

=== Packages Affected ===

=== User Interface Requirements ===

== Outstanding Issues ==

 - Does this spec need to address just upstream product development, or sourcepackage maintanance as well? HCT may interface with Malone directly instead of using this workflow, which means we will only ever need to change a BugTask's status to FIXED using a commit.

=== UDU BOF Agenda ===

=== UDU Pre-Work ===

MaloneBazaarIntegration

Status

Introduction

Many BugTasks require code changes. If these code changes are being made in a Bazaar branch, then it should be possible to set the status of the BugTask automatically on commit, attach a diff (or provide a link to the diff) of the relevant changes as an attachment to the bug, and a comment added containing the changelog of the changes.

Rationale

Developers are lazy, and any steps we can take to ensure that the Malone Bug database is gardened and curernt is good. This integration will also provide more reasons for developers to use Bazaar and Malone in tandem, rather than alternative revision control or bug tracking systems.

Scope and Use Cases

  • - An upstream maintainer wants to fix Bug#66 in upstream product fnord-ng. They create a branch and add metadata to the branch stating in machine readable for 'This is a fix for Bug#66 in upstream product fnord-ng'. They fix the bug in a series of commits. The branch is flagged as finished (ie. sealed). When this branch is mirrored to the SuperMirror, the BugTask status is set to FIXED (the default), the changelog of the branch attached as a comment (in a low noise format) and a diff between base-0 and the tail attached to the bug as an attachment. A reference to the branch on the supermirror is also attached as a comment.

    - A package maintainer fixes a bug in an Ubuntu package using HCT. Meta data is added to the Bazaar branch created stating in machine readable form 'This is a fix for Bug#66 in Ubuntu Hoary sourcepackage fnord-ng'. The fix is made and committed. Metadata is added to the branch stating that the fix is PENDING UPLOAD. The branch is flagged as Done. When this branch is mirrored to the SuperMirror, the BugTask status is set to PENDINGUPLOAD, the changelog of the branch attached as a comment (in a low noise format) and a diff between base-0 and the tail attached to the bug as an attachment. A reference to the branch on the supermirror is also attached as a comment.

Implementation Plan

Data Preservation and Migration

Packages Affected

User Interface Requirements

Outstanding Issues

  • - Does this spec need to address just upstream product development, or sourcepackage maintanance as well? HCT may interface with Malone directly instead of using this workflow, which means we will only ever need to change a BugTask's status to FIXED using a commit.

UDU BOF Agenda

UDU Pre-Work

UbuntuDownUnder/BOFs/MaloneBazaarIntegration (last edited 2008-08-06 16:23:58 by localhost)