Hi how are things
I found a problem with the ICON as it loses all its CSS styles when putting a link
I also checked if I could fix it with the ICON BOX and if luckily I was able to use it as a temporary solution
Please review ICON as it loses the styles when you choose any option
I was about to also create a topic for this. This one is one year old but still relevant. I believe me and other developers would highly appreciate more stable and tested releases. It’s just annoying you can’t update in anytime without worrying what breaks on you site today…
Would you consider releasing first beta versions and then stable versions of each built? Or any other solution like internal beta testing program with a few hundreds of volunteers? It seems in a small group you can’t ever test enough scenarios to have a stable built – so without beta testing you just throw us an experiment every time instead.
I know you are quite fast in fixing those bugs but how can I as a developer orientate in that when the releases are not marked as beta/stable?
UPDATE:
One of bricks’s fellow stated this solution in FB group which it makes a lot of sense to me:
[Ivan Arnaudov]
I think the conversation should be reframed more generally in the context of versioning and feature release / bugfixes.
In my opinion, x.y versions should be reserved for feature releases, and x.y.z should be about bugfixes, and these should not be mixed.
This way it will be fairly easy to know when to hurry up and update and when to take a more conservative approach (bugfix releases are much less likely to break things).
By mixing feature releases with bugfixes, the developer creates an antagonistic relationship between the two: a user would want to update because of a bugfix, but their website might break as a result of a feature release.
This isn’t something new and groundbreaking, WP itself follows such logic.
Keep bugfix releases separate from feature releases.