Refining the blueprint page and associated content

Registered by Joey Stanford on 2011-04-26

A discussion about refining the blueprints and cycle documentation to resolve confusion surrounding the various types of blueprints and their uses.

Blueprint information

Status:
Complete
Approver:
Joey Stanford
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Joey Stanford
Definition:
Approved
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Started by
Joey Stanford
Completed by
Joey Stanford

Related branches

Sprints

Whiteboard

[james_w 2011-05-25] ACTION (for Mounir!): contact james_w about improving LP searching of blueprints <- is done. We can ask the Launchpad team to do it at a later date if we are still interested. Mounir has proposed that the Infrastructure team work on it instead.
[james_w 2011-05-25] ACTION: ask Salgado about summit tool naming conventions - ie can we use linaro-<team>-1111-* rather than doing linaro-<team>-o-*. This way we can use engineering BP's in a non-Ubuntu friendly way. <- As it stands, this is perfectly doable. linaro-<team> is not how the summit system sees the names. It sees them as <track>-<something> and only cares about the track part. Therefore something on the linaro-kernel track should be named linaro-kernel-<whatever>. Ubuntu just uses "-o-" to distinguish the series in listings of blueprints, and to make it easier to search as you can only search by name. I suggest that we continue this, but <track>-1111-* works just as well as <track>-o-* for that, provided we are consistent.

(?)

Work Items