@bowlofeggs bowlofeggs released this Sep 17, 2018 · 32 commits to develop since this release

Assets 2

Dependency changes

The composer now requires hawkey.

Server upgrade instructions

This release contains database migrations. To apply them, run::

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

Features

  • It is no longer an error if a developer tries to create an override for a build that already had
    an override. Instead, Bodhi helpfully edits the old override automatically (#2030).
  • The UI displays the date that expired overrides became expired (#2136).
  • Security updates now require severity to be set (#2206).
  • The Waiver UI now gives the user more context (#2270 and #2363).
  • The CLI can be used to edit Release mail templates (#2475).
  • A new clean_old_composes setting allows admins to disable the automatic compose cleanup
    feature that was new in Bodhi 3.9.0 (#2561).
  • The API can filter releases by state (beb69a0).
  • The CLI now has a --debug flag on a couple of commands (1bd7617).
  • The bindings have some debug level logging when retrieving Greenwave status (b55fa45).
  • The UI now makes it clear that only authenticated users can leave karma on updates
    (3b551c3).
  • Bodhi can now manage Flatpaks (1a6c4e8).
  • Bodhi now ships a /usr/bin/bodhi-skopeo-lite, which is intended to be an alternative for use
    with the skopeo.cmd setting. It allows for multi-arch containers and Flatpaks to be managed by
    Bodhi (a0496fc).
  • The composer now uses librepo/hawkey to do much more extensive testing on the produced yum
    repositories to ensure they are valid (7dda554).

Bug fixes

  • More space was added around some buttons so they don't touch on small screens (#1902).
  • The bodhi releases subcommands no longer prompt for password when not necessary
    (#2496).
  • The submit feedback button now appears on low resolution screens (#2509).
  • Articles were fixed in a tooltip on the update page (075f8a9).
  • The CLI can again display missing required tests (cf75ff8).
  • Fix a failure that sometimes occurred when editing multi-build updates (d997ed4).
  • Unknown Koji tags will no longer cause an Exception when creating new updates
    (78dd4aa).

Development improvements

  • Line test coverage has reached 100% (2477fc8).
  • A fake Pungi is used in the Vagrant environment to speed up vagrant up (1b4f5fc).
  • No tests are skipped on Python 3 anymore (44d46e3).

Contributors

The following developers contributed to Bodhi 3.10.0:

  • Anatoli Babenia
  • Clement Verna
  • Mattia Verga
  • Owen W. Taylor
  • Patrick Uiterwijk
  • Pierre-Yves Chibon
  • Ralph Bean
  • Rick Elrod
  • Vismay Golwala
  • Randy Barlow

@bowlofeggs bowlofeggs released this Aug 22, 2018 · 84 commits to develop since this release

Assets 2

Server upgrade instructions

This release contains database migrations. To apply them, run::

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

Deprecation

bodhi-manage-releases is now deprecated. The bodhi CLI now has a releases section
that performs the tasks that bodhi-manage-releases is used for.

Dependency changes

  • Cornice must now be at least version 3.1.0 (#2286).
  • Greenwave is now a required service for Bodhi deployments that wish to continue displaying test
    results in the UI (#2370).

Features

  • Bodhi now comments in the same POST as status changes on Bugzilla comments (#336).
  • The RSS feeds now have titles (#1119).
  • bodhi-clean-old-mashes is automatically run after each successful compose (#1304).
  • The bodhi CLI can now edit releases' pending_signing_tag fields (#1337).
  • White space is stripped when searching for packages or updates (#2046).
  • Severity is displayed in the web UI (#2108).
  • Bugzilla bugs are sorted by number on the update bugs tab (#2222).
  • The web UI now queries Greenwave with each page load to display the test gating status, rather
    than displaying the cached value from Bodhi's database. This allows users to see the current
    status of their update from Greenwave's perspective. This change also causes Bodhi to retrieve the
    test results from Greenwave rather than from ResultsDB, which means the test results tab now shows
    the same test results that influence the gating decision (#2370, #2393, and
    #2425)
  • The waiver API is now documented (#2390).
  • The CLI and bindings can now paginate results when querying updates and overrides (#2405).
  • The bodhi CLI can now manage releases (#2419).
  • Comments have a mouse hoverover for timestamps (60e2cdd).
  • The compose is now skipped if the repo is already staged (9d94edb).
  • Update statuses have a descriptive tooltip in the web UI (40d0422).
  • A new /updates/{id}/get-test-results :doc:../server_api/updates API endpoint was added
    that can retrieve the test results for an update from Greenwave (9631a9b).
  • API users can specify which results they'd like to waive in the waiver API (7d51ee5).
  • Update CI status is now displayed in the CLI (4ab03af).
  • The CLI can now waive test results (833a9c1).

Bug fixes

  • Do not alter Bugzilla tickets that are not related to an approved product (#1043 and
    #2336).
  • Only comments after the most recent karma reset event are considered for critpath karma
    (#1996).
  • The homepage now uses correct link for critical path updates (#2094).
  • Bug and test case karma is now correctly registered (#2130, #2189, and
    #2456).
  • The web UI no longer uses a hardcoded Koji URL, and gets it from the new koji_web_url
    setting instead (#2182).
  • The Bodhi CLI will no longer reset unedited fields to their defaults when editing updates
    (#2208).
  • Return a helpful error when notes are not supplied when creating an update (#2214).
  • Removed a conflicting HTTPForbidden handler (#2258).
  • The RSS view for an update now works when the update has comments with no text (#2314).
  • Composes that fail the sanity check are now thrown out (#2374).
  • The uniqueness constraint on e-mail was dropped since it was not useful and did cause occasional
    problems (#2387).
  • e-mail templates are no longer hardcoded and are now stored on the filesystem (#2396).
  • Failure to act on private Bugzilla tickets is no longer logged at error level (#2431).
  • Block quotes are now correctly styled (fd843a4).
  • The validators will no longer report spurious errors due to previously failed validations
    (5241205).

Development improvements

  • Python 2 line test coverage was raised to 99% (#2409).
  • The development build system now implements the addTag and deleteTag calls (4787a3e).
  • The querystring validator is now used from Cornice (f9900c0).
  • The tests now initialize the BodhiClient with a username so the tests will pass when there is a
    cached username (such as on a Fedora system that has Bodhi credentials) (773232b).
  • A new subclass of webtest.TestApp was created so tests would pass on Python 3
    (847873f).
  • devel/Vagrantfile.example was renamed to Vagrantfile (e985fa3).
  • The tests now pass on systems that don't use UTC (6354367).
  • Python 3 line test coverage was significantly increased, up to 98%.
  • A few warnings have been fixed.

Contributors

The following developers contributed to Bodhi 3.9.0:

  • Clement Verna
  • Eli Young
  • Lumir Balhar
  • Mattia Verga
  • Miro Hrončok
  • Owen W. Taylor
  • Patrick Uiterwijk
  • Pierre-Yves Chibon
  • Ralph Bean
  • Vismay Golwala
  • Randy Barlow

@bowlofeggs bowlofeggs released this Jun 12, 2018 · 156 commits to develop since this release

Assets 2

Bug

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

Contributor

Thanks to Miro Hrončok for fixing these issues.

@bowlofeggs bowlofeggs released this May 25, 2018 · 156 commits to develop since this release

Assets 2

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

@bowlofeggs bowlofeggs released this May 8, 2018 · 209 commits to develop since this release

Assets 2

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

@bowlofeggs bowlofeggs released this Apr 23, 2018 · 209 commits to develop since this release

Assets 2

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

@bowlofeggs bowlofeggs released this Apr 16, 2018 · 209 commits to develop since this release

Assets 2

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

@bowlofeggs bowlofeggs released this Mar 26, 2018 · 333 commits to develop since this release

Assets 2

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.

@bowlofeggs bowlofeggs released this Mar 21, 2018 · 333 commits to develop since this release

Assets 2

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.

@bowlofeggs bowlofeggs released this Mar 8, 2018 · 333 commits to develop since this release

Assets 2

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