V4.5+ Testing Channel Changelog

v4.5.0-0

Released in Testing Channel updates on 9th November 2022.

Our first v4.5 Testing Channel release.

We are, in this release, starting out a little differently than our prior releases. This new approach was covered in our last stable channel announcement here:

this is said aforementioned thread.

Thanks

As per our usual practice, I’d like to thank all those ‘out here’ and behind the scenes that have made this somewhat significant release possible. Most specifically our very own venerable @Flox. A ‘co-maintainer of sorts’ who has been instrumental in guiding and supporting this and all releases for a number of years now. And the author of a number of pivotal fixes and developments.

We are also grateful (and dependant upon) all update channel subscribers. My appologies for dragging my feed on re-establishing the stable subscription shop setup. All in good time and again, thanks to all those who so persistently help to keep us a-float. I’ll get the new shop sorted directly after a number of pressing matters here in development and in my own personal/business emigration elements.

I would like also to again thank all those participating in our forum and GitHub reporting and bug investigation. Unfortunately this first v4.1.0-0 to v4.5.0-0 development run has been a particularly tricky one with regard to community involvement. Due mainly to the massive changes required rendering the testing branch code essentially unusable for months at a time. On reflection, I think we should maybe have simply releases what we had on the planned (regular/frequent) release cadence. But our testing channel releases have maintained such a long history of being basically usable that it felt like going against the grain. But as a result many fewer folks were able to report issues, but on the other hand, how many “it doesn’t start” issues do we actually need? But to be fair we have always introduced the testing releases as experimental and known broken, as they have yet to be proven to work across many setups ‘in-the-field’, thus are considered broken by default. @Flox has begun some significant work on some far more advanced automated end-to-end testing that should improve our confidence prior to each testing release. But alas all things take time, and this particular release has taken far more than it’s fair share. So lets get right to the changelog for 4.5.0-0 (from v4.1.0-0):

Changelog summary:

Please note our new contributor @parth for their email fix on ‘local’ domain configs. My apologies for this fix taking so long to be release. We also have the super helpful @Hooverdan’s fix for the Scrub UI failing on large pools, a nice fix that has also taken a long time to see the light of day.

A gentle request

As as been our way, or mostly intended way, we have always encouraged, and been encouraged by, user feedback. The testing channel is king in this regard, especially given the massive number and far reaching nature of this release. We very much need this release tested to exhaustion. Please report here on the forum, in discrete threads, issue that your find that are not already identified in our GitHub repos. The intention, now we are back to hopefully more frequent releases, is to push things fast and often to the new ‘testing ground’ of the testing branch. We need to, as quickly as possible, get our entire project rid of it’s technical dept. And the changes in this release should help get us started this next journey.

As is, this release looks indistinguishable from v4.1.0-0, but rest assured, there are many changes, mainly in our dependencies, and many more to come, that all add up to our way forward. But we had to start somewhere and that where is here.

As we move and settle our dependencies, we can begin approaching a few more feature additions, especially given our much improved automated unit testing in this release and the QA testing to come.

Test away and report rapidly as we work against the forces of kipple.

Enjoy and report.

4 Likes

v4.5.4-0

Released in Testing Channel updates on 17th January 2023.

Our first Stable Release Candidate built using Poetry.

Again we have a little more difference than the main developers would have liked. One of the remaining key legacy code components, Buildout, our prior build system, scuppered our intended interim releases of 4.5.1-0+ in the last couple of months. The intended-for-release code-state at that time failed the final rpm build due to a zc.sourcerelese (2012!!) dependency within our Buildout build system. We had a slight difference between how we build for development, and how we build for our rpm releases. This difference has now been removed along with all traces of Buildout. The replacement is the new shiny of Poetry. This needed to happen sooner rather than latter anyway. Hats-off to buildout and co for working (mostly) for all these years.

Immidiate roadmap

The above is intended primarily to help define our path to the next Stable release as quickly as possible. We do not have the resources, at least currently, to carry two build systems. And so we must move to have master branch (stable) and testing branch (testing) built by the same modern method.

Thanks

I would again like to thank all those who have practices such rigour and patience as to get us this far - both here on the forum and toiling away in the background. As stated before, we have had less than ideal release cadence as although we develop in the open via GitHub, such changes as have been required of late, has rendered rpm releases either un-buildable or otherwise unworkable. But a return to a more fervent release cadence is now foreseeable. In a major way this is down to user feedback. We do have, down to the efforts of the venerable @Flox, an ongoing effort to improve our automated testing. In this case via yet-another excellent open-source tool, mentioned previously, from our upstream of openSUSE: http://open.qa/. But that news is for another day. But while on the testing topic, if momentarily, we do now, via the %check scriptlet, run all our existing unit tests prior to each and every rpm build. Another improvement brought on by the somewhat forced re-jig of our entire build system. Note also the rocsktor-jslib and licensing clarification improvements referenced below.

Changelog summary:

Noteworthy is not an inconsiderable effort towards our new Leap 15.4 compatibility: I know, but better late than never. Plus some repo enhancements: that should help with further community involvement; again news for another post, post publication as it were.

A gentle request

(repeated for emphasis :slight_smile: )

As as been our way, or mostly intended way, we have always encouraged, and been encouraged by, user feedback. The testing channel is king in this regard, especially given the massive number and far reaching nature of recent changes. We very much need this release tested to its extremities. Please report here on the forum, in discrete threads, issues that you find that are not already identified in our GitHub repos. The intention, now we are back to hopefully more frequent releases, is to push things fast and often to the relatively new ‘testing ground’ of the testing branch. We need to, as quickly as possible, get our entire project rid of it’s technical dept. And the changes in these releases should help get us along the way of this next part of our journey.

Test away and report rapidly as we work against the forces of kipple.

Enjoy and report.

4 Likes

4.5.5-0

Released in Testing Channel updates on 19th January 2023.

Our second Stable Release Candidate build using Poetry.

We had in 4.5.4-0 some trivial but important changed omitted that were related to our recent Poetry build system. This was inevitable and expected give the project wide changes required in switching our build system. We have also in this release bumped our rockstor-jslibs version in accordance with the package version: but no changes were actually included in this library (unlike in 4.5.4-0 where we slimmed it down some). This further field-tests this part of the update and to see if there are any un-forseen issues that may result from who we do that update. In house testing looks to have gone as expected however.

Thanks and a welcome

I would like to welcome in this release a fast fixer known on GitHub, ironically, as slowhand93 (suspected @Mark93 here on the forum); who earlier today fixed an issue opened all of 7 hours ago by myself. That was a surprise! Who many years ago now also contributed to our https://github.com/rockstor/rockon-registry.

And again special thanks to our forum moderator and all around intrepid @Flox who also did much of the diagnostic work for the path issues we faced, and fixed, in this 4.5.4-0 to 4.5.5-0 work.

We were able to find and fix these the below issue down to some excellent feedback here on the forum by @Jorma_Tuomainen, @Mark93, @aremiaskfa, @stitch10925, @agjbond007 along with others’ reports behind the scenes. As always much appreciation to you all. My apologies if I have omitted anyone in these attributions.

Changelog summary:

Test away and report rapidly as we work against the forces of kipple.

Enjoy and report.

4 Likes

4.5.6-0

Released in Testing Channel updates on 25th January 2023.

Our third Stable Release Candidate

I’ll keep this release announcement short as I know there are folks in need of these fixes:

So 4.5.5-0 (RC2) had the disappointing but deep failure on config-upload. Bit of a show-stopper that one; but no matter as it’s fixed now in this next release. Thanks to the rapid and rabid work of our intrepid forum admin @Flox and newly active forum member @aremiaskfa. Thanks to you both for jumping on this one and getting us out of that little corner. This also makes @aremiaskfa our first of two new contributors. See also @stitch10925 who stitched up a hole we had in our local Rock-ons repo where we basically took on all files, without even filtering for .json: oh well; again it’s sorted now !!

Thanks and welcome

We had another good run on the feedback leading up to this latest 4.5.6-0 release. Thanks as always to @Flox, a key member of the core contributors, saving the day (release) yet again. And to our two new contributors @stitch10925, and @aremiaskfa. We also have the ongoing reports of confirmations and code maufunctioning from among others @Mark93.

Changelog summary:

Test away and report rapidly as we work against the forces of kipple.

Enjoy and report.

5 Likes