launchpad-users team mailing list archive

[Dan MacNeil <dan@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


We're thinking of ditching the blueprints and moving our 17 blueprints
to the bug tracker.

As near as I can tell

Blueprints can do these things that bugs can't.

   1) distignish between Dafter/approver/implementor

   2) create a pretty dependency graph to other
      blueprints

   3) Mark blueprint as related to a bug

   4) (somehow?) be used for project management

Bugs can do these things blueprints can't

  1) be managed/updated via email
  2) be tagged

Bug advantage #1 is huge as far as time savings go.

Blueprint advantages 1-2 aren't important to us. #2 and #3 can be
largely be accomplished by mentioning related bugs numbers/urls in the
narrative.

#4 is something I've not figured out.

For even moderately detailed specifications, Blueprints are not nearly
as easy to use as a text file or word processing document checked into
version.

The lack of email support ---apparently even x-message-rationale means
that blueprints can't even be sorted / filtered.

Launchpad itself has only 9 blueprints and they don't seem to be active.

Ubuntu has hundreds and that group seems to use them. This is a good
random example:

https://blueprints.launchpad.net/ubuntu/+spec/desktop-karmic-bug-workflow

However, I don't see how this couldn't have been done in the bug tracker
 via an email conversation.

The biggest thing holding us back from moving our blueprints to the bug
tracker is that it is nice to hope to have all bugs closed.

Is there anyone on this list using blueprints happily, who would
recommend against us (a small project) ditching blueprints?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpPxUMACgkQLzI3mETyffxsYgCgoQ3B8nNMNUiKT6YEOae5kMNa
2kgAmgOjNkFwvsumomx/Aa6n6zWiHk40
=Rc2Z
-----END PGP SIGNATURE-----