Hello! As you may be aware, Bodhi 2.0 is deployed in production[0] while Bodhi 0.9 is packaged in the Fedora and EPEL repositories[1]. The tl;dr of this post is that we are interested in updating the bodhi package in EPEL 7 to the newer 2.x release series so that the client will work with the production deployment of Bodhi. Unfortunately, the 2.x CLI is not backwards compatible with the 0.9 series. The incompatible upgrades policy[2] suggests that we should instead create a new package called bodhi2, since our reason for upgrading the bodhi package is not security related. I'm happy to go with that policy if the discussion here leads down that path, but I'd like to request an exception in this case since the bodhi 0.9 CLI is not fully compatible with the Bodhi 2 server. What do you think?

On Wed, 2016-07-27 at 17:12 -0400, Neal Gompa wrote: > It makes sense to me to go ahead and upgrade it. I don't know of any > other Bodhi instances out there, and frankly broken software needs to > be removed from the repos as soon as possible. It puzzles me that > this > hasn't been resolved before... Thank you for your feedback Neal! I would like to ask the group to discuss this in the next EPEL weekly meeting, so we can begin to move forward with updating bodhi. According to the incompatible upgrades policy[0], this should be discussed at a weekly EPEL meeting. However, I wasn't able to find out when the EPEL weekly meeting is on the EPEL calendar[1]. When/where is the next EPEL meeting? Thanks for your consideration! [0] https://fedoraproject.org/wiki/EPEL_incompatible_upgrades_policy [1] https://apps.fedoraproject.org/calendar/epel/2016/8/8/ _______________________________________________ epel-devel mailing list epel-devel(a)lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraprojec...