keepassx 2.0?

[Ed Marshall <esm@xxxxxxxxx>]

Bringing this discussion to the mailing list, since it's all apparently happened in bugzilla until now (and I only found out when I updated this evening).

For reference: https://bugzilla.redhat.com/show_bug.cgi?id=1282825

This update (0.4.3 to 2.0.0) went out today, for both F22 and F23. It removes the ability to edit KeePass 1.x databases, and offers only a one-way import to 2.x databases. This breaks anyone depending on the ability to sync databases between devices mid-release.

How is this possibly the correct thing to do for users in the middle of a release cycle? Could a keepassx2 package not have been pushed out, or barring that, a copr for the updated package for people to try out on their own if they need it today? Shouldn't breaking changes like this wait for release boundaries? (Isn't that why we have relatively short release cycles in the first place?)

--

Ed Marshall <esm@xxxxxxxxx>
Felix qui potuit rerum cognoscere causas.
http://esm.logic.net/

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx