Provide patches for releases, provide minor releases as often as possible

[janmyszkier]

Issue is pretty important for all the magento project owners because we need to reinvent the wheel for the stores and waste money (which is not how magento should be known for, but it is). Example issue:
magento/magento2#20405

The comment that tackles the main problem is:
magento/magento2#20405 (comment)
and I'm sure he is right here. When the patch is ready we shouldn't leave the stores non-functional when there is known way to fix the issue. Nor should all store owners pay the programmers for reinventing the wheel.

Aim / Request:

• Release bugfixes as patches and have them publicly available as .patch files
• in release changelog, include merged patch numbers
• release minor versions every time a bugfix was found and fixed by patch (yes it means big minor versions like 2.3.1234 are potentially possible)

also what I think is important:
non-security patches should NOT be backward compatible nor prepared for older versions.
They were fixed when 2.3 was develop branch, then the patch should be only for 2.3 and already included in 2.4 as a part of the core.

WHY?
If the Magento store owner decides to keep older Magento version, it's up to him and his wallet to pay for back-porting the patch for his store. It was his decision to NOT update the store.