2.5.0

Bodhi 2.5.0 is a feature and bugfix release.

Features

• #1313 - The web interface now uses the Fedora Bootstrap theme. The layout of the update page has also been revamped to display the information about an update in a clearer manner.
• The bodhi CLI now has a --url flag that can be used to switch which Bodhi server it communicates with. The BODHI_URL environment can also be used to configure this flag.
• The documentation has been reorganized.
• The Python bindings are now documented.
• 6d6de4bc - Bodhi will now announce that karma has been reset to 0 when builds are added or removed from updates.
• d3ccc579 - Bodhi will now announce that autokarma has been disabled when an update received negative karma.
• 57a80f42 - The docs theme is now Alabaster.
• #1322 - The Bodhi documentation now has a description of Bodhi on the landing page.
• #1323 - The REST API is now documented.
• 1087939b - The client Python bindings can now accept a base_url that doesn't end in a slash.

Bugs

• #902 - The position of the Add Comment button is now the bottom right.
• #1187 - An unusuable --request flag has been removed from a CLI command.
• #1296 - The cursor is now a pointer when hovering over Releases button.
• #1305 - The number of days to stable is now correctly calculated on updates.
• d5bec3fa - Fix a query regular expression so that Fedora update ids work.
• #1033 - Karma thresholds can now be set when autopush is disabled.

Development improvements

• The Vagrant development environment automatically configures the BODHI_URL environment variable so that the client talks to the local server instead of production or staging.
• Test coverage is up another percentage to 82%.
• Bodhi is now PEP-8 compliant.
• The development environment now displays all Python warnings once.

Release contributors

The following developers contributed to Bodhi 2.5.0:

• Ryan Lerch
• Trishna Guha
• Jeremy Cline
• Ankit Raj Ojha
• Ariel O. Barria
• Randy Barlow

2.4.0

Bodhi 2.4.0 is a feature and bugfix release.

Features

• #999: The web interface now displays whether an update has autopush enabled.
• #1191: Autopush is now disabled on any update that receives authenticated negative karma.
• #1246: Bodhi now links to Koji builds via TLS instead of plaintext.
• Some usage examples have been added to the bodhi man page.
• Bodhi's server package has a new script called bodhi-clean-old-mashes that can recursively
  delete any folders with names that end in a dash followed by a string that can be interpreted as a
  float, sparing the newest 10 by lexigraphical sorting. This should help release engineers keep the
  Koji mashing folder clean.
• There is now a bodhi.client.bindings module provided by the Bodhi client package. It contains
  Python bindings to Bodhi's REST API.
• The bodhi CLI now prints autokarma and thresholds when displaying updates.
• bodhi-push now has a --version flag.
• There are now man pages for bodhi-push and initialize_bodhi_db.

Bugs

• #902: Users' e-mail addresses will now be updated when they log in to Bodhi.
• #908: The masher now tests for repomd.xml instead of the directory that contains it.
• #1018: Users can now only upvote an update once.
• #1009: Only comment on non-autokarma updates when they meet testing requirements.
• #1048: Autokarma can no longer be set to NULL.
• #1064: Users can now be more fickle than ever about karma.
• #1065: Critical path updates can now be free of past negative karma ghosts.
• #1094: Bodhi now comments on non-autokarma updates after enough time has passed.
• #1107: bodhi-push now does not crash when users abort a push.
• #1113: bodhi-push now does not print updates when resuming a push.
• #1146: Bodhi now says "Log in" and "Log out" instead of "Login" and "Logout".
• #1201: Bodhi now configures the Koji client to retry, which should help make the masher more reliable.
• #1262: Bodhi is now compatible with Pillow-4.0.0.
• #1408195: The bodhi cli no longer prints update JSON when setting the request.
• Bodhi's signed handler now skips builds that were not assigned to a release.
• The comps file is now cloned into an explicit path during mashing.
• The buildsystem is now locked during login.

Development improvements

• A great deal of tests were written for Bodhi. Test coverage is now up to 81% and is enforced by
  the test suite.
• Bodhi's server code is now PEP-8 compliant.
• The docs now contain contribution guidelines.
• The build system will now fail with a useful Exception if used without being set up.
• The Vagrantfile is a good bit fancier, with hostname, dnf caching, unsafe but performant disk I/O,
  and more.
• The docs now include a database schema image.
• Bodhi is now run by systemd in the Vagrant guest.
• The Vagrant environment now has several helpful shell aliases and a helpful MOTD to advertise
  them to developers.
• The development environment now uses Fedora 25 by default.
• The test suite is less chatty, as several unicode warnings have been fixed.

Dependency change

• Bodhi server now depends on click for bodhi-push.

Release contributors

The following contributors submitted patches for Bodhi 2.4.0:

• Trishna Guha
• Patrick Uiterwijk
• Jeremy Cline
• Till Mass
• Josef Sukdol
• Clement Verna
• andreas
• Ankit Raj Ojha
• Randy Barlow

Bodhi 2.3.3 released

Bodhi 2.3.3 converts koji auth to be done with krb5 and fixes one bug:

• #1129 - Use krb5 for koji.
• #1134 - Disable caching koji sessions during mashing process.

Thanks to Patrick Uiterwijk for contributing both of these commits!

Bodhi 2.3.2 released

Bodhi 2.3.2 is a bugfix release that addresses the following issues:

• #1071 - push.py now defaults to the current releases.
• #1072 - Fixed a typo in the masher in sending an ostree compose message.
• #1073 - Fixed a typo in looking up an e-mail template.
• #1079 - The fedmsg name is now passed explicitly.
• #1095 - The man page was corrected to state that builds should be comma separated.
• #1111 - Fixed a race condition between robosignatory and the signed handler.
• e7cb3f13 - Fix querying the updates for resumption in push.py.
• abeca57e - push.py now prompts for the username if not given.

Release contributors

The following contributors authored patches for 2.3.2:

• Patrick Uiterwijk
• Randy Barlow

Bodhi 2.3.1 released

Bodhi 2.3.1 fixes #1067,
such that edited updates now tag new builds into the pending_signing_tag
instead of the pending_testing_tag. This is needed for automatic signing
gating to work.

Bodhi 2.3.0 released

Bodhi 2.3.0 is a feature and bug fix release.

Features

• The package input field is now autofocused when creating new updates
  #876.
• Releases now have a pending_signing_tag
  3fe3e219.
• fedmsg notifications are now sent during ostree compositions
  b972cad0.
• Critical path updates will have autopush disabled if they receive negative karma
  b1f71006.
• The e-mail templates reference dnf for Fedora and yum for Enterprise Linux
  1c1f2ab7.
• Updates are now obsoleted if they reach the unstable threshold while pending
  f033c74c.
• Bodhi now gates Updates based on whether they are signed yet or not
  #1011.

Bugs

• Candidate builds and bugs are no longer duplicated while searching
  #897.
• The Bugzilla connection is only initialized when needed
  950eee2c.
• A sorting issue was fixed on the metrics page so the data is presented correctly
  487acaaf.
• The Copyright date in the footer of the web interface is updated
  1447b6c7.
• Bodhi will comment with the required time instead of the elapsed time on updates
  #1017.
• Bodhi will only comment once to say that non-autopush updates have reached the threshold
  #1009.
• /masher/ is now allowed in addition to /masher for GET requests
  cdb621ba.

Dependencies

Bodhi now depends on fedmsg-atomic-composer >= 2016.3, which addresses a few issues during mashing.

Development improvements

Bodhi 2.3.0 also has a few improvements to the development environment that make it easier to
contribute to Bodhi or improve Bodhi's automated tests:

• Documentation was added to describe how to connect development Bodhi to staging Koji
  7f3b5fa2.
• An unused locked_date_for_update() method was removed
  b87a6395.
• The development.ini.example base_address was changed to localhost so requests would be allowed
  0fd5901d.
• The setup.py file has more complete metadata, making it more suitable for submission to PyPI
  5c201ac2.
• The #bodhi and #fedora-apps channels are now documented in the readme file
  52093069.
• A new test has been added to enforce PEP-8 style and a few modules have been converted to conform
  bbafc9e6.

Release contributors

The following contributors authored patches for 2.3.0:

• Josef Sukdol
• Julio Faracco
• Patrick Uiterwijk
• Randy Barlow
• Richard Fearn
• Trishna Guha

Bodhi 2.2.4 released to fix two more issues

This release fixes two issues:

• #989, where Karma on
  non-autopush updates would reset the request to None.
• #994, allowing Bodhi to
  be built on setuptools-28.

Bodhi 2.2.3 released to fix large updates

This release fixes #951, which prevented updates with large numbers of packages to be viewable in web browsers.

Bodhi 2.2.2 released

This is another in a series of bug fix releases for Bodhi this week. In this release, we've fixed
the following issues:

• Disallow comment text to be set to the NULL value in the database
  #949.
• Fix autopush on updates that predate the 2.2.0 release
  #950.
• Don't wait on mashes when there aren't any
  68de510c.

A bug fix release, primarily focusing on mashing issues

Bodhi 2.2.1 is a bug fix release, primarily focusing on mashing issues:

• Register date locked during mashing #952.
• UTF-8 encode the updateinfo before writing it to disk #955.
• Improved logging during updateinfo generation #956.
• Removed some unused code
  07ff664f.
• Fix some incorrect imports
  9dd5bdbc and
  b1cc12ad.
• Rely on self.skip_mash to detect when it is ok to skip a mash
  ad65362e.