The 2.0.0 development cycle is coming to an end, and I am confident I’ll be able to deliver this new major version of the software on September 21, as planned: it will be Saint Matthew’s Day (my name day, even though my first name is spelled with only one T!).
This release candidate marks an important step: the one at which I believe the progress made during this cycle is ready to be stabilized in a major release, the second one. Please use this â likely â last pre-release to check your potential customizations (extensions or themes) are ready to welcome 2.0.0 as they should be: with complete stability.
It’s « string freeze » stage, translatable strings will not change until the final 2.0.0 release. Allowing software translators time to update their own language catalogs is a good practice I like to follow. As far as I’m concerned, I’ve already done the job on the French translation.
The 1-click core upgrade feature is ready!
Tests I made during the transition from the first beta to the second one were very reassuring: everything behaved as expected each time. I therefore decided to remove the « opt-in » mechanism that was integrated into previous pre-release versions (a filter hook placed in a strategic location of the source code was playing this role). The one-click upgrade has thus become our preferred way to keep our Retraceur instances up to date and therefore secure.
I’m very proud about the work I accomplished when designing this mechanism because it promises:
- updating core is easier, when performing this process manually, it’s rather tedious and stressful;
- and, as a result, I hope, more contributors will choose this ethics first open source project (unlike the « forked » software from which it originated).
As soon as a Retraceur minor or major version is released & and made available from its GitHub repository, we will be notified about it almost instantly via the dashboard on our personal website. All we have to do is save our sensitive files as explained in the documentation before clicking on the button to start the upgrade process.
PS: I’ll tell you more about the other software improvements in the final 2.0.0 announcement post I’ll write when released.
Ready for one last hunt for anomalies?
The whole point of pre-releases is to ensure that the software updates work as expected and haven’t caused regressions or generated bugs. This is especially important since Retraceur offers configuration, customization, and extension options that you can use in very different ways: I can’t anticipate them all in my tests!
Contributing to this 2.0.0-RC1 tests is an investment in the stability of your installation and contributes to the stability of all other users. If you’ve chosen to trust Retraceur to power your online publishing hub, I encourage you for a hunt with me and report any bugs you encounter. Thanks in advance for your help.
NB: do not test Retraceur on your production website; use a local development site (using MAMP, LAMP, or WAMP, depending on your hardware) or a remote one. If you have forgotten how to install Retraceur since version 1.0.0, please have a look at this documentation resource.
Featured photo credits Troy Olson on Unsplash
Conversation
Rejoignez la conversation depuis Bluesky