5.0.7-0
Released in testing channel updates on 29th January 2024
2nd Stable Release Candidate (RC2)
Note, there were a few surprised reporters here on the forum that our TESTING-channel-only release of RC1 (5.0.6-0) rpm failed to update from a number of older releases. This is entirely normal, every rpm we publish is tested before release for it’s fresh install capability (no .initrock so DB wipe). But updates, from any prior install (regardless of channel), are in no way guaranteed/tested/indicated-as-working. But given that; as we enter the last stage of each testing phase (RC* releases) we begin, resources/contributions/time allowing, to make best efforts on updating from the last Stable release only (currently 4.6.1-0). But given the extensive changes we have made, and usually make in each testing run, this often also ensures updates from any prior testing version in the current phase: but only later on in said phase.
Overview
With the above as context, we got our much appreciated high quality feedback from forum engaged testers/developers to further our collective effort. Special thanks to @KarstenV for their patient and productive persistence engaging with our stalwart Open Collective team members of @Flox & @Hooverdan. The result diagnosed some subtle issues (cause not effect 
) around our very first Poetry update combined (happenstance - looking on the bright side) by way of yet-another Django update; with a PostgreSQL format incompatibility.
We have now, in this testing phase alone, updated virtually every dependency we have; some, like our Python and Django versions, as many as 3 times each. This step-by-step approach was taken to maintain a fresh install rpm capability during all these changes. Greatly easing community engagement/feedback on our priorities and progress. And further testing our developing update mechanisms. The testing channel is our way to reach production quality releases, consequently the first stable release rpm is always also published in testing first (at the end): as a result of our existing methods, unchanged for the lifetime of the project.
All 3 functional changes in this release pertain to testing-channel-only rpm update regressions introduced/reported/uncovered in our last testing rpm. Thanks also to @hmete1, @Warbucks, and @phemmy22 for their positive engaging on these and other issues here on the forum. We still have some ‘5.1.X-X Stable release’ Milestone issues to address, and are open to adding smaller ones if well defined.
What’s Changed
- Failure to remove legacy poetry version in 5.0.6-0 rpm #2782 by @phillxnet in #2784
- Establish Postgres database format upgrade #2780 by @phillxnet in #2787
- Failure to re-create venv - pre 5.0.3-0 updating to 5.0.6-0 rpm #2788 by @phillxnet in #2790
- Bump versions to a 5.0.7 base - testing branch #2791 by @phillxnet in #2792
Test away and report rapidly as we work against the forces of kipple.