Remove bodhi manage releases #2652
Conversation
sebwoj
force-pushed
the
Remove_bodhi_manage_releases
branch
2 times, most recently
from
1c73e02 to
08e8eea
Compare
bowlofeggs
added
no-mergify
Server CLI
|
As noted in #2420, we don't want to merge this until we are ready to make Bodhi 4.0.0, since it is backwards incompatible. |
| @@ -11,114 +11,12 @@ Synopsis | |||
| Description | |||
| =========== | |||
|
|
|||
| DEPRECATED: This utility has been deprecated. Please use ``bodhi releases`` instead. | |||
| REMOVED: This utility has been removed. Please use ``bodhi releases`` instead. | |||
There was a problem hiding this comment.
For when it's time to merge this PR, we should also delete this file. The more noticeable place to make a note of the files removal is the release notes (see docs/user/release_notes.rst).
There was a problem hiding this comment.
There is a link in releases_notes.rst, so after removal the following info is shown after bdocs:
Warning, treated as error:
/home/vagrant/bodhi/docs/user/release_notes.rst:563:unknown document: man_pages/bodhi-manage-releases
Is it ok to change lines in release_notes.rst in legacy releases?
|
On Tue, 2018-10-09 at 13:29 -0700, Sebastian Wojciechowski wrote:
Is it ok to change lines in release_notes.rst in legacy releases?
Yeah I think that's OK in this case. We can leave the text but just
stop it from being a link.
|
sebwoj
force-pushed
the
Remove_bodhi_manage_releases
branch
2 times, most recently
from
9f39cb8 to
2e3970c
Compare
sebwoj
force-pushed
the
Remove_bodhi_manage_releases
branch
from
2e3970c to
a98c979
Compare
Fixes fedora-infra#2420 Signed-off-by: Sebastian Wojciechowski <[email protected]>
sebwoj
force-pushed
the
Remove_bodhi_manage_releases
branch
from
a98c979 to
360c1b5
Compare
|
This patch is planned for inclusion in the upcoming 4.0.0 release: #3221 |
|
Bodhi 4.0.0 beta is built and deployed to staging: https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi-pre-release |
Fix #2420
Signed-off-by: Sebastian Wojciechowski [email protected]