Hi Bernd, > I registered a few blueprints in the past, but for my opinion blueprints > in launchpad are very useless. FWIW, Blueprint hasn't seen much work in the last couple of years. It has some great ideas, and many of the basic features are there, but we know it can be improved a lot. Now that Launchpad is free software, it's possible for anyone to jump in and start helping make blueprints rock. > But why do I think so? I gained experience that blueprints doesn't get > an answer, always stay unchanged and nobody reviews them. That's more about the dynamics of the project, than a problem with the application, IMO. I know for sure that there are projects that use blueprints where developers pay close attention and track them. Comments, and better email interface would probably help, of course. > In my opinion it's better to report a bug also for feature requests. Bug > reports get a lot more attention. Nobody would like to have a lot of > open bugs. But open blueprints doesn't matter. I agree. For tracking work on new features the bug tracker is a great tool. That's mostly what we do when managing Malone. Bear in mind though, that blueprints aren't "like bugs but for features". The purpose of blueprints is to help plan features in the software, rather than track the work involved in implementing them. Blueprints track dependencies, for example, and display them in a convenient way. They also capture metadata that is much more suitable for software design than for tracking work, Tom
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)