Polishing Interactions with Bazaar
Registered by
John A Meinel
As we get closer to a 1.0 release of Bazaar, we are going to want to work more on the user-visible polish of the project.
We should come up with "user acceptance" level tests, or at least basic use-case scenarios, and review the errors and user feedback that bzr gives.
Some of this could become blackbox tests, this spec is more focused on writing down the use cases (especially error conditions), and making sure that the output bzr gives is actually understandable.
Blueprint information
- Status:
- Complete
- Approver:
- Martin Pool
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Martin Pool
Related branches
Related bugs
Bug #91614: Error messages should not include internal filenames below bzrdir | Confirmed |
Whiteboard
mbp 2007-12: not a meaningful spec
(?)