Add reno for release notes management
Bug #1571946 reported by
Yushiro FURUKAWA
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-fujitsu |
Fix Released
|
High
|
Yushiro FURUKAWA |
Changed in networking-fujitsu: | |
assignee: | nobody → Yushiro FURUKAWA (y-furukawa-2) |
Changed in networking-fujitsu: | |
milestone: | none → 2.0.0 |
importance: | Undecided → High |
Changed in networking-fujitsu: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/307559 /git.openstack. org/cgit/ openstack/ networking- fujitsu/ commit/ ?id=deeebef1960 1c6eded19666c4c 3906f38a25b271
Committed: https:/
Submitter: Jenkins
Branch: master
commit deeebef19601c6e ded19666c4c3906 f38a25b271
Author: Yushiro FURUKAWA <email address hidden>
Date: Tue Apr 12 16:14:36 2016 +0900
Add reno for releasenotes management
This commit adds reno for release management.[1] lists.openstack .org/pipermail/ openstack- dev/2015- November/ 078301. html /review. openstack. org/#/c/ 249973/
This commit also referred [2] for 'sphinx-build' option.
[1] http://
[2] https:/
Change-Id: I2ca98a7d720772 b277df2ef7ffe8d f448780b5a0
Closes-Bug: #1571946