dineshbhor c6c09dbe3c Add Rocky specs repo

This patch adds rocky specs repo.

In addition to that it also fixes below issues:
1. Adds a single template.rst for all branches in
   doc/source/specs repo.
2. Fixes incorrect references in history section.
3. Creates missing symbolic links to specs templates.
4. Moves implemented specs from 'approved' to 'implemented'
   directory.
   In future we should have a tox script similar to [1] for
   moving implemented specs from approved to implemented directory.

[1] dad9782fc1/tox.ini (L32)

Change-Id: I4499facd28b1cc48d425a8fe15930ebaa4ac24d9

2018-04-17 18:33:34 -07:00

2.5 KiB

Raw Blame History

This work is licensed under a Creative Commons Attribution 3.0 Unported License. http://creativecommons.org/licenses/by/3.0/legalcode

The title of your blueprint

Include the URL of your launchpad blueprint:

https://blueprints.launchpad.net/masakari/+spec/example

Introduction paragraph -- why are we doing anything?

Problem description

A detailed description of the problem.

Proposed change

Here is where you cover the change you propose to make in detail. How do you propose to solve this problem?

If this is one part of a larger effort make it clear where this piece ends. In other words, what's the scope of this effort?

Include where in the masakari tree hierarchy this will reside.

Alternatives

This is an optional section, where it does apply we'd just like a demonstration that some thought has been put into why the proposed approach is the best one.

Implementation

Assignee(s)

Who is leading the writing of the code? Or is this a blueprint where you're throwing it out there to see who picks it up?

If more than one person is working on the implementation, please designate the primary author and contact.

Primary assignee:: <launchpad-id or None>

Can optionally can list additional ids if they intend on doing substantial implementation work on this blueprint.

Milestones

Target Milestone for completion:: Juno-1

Work Items

Work items or tasks -- break the feature up into the things that need to be done to implement it. Those parts might end up being done by different people, but we're mostly trying to understand the timeline for implementation.

Dependencies

Include specific references to specs and/or blueprints in masakari, or in other projects, that this one either depends on or is related to.
Does this feature require any new library dependencies or code otherwise not included in OpenStack? Or does it depend on a specific version of library?

2.5 KiB Raw Blame History