It seemed settled, pending releases. They are published in Releases category.
Release: 2.1.1.0 (Experimental) 2025-07-17 (following a long series of Canary)
This release is an experimental release inteded to be used for testing.
The intention is to adjust any issues uncovered with this version, and eventually get a new stable release.
A somewhat longer answer (which might sound familiar) came out 14 days ago:
This must be 2.0.8.1_beta_2024-05-07. You hit this on 2.1.0.2_beta_2024-11-29:
I’m tempted to blame 2.1 beta changes which were huge, not it turning to “release”.
I’m surprised that there aren’t more reports, and I hope the fix fixes it for your case.
What would be sad would be if this untested fix doesn’t fix it, and there’s more wait.
Can you reproduce the problem on a non-production system, and see if Canary fixes it?
IMO it is now worth asking development if the most-stable (was a beta, now a stable) releases will maintain the ends-at-beta pattern of a long wait for updated most-stable.
2.1.0.4_stable_2025-01-31 did get a follow-on 2.1.0.5_stable_2025-03-04 for reason:
but what if an issue isn’t critical, or seems to affect only one or a few people severely?
Way back in the all-volunteer days, there was a goal of a Beta every 6 months, I think.
That was reduced from about 9, which then stretched way out when the help was thin.
I’m kind of wondering how 2.2 will go initially, but what about ongoing non-hotfix fixes?
There have long been discussions of how to manage source and releases. Any news?
Dev staff are doing features and fixing bugs, but test and release side seems old-style.