Add Reno for release notes management

Registered by HouMing Wang

From the announcement of OpenStack release management team[1], the release team is modifying change management tracking tools and processes for stable/liberty and mitaka. A new tool - Reno is introduced to handle release notes as files in-tree, to allow us to simply and continuously build the release notes for stable branch point releases and milestones on the master branch.
We should add Reno in Magnum for better and clear release management.

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html

Blueprint information

Status:
Complete
Approver:
Adrian Otto
Priority:
Low
Drafter:
HouMing Wang
Direction:
Approved
Assignee:
HouMing Wang
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Spyros Trigazis
Completed by
Spyros Trigazis

Related branches

Sprints

Whiteboard

strigazi: we have reno for some time now.

Dos added http://docs.openstack.org/developer/reno/ (eliqiao 2016-02-26)

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-reno-for-release-management,n,z

Addressed by: https://review.openstack.org/298589
    Add reno to Magnum

@Eli, @HouMing, it looks this BP has already been implemented. Could you confirm? -- hongbin 2015-05-01 (Should be 2016-05-02 I think)

@hongbin, yes, feel free to close it. and please advise to team that every significant change requires a reno --Eli 2016-5-2

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.