Open Stack

On 6/11/2018 3:23 PM, Jeremy Stanley wrote:
> If you recall the "specs" experiment years
> ago, a few teams tried mildly different solutions for moving from LP
> blueprints with random wiki page links to tracking specifications in
> Git repositories, and over time they learned successful patterns
> from each other and mostly converged on similar solutions. There
> were similar cries back then about "how will users/operators find
> out what is being planned?" but I think the end result was far
> better than what it replaced.

The specs thing was mentioned last week in IRC when talking about 
blueprints in launchpad and I just want to reiterate the specs are more 
about high level designs and reviewing those designs in Gerrit which was 
/ is a major drawback in the 'whiteboard' in launchpad for working on 
blueprints - old blueprints that had a design (if they had a design at 
all) were usually linked from a wiki page.

Anyway, specs are design documents per release. Blueprints in launchpad, 
at least for nova, are the project management tracking tool for that 
release. Not all blueprints require a spec, but all specs require a 
blueprint since specs are generally for API changes or other major 
design changes or features. Just FYI.

-- 

Thanks,

Matt