It was my hope we would push this out as 2.5.1-alpha, as now synced
with 2.4.x branch, and let the eager early adopters help us uncover any
unforeseen issues. Think we have a handle on, and have addressed
the anticipated issues.
So "eager early adopters" are OK with modules *you* wish to push out, even if they aren't quite ready, but NOT OK with modules and features others want, even if they also agree that they 'have a handle on, and have addressed the anticipated issues'
In other words: would anyone else have suggested adding a major feature such as this, with somewhat questionable testing as well as it being the sole reason for said release, you would have complained and dismissed such explanations as 'eager early adopters' as facetious. I am glad that this is no longer the case and you have Seen The Light! As long as we can show an attempt at testing, and convince ourselves we have a "handle on" anything that might pop up, and addressed any anticipated issues, we can continue adding new features as we have been and still come out ahead for all users. Again, this is what I and others have been pushing and promoting for years so I am again glad that you have finally agreed.
It's the inconsistency that is bothersome.