When a specification is implemented..

[Matthew Paul Thomas]

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

On Oct 4, 2006, at 7:26 PM, Lloyd D Budd wrote:
>
> ... I think it would be useful to connect the information, because
> currently "implemented" seems like a bit of a dead end for
> information.
>
> Example:
> https://launchpad.net/distros/ubuntu/+spec/automated-problem-reports
> maybe could provide a link to at least packages affected.
> ...

In the long term, blueprints affecting distribution packages probably 
will be a small minority. Most will be about upstream software 
projects, and even some of those for distributions will be about the 
distribution in general rather than packages in particular. So such a 
field would be relatively unused.

The specification in question
<https://wiki.ubuntu.com/AutomatedProblemReports> already contains a 
"Packages affected:" field, but it's empty. It's not clear to me that 
the field would more likely have been filled in if in Launchpad rather 
than on the wiki page, especially since in Launchpad it probably would 
have involved more page loads.

If you're writing your own specification and want to track 
implementation in multiple packages, one option is to report a Wishlist 
bug instead (initially assigned to yourself), and draft the 
specification by editing the bug report. You can use "Also affects: 
Distribution" to file the bug on multiple packages.

Cheers
- --
Matthew Paul Thomas
http://mpt.net.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFGHcYf6PUxNfU6ecoRAkoGAKCwq49UIRtSZsuZfuof0MGN89DcIACfcUKW
MWEcnTsvsRR4EciVwmMsiZU=
=qM0G
-----END PGP SIGNATURE-----