PR#421: 1.40 Release - fedpkg

fedpkg

#421 1.40 Release

Merged 3 years ago by onosek. Opened 3 years ago by onosek.

onosek/fedpkg 1.40_release into master

1.40 Release

Ondrej Nosek • 3 years ago

c151b55

doc/source/conf.py

file modified

+2 -2

		`@@ -24,9 +24,9 @@`
		`author = 'fedpkg Team'`

		`# The short X.Y version`
		`- version = '1.39'`
		`+ version = '1.40'`
		`# The full version, including alpha/beta/rc tags`
		`- release = '1.39'`
		`+ release = '1.40'`


		`# -- General configuration ---------------------------------------------------`

doc/source/releases.rst

file modified

		`@@ -6,6 +6,7 @@`
		`.. toctree::`
		`:maxdepth: 1`

		`+ releases/1.40`
		`releases/1.39`
		`releases/1.38`
		`releases/1.37`

doc/source/releases/1.34.rst

file modified

+5 -5

		`@@ -22,7 +22,7 @@`
		`HTTPS. That means you don't have to request SSH permission to contribute to`
		`a package.`

		- Command ``override`` to operate Bodhi update
		+ Command `override` to operate Bodhi update
		`~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		`This new command has two subcommands to create and extend expiration`
		`@@ -57,8 +57,8 @@`

		fedpkg works with ``bodhi-client >= 2.0`` only.

		- Pass repository name to ``request-repo`` explicitly
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ Pass repository name to `request-repo` explicitly
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		`Previously the new repository name, aka the package, module, or container name,`
		to be requested is specified by a global option ``--module-name`` (which is
		`@@ -82,8 +82,8 @@`
		Original form ``fedpkg --module-name foo request-repo`` is not supported.
		`Please switch to the new command form.`

		- Optional repository name and namespace to ``request-branch``
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ Optional repository name and namespace to `request-branch`
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		Command ``request-branch`` now has its own option ``--repo`` and
		``--namespace`` to make it easy to use and avoid any potential confusion.

doc/source/releases/1.35.rst

file modified

+4 -4

		`@@ -35,8 +35,8 @@`

		Refer to ``fedpkg build -h`` for more details.

		- New command ``releases-info``
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ New command `releases-info`
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		``releases-info`` is helpful for packagers to know current active
		`Fedora or EPEL rleases, or both. For example to show active Fedora`
		`@@ -79,8 +79,8 @@`
		`process by two ways, one is to commented out all lines, and another`
		`one is just remove all lines.`

		- Do not delete ``bodhi.template`` if fail to create update
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ Do not delete `bodhi.template` if fail to create update
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		`There could be some reasons that causes update creation fails. Once it`
		happens, ``bodhi.template.last`` is saved and includes what you

doc/source/releases/1.36.rst

file modified

+4 -4

		`@@ -15,8 +15,8 @@`
		`What's new in fedpkg 1.36`
		`-------------------------`

		- Add support for a ``flatpaks`` namespace
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ Add support for a `flatpaks` namespace
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		`flatpaks will be added as a separate namespace in Fedora distgit:`
		see more info at `fedora devel mailing list`_.
		`@@ -25,8 +25,8 @@`
		`- No bugzilla bug is required for repository creation`
		`- Branch names must be valid module stream names`

		- Make ``fedpkg update`` work for containers
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ Make `fedpkg update` work for containers
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		`We don't really have an NVR available, but users can fill it in by themselves.`
		Also add ``severity=`` option to ``fedpkg update`` template. This is now

doc/source/releases/1.37.rst

file modified

+2 -2

		`@@ -38,8 +38,8 @@`
		When Pagure token is expired, hint is added in commands ``fedpkg request-repo``
		and ``fedpkg request-branch`` to keep user informed how to renew the token.

		`- Include possible distprefix in "--define dist" for Forge-based packages`
		`- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		`+ Include possible distprefix in "\\-\\-define dist" for Forge-based packages`
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

		`In forge based packages, and most notably all Golang packages, dist tag are`
		`computed by a lua script in order to generate a snapshot date and shortcommit.`

doc/source/releases/1.39.rst

file modified

+2 -2

		`@@ -45,8 +45,8 @@`

		When ``fedpkg`` communicates with a web API (Pagure or DistGit), prints (json) response data for debugging. The response is shown when there is verbose mode enabled.

		- ``fedpkg fork`` updates
		`- ~~~~~~~~~~~~~~~~~~~~~~~`
		+ `fedpkg fork` updates
		`+ ~~~~~~~~~~~~~~~~~~~~~`

		`* checks if the fork already exists`

doc/source/releases/1.40.rst

file added

+49

		`@@ -0,0 +1,49 @@`
		`+ .. _release_1.40:`
		`+`
		`+ fedpkg 1.40 Release Notes`
		`+ =========================`
		`+`
		`+ Released on December 2, 2020`
		`+`
		+ This release requires ``rpkg >= 1.61-1``.
		`+`
		`+ Python compatibility`
		`+ --------------------`
		`+`
		`+ fedpkg works with Python 2.7, 3.7, 3.8 and 3.9`
		`+`
		`+ What's new in fedpkg 1.40`
		`+ -------------------------`
		`+`
		+ Add support for using `\\-\\-release eln`
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		`+`
		+ 'rpmdefines' configuration values needed for building this release are loaded from Koji. They are located in 'Extra options' section of the 'eln' build target record. Macros for building are named ``rpm.macro.*``.
		`+`
		+ Revert "Support for `epel*-playground` branch requests"
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		`+`
		+ Per recent changes discussed in the EPEL SC meetings, ``epel-playground`` branches should no longer be created automatically when a corresponding ``epel`` branch is requested.
		`+`
		+ Reverting this commit makes ``epel`` branches behave like normal branches and no longer disallow ``epel-playground`` branches from being manually requested if needed.
		`+`
		`+ Do not show warning when 'package.cfg' is missing`
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		+ EPEL sig decided that 'playground' branch won't be required for epel8. In ``package.cfg`` there was a list of target branches. Now it is not necessary to have this configuration file in the repository. Warning about missing this configuration is removed. Config file (if present) still works as previously.
		`+`
		`+ Limit version of 'python-bugzilla' for Python2 tests`
		`+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
		`+`
		`+ There is no more Python 2 support in new python-bugzilla packages. Therefore this dependent package's version has to be limited.`
		`+`
		`+ Change Logs`
		`+ -----------`
		`+ - Tests for "--release eln" (onosek)`
		`+ - Add support for using "--release eln" (mmathesi)`
		`+ - Fix Python 2 tests for epel7 (onosek)`
		+ - Do not show warning when 'package.cfg' is missing - `#417`_ (onosek)
		+ - Fix tests - `#414`_ (michel)
		+ - Revert "Support for epel*-playground branch requests" - `#414`_ (michel)
		`+`
		+ .. _`#414`: https://pagure.io/fedpkg/issue/414
		+ .. _`#417`: https://pagure.io/fedpkg/issue/417

setup.py

file modified

+1 -1

		`@@ -40,7 +40,7 @@`

		`setup(`
		`name="fedpkg",`
		`- version="1.39",`
		`+ version="1.40",`
		`author="Dennis Gilmore",`
		`author_email="dgilmore@fedoraproject.org",`
		`description=("Fedora plugin to rpkg to manage "`