On Thu, Dec 19, 2013 at 01:33:58PM -0500, Martin Owens wrote:
On Thu, 2013-12-19 at 16:33 +0000, John Cliff wrote:
It's one of the things that I really dislike with launchpad, on sf bugs and feature requests were the same system, but not the same thing, so you could filter them out. The bastardized system we have on launchpad is frustrating in comparison.
What is it you'd like to see? Email me, maybe there's some way of getting the right workflow with the website's unreleased roadmap page which would be based on launchpad blueprints.
Martin,
I know what he's referring to, and I definitely sympathize. In SourceForge we had an entirely separate queue for bugs that were feature requests. So like having two parallel bug trackers, and we could prioritize features just like bugs. When we converted over to Launchpad both queues were merged into the one bug list, with the features being set to importance Wishlist without the ability to order them by priority.
The Launchpad developers had work under way to change Blueprints to unify them with bugs, which I think would be a better model for what we actually want here, but as blueprints are currently implemented I'm not sure they're a very good match to our needs. When we first switched to launchpad I tried to encourage reporters to write blueprints instead of filing bugs for feature requests, but it seemed to not really catch on well. But maybe it's worth more thought.
Theoretically, if we did want to move the feature request bugs into blueprints, we could make a launchpad API script to copy them over. Think we'd need to consider if it'd pay off well enough to be worth the trouble.
Bryce