PR#704: Update the "How to release Copr" document - copr/copr

copr / copr

#704 Update the "How to release Copr" document

Closed 4 years ago by praiskup. Opened 4 years ago by frostyx.

copr/ frostyx/copr update-how-to-release-copr-2 into master

[doc] use version without release number for PyPI

Jakub Kadlčík • 4 years ago

99c0009

[doc] add a link to MODIFIED bugzillas

Jakub Kadlčík • 4 years ago

371ee60

[doc] use alembic-3 command instead of alembic

Jakub Kadlčík • 4 years ago

bf4c9a1

doc/how_to_release_copr.rst

file modified

+4 -3

		`@@ -44,7 +44,7 @@`

		`sudo su - copr-fe`

		`- alembic upgrade head`
		`+ alembic-3 upgrade head`

		`Note: If there is a new version of copr-rpmbuild, run this on backend::`

		`@@ -57,7 +57,8 @@`
		`Call for QA`
		`-----------`

		`- Move MODIFIED+ bugzillas to ON_QA.`
		+ Move `MODIFIED+ <https://bugzilla.redhat.com/buglist.cgi?bug_status=POST&bug_status=MODIFIED&product=Copr>`_
		`+ bugzillas to ON_QA.`

		`Ask people to test, verify bugs, and generally help with QA. They will ignore it but you will feel good about giving them a chance.`

		`@@ -76,7 +77,7 @@`
		`version=<current_pkg_version> python3 setup.py sdist`
		`twine upload dist/<NAME-VERSION>.tar.gz`

		- Substitute `<current_pkg_version>` with the current package version.
		+ Substitute `<current_pkg_version>` with the current package version (without release).

		`If you cannot run that, tell somebody with access to run that (msuchy has access).`

frostyx commented 4 years ago

Just an ordinary post-release update of "How to release Copr" document.

praiskup commented on line 15 of doc/how_to_release_copr.rst 4 years ago

can we use this? https://bugzilla.redhat.com/buglist.cgi?bug_status=POST&bug_status=MODIFIED&product=Copr

praiskup commented on line 31 of doc/how_to_release_copr.rst 4 years ago

I'm not sure this deserves attention and it slightly sounds like a configuration issue.
f28 is soon to die, and documenting legacy ... up to you.

praiskup commented on line 18 of doc/how_to_release_copr.rst 4 years ago

What about - while we are on it - instruct maintainers to move the bugs to CLOSED CURRENTRELEASE directly?

frostyx commented on line 18 of doc/how_to_release_copr.rst 4 years ago

We can't close the bugs yet. In this phase, only dev instance is updated and the production instance is still untouched. We could possibly skip this step and just close the bugs in "Post release" section but I think, that it is a good idea to give people a chance to test our fixes on devel instance. I think, that we should have a nice template, saying that the fix is deployed to the devel instance, that could be copy-pasted to the BZs.

3 new commits added