Release notes
2.3.1
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.
2.3.0
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
2.2.4
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.
2.2.3
This release fixes #951, which prevented
updates with large numbers of packages to be viewable in web browsers.
2.2.2
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).
2.2.1
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).
2.2.0
Bodhi 2.2.0 is a security and feature release, with a few bug fixes as well.
Security
This update addresses CVE-2016-1000008 by
disallowing the re-use of solved captchas. Additionally, the captcha is
warped to make it more difficult to
solve through automation. Thanks to Patrick Uiterwijk for discovering and reporting this issue.
Features
- Bodhi’s approve_testing.py script will now comment on updates when they have reached a stable
karma threshold
(5b0d1c7c).
- The web interface now displays a push to stable button when the karma reaches the right level when
autokarma is disabled
(#772 and
#796).
- Masher messages now have an “agent”, so it is possible to tell which user ran the mash
(45e4fc9f).
- Locked updates now list the time they were locked
(#831).
- Bugs are closed and commented on in the same Bugzilla POST
(#404).
- Karma values equal to 0 are no longer displayed with a green background to better distinguish them
from positive karma reports (#799).
- Updates display a link to the feedback guidelines
(#865).
- The new CLI now has a man page
(95574831).
- The CLI now has a --version flag (#895).
Bugs
- Locked updates that aren’t part of a current push will now be pushed and warnings will be logged
(bf4bdeef). This should help us to fix
#838.
- Don’t show users an option to push to stable on obsoleted updates
(#848).
- taskotron updates are shown per build, rather than per update
(ce2394c6,
8e199668).
- The Sphinx documentation now builds again
(b3f80b1b).
- Validator messages are now more useful and helpful
(#630).
- The Bodhi CLI no longer depends on the server code to function
(#900).
- Private bugs will no longer prevent the updates consumer from continuing
(#905).
- bootstrap is now included in the setuptools manifest for the server package
(#919).
Commit log
The above lists are the highlights of what changed. For a full list of the changes since 2.1.8,
please see the
changelog.