Bodhi 3.8.1 released

Bug

• Fix two incompatibilities with Python 3.7 (#2436 and #2438).

Contributor

Thanks to Miro Hrončok for fixing these issues.

Bodhi 3.8.0 released

Features

• Container releases may now have a trailing "C" in their name (#2250).
• The number of days an update has been in its current state is now displayed by the CLI
  (#2176 and #2269).
• Composes are no longer batched by category (security vs. non-security, updates vs. testing)
  as this was not found to be beneficial and did slow the compose process down (68c7936).
• A fedmsg is now transmitted when an update's time in testing is met (99923f1).
• New states for updates that are related to side tags have been documented (d7b5432).

Bugs

• Bodhi no longer considers HTTP codes > 200 and < 300 to be errors (#2361).
• Do not apply null Koji tags to ejected updates during compose (#2368).

Development improvements

• The container composer has been refactored to use a cleaner helper function (#2259).
• Bodhi's models now support side tags, a planned feature for an upcoming Bodhi release
  (#2275).
• Compose.from_updates() returns a list in Python 3 (#2291).
• Some silliness was removed from the universe, as bodhi.server.models.BodhiBase.get() no
  longer requires a database session to be passed to it (#2298).
• The in-memory dogpile cache backend is used for development by default (#2300).
• The CI container no longer installs Pungi, which speeds the CI testing time up (#2306).
• Dropped support for str arguments from util.cmd() (#2332).
• Python 3 line test coverage has increased to 85%.

Server upgrade instructions

This update contains a migration to add two new updates states for side tags. After installing the
new server packages, you need to run the migrations:

    $ sudo -u apache /usr/bin/alembic -c /etc/bodhi/alembic.ini upgrade head

Contributors

The following developers contributed to Bodhi 3.8.0:

• Mattia Verga
• Eli Young
• Lumir Balhar
• Patrick Uiterwijk
• Ralph Bean
• Paul W. Frields
• Randy Barlow

Bodhi 3.7.0 released

Features

• Include the missing tests in the summary about greenwave's decision
  (#2273 and #2345).
• Show waivers about an update on its page for easier access to users and admins
  (#2277).
• New legal_link and privacy_link settings allow Bodhi to link to a legal document and
  privacy policy (#2347).

Bugs

• Properly call the WaiverDB API when waiving tests from the UI (#2272).
• Only ask greenwave about updates in active releases when asking their gating
  status (#2121).
• Updates can no longer be pushed if they fail the gating tests (#2346).

Contributors

The following developers contributed to Bodhi 3.7.0:

• Pierre-Yves Chibon
• Patrick Uiterwijk
• Randy Barlow

Bodhi 3.6.1 released

Bug fixes

• The update template no longer crashes on locked updates (#2288).
• Do not cache calculated libravatar links (#2289).
• Warm the release cache at startup to avoid intermingled queries (#2296).
• Warm the home page cache at startup to avoid slow responses and intermingled queries
  (#2297).
• Interpret the dogpile.cache.expiration_time as an int instead of a str
  (#2299).
• Do not cache the Koji latest composes (#2301).
• Do not require the web server to have Pungi installed since it does not use it (#2303).

Contributors

The following developers contributed patches to Bodhi 3.6.1:

• Patrick Uiterwijk
• Randy Barlow

Bodhi 3.6.0 released

Deprecation

• bodhi-monitor-composes has been deprecated and will be removed in a future release. Please
  use bodhi composes list instead (#2170).

Dependency changes

• Pungi 4.1.20 or higher is now required.
• six is now a required dependency.
• Skopeo is now a required dependency for Bodhi installations that compose containers.

Features

• The UI no longer lists a user's updates from retired releases by default (#752).
• The CLI now supports update severity (#1814).
• There is now a REST API to find out the status of running or failed composes (#2015).
• The CLI now has a composes section which is able to query the server to display the status
  of composes (#2016).
• Bodhi is now able to identify containers in Koji (#2027).
• Bodhi is now able to compose containers (#2028).
• There is now a cache_dir setting that can be used to direct Bodhi where to store a
  shelve while generating metadata (9b08f7b).
• There is now documentation about buildroot overrides (3450073).
• Bodhi will now include RPM changelogs in e-mails (07b27fe).
• Bodhi's update e-mail now instruct dnf users to use the --advisory flag
  (9fd56f9).
• A new wait_for_repo_sig setting will allow Bodhi to work with signed repodata
  (eea4039).

Bugs

• Bodhi will not reopen VERIFIED or CLOSED bugs anymore
  (#1091, #1349, #2168).
• Bugzilla tickets will no longer get too much text inserted into their fixedin field
  (#1430).
• The CLI --close-bugs flag now works correctly (#1818).
• Fix ACL lookup for Module Packages (2251).
• Captcha errors are now correctly noted on cookies instead of the session, which was incompatible
  with Cornice 3 (900e80a).
• The prefer_ssl setting now properly works (9f55c7d).

Development improvements

• Uniqueness on a release's branch column was dropped, since container releases will likely use the
  same branch name as RPM releases (2216).
• Bodhi now learns the Pungi output dir directly from Pungi (dbc337e).
• The composer now uses a semaphore to keep track of how many concurrent composes are running
  (66f995e).
• CI tests are now also run against Fedora 28 (#2215).
• Bodhi is now up to 98% line test coverage, from 95% in the 3.5.0 release.
• It is now possible to run the same tests that CI runs in the Vagrant environment by running
  devel/run_tests.sh.
• The Bodhi CLI now supports Python 3 with 100% test coverage.
• The Bodhi server also now supports Python 3, but only has 78% test coverage with Python 3 as many
  tests need to be converted to pass on Python 3, thus it is not yet recommended to run Bodhi server
  on Python 3 even though it is theoretically possible.

Contributors

The following developer contributed patches to Bodhi 3.6.0:

• Lumir Balhar
• Patrick Uiterwijk
• Mattia Verga
• Clément Verna
• Pierre-Yves Chibon
• Jan Kaluza
• Randy Barlow

Bodhi 3.5.2 released

3.5.2 is an important bug fix release. Users are strongly recommended to use it over 3.5.1, which
introduced the bug.

Bug fix

• Fix loop variable leaking in sorted_updates, which led to packages not being tagged in Koji when
  they are pushed to a repository (#2243).

Contributor

Thanks to Patrick Uiterwijk for submitting the fix for this release.

Bodhi 3.5.1 released

Bug fixes

• Use correct N, V, R splitting for module builds and add stream support (#2226).
• Fixed Release.version_int for modular releases (#2232).

Contributor

Both 3.5.1 fixes were submitted by Patrick Uiterwijk.

Bodhi 3.5.0 released

Feature

• Allow version-specific repomd url overrides (#2199).

Bugs

• The location of the release notes was fixed in the developer docs (#2154).
• Use ":"'s instead of "-"'s as the NSV separator for Modules (#2167).
• bodhi-push no longer authenticates to Koji (#2190).
• Two tag references were fixed in bodhi-untag-branched (59c83fc).
• Ensure there is a Greenwave summary to display before displaying it (c07daf9).

Development improvements

• The composer was refactored to split Pungi-specific code out into a new intermediate base class,
  to prepare the way for a coming container composer. This way the future container composer can
  share code with the RPM and Module composer code, while only using Pungi for the latter two
  (#2152).
• The Vagrant development environment was upgraded to Fedora 27 (#2158).

Contributors

The following developers contributed to Bodhi 3.5.0:

• Patrick Uiterwijk
• Jan Kaluza
• Pierre-Yves Chibon
• Anatoli Babenia
• Randy Barlow

Bodhi 3.4.0 released

Features

• A UI for waiving failed test results has been added to the update page (7f7472b).
• A man page was written for bodhi-untag-branched (2b83aec).
• bodhi-clean-old-mashes now prints directories before deleting them (1cfa8a6).

Bug fixes

• The mouseover text for severity was fixed on the new update form (fe40e38).
• It was made clearer in production.ini that some settings don't have defaults
  (c865af9).

Development improvements

• All of Bodhi's public code now has docblocks that follow PEP-257.

Contributors

The following developers contributed to Bodhi 3.4.0:

• Matt Jia
• Lubomír Sedlář
• Randy Barlow

Bodhi 3.3.0 released

Features

• Test gating status is now polled whenever an update is created or edited (#1514).
• Check the state of updates when they are missing signatures during bodhi-push (#1781).
• There is now a web interface that displays the status of running composes (#2022).
• There is now an API for waiving test results (d52cc1a).
• Update states are now documented (6f4a48a).
• Testing documentation was written (f1f2d01).
• A man page for bodhi-expire-overrides was written (e4402a3).
• A man page for bodhi-manage-releases was written (84d0166).
• Update status and request fields are now indexed for more performant searching
  (768ccb6).
• updateinfo.xml now includes the severity level on security updates (8c9c1bf).
• Only request the global_component field for critpath PDC lookups (46f3588).
• Newer updates are checked first by bodhi-check-policies (c894255).

Bugs

• Ensure that issued_date and updated_date are always present in metadata (#2137).
• A link describing ffmarkdown syntax was fixed (70895e5).

Development improvements

• Some validation code was cleaned up to share code (9f17b6c).
• The database now has a content type enum for containers (#2026).
• Docblocks were written for more code.

Contributors

The following developers contributed to Bodhi 3.3.0:

• Matt Jia
• Jonathan Lebon
• Yadnyawalkya Tale
• Patrick Uiterwijk
• Till Maas
• Ken Dreyer
• Randy Barlow