On Tue, 3 Aug 2010, Luke Macken wrote:
Hey guys,
I want to perform a production bodhi upgrade.
Risks are fairly minimal. I've written unit tests for the new major
features,
and have been bashing on this code in staging all day today. I also tested
`yum downgrade bodhi-server` in staging, which works fine. There are no
database schema changes.
The current version of bodhi in production slipped out of staging a week
or so ago, so a lot of these changes are already in production. This
newer release fixes a few issues, and now adheres to the
minimum-time-in-testing part of the package update acceptance criteria.
Changes in this release include:
+1, I assume if things go south we can just downgrade right?
-Mike