Since the gerrit commentlinks are simple regexes with no context of project, we have to link to blueprints by searching for them. We currently limit that search to openstack projects so we are not searching all of LP.
Some ways we could solve this:
1) Add any project in Gerrit to an umbrella project in Launchpad (eg, the openstack project).
Is that desirable? If not, is a second umbrella project an option?
2) Add a commentlink regex that includes the project name. So that "Implements blueprint myproject/myblueprint" would link to myproject/+spec/myblueprint.
This could cause confusion for projects if they migrate from stackforge/ to openstack/, and may also confuse people working on multiple projects. We might mitigate that by _only_ using the expanded syntax (perhaps after a transition period).
Since the gerrit commentlinks are simple regexes with no context of project, we have to link to blueprints by searching for them. We currently limit that search to openstack projects so we are not searching all of LP.
Some ways we could solve this:
1) Add any project in Gerrit to an umbrella project in Launchpad (eg, the openstack project).
Is that desirable? If not, is a second umbrella project an option?
2) Add a commentlink regex that includes the project name. So that "Implements blueprint myproject/ myblueprint" would link to myproject/ +spec/mybluepri nt.
This could cause confusion for projects if they migrate from stackforge/ to openstack/, and may also confuse people working on multiple projects. We might mitigate that by _only_ using the expanded syntax (perhaps after a transition period).