On Jun 22, 2011, at 4:02 AM, Olaf van der Spek wrote: > On Wed, Jun 22, 2011 at 4:31 AM, Stewart Smith <[email protected]> > wrote: >>> It's not about tracking, it's about being able to comment / edit >>> issues. You can for bugs, you can't fur blueprints. >> >> you can edit and write on the whiteboard for them. >> >> I think it's a long-standing feature request to have more comments >> attached to them. Blueprints haven't been the most worked-on feature of >> launchpad. > > What's the advantage of blueprints over bugs for us? >
In my opinion there is a different use case for blueprints, and bugs. A blueprint could be an idea, proposal, or anything else for future development or organizational changes. A bug or feature request is a specific code request to add this or change that. I think the ideal situation would be that blueprints are used to outline things we need to do, or want to do, and to 'brain storm' how we want to do that thing. Upon approval, issue trackers can then be 'linked' to the blueprint. I think the blueprint can be seen as a high level view of some sort of implementation/change... where the bug are the lower level specific tasks required to accomplish/complete the blueprint. A blue print could very well have dozens of bugs related to it depending on the scale of the proposal. --- derks _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
