Thanks Matthew, this actually is starting to make more sense.
I might add a PR for your consideration in the maintenance policy.
Something brief and clear.
On Tuesday, December 24, 2019 at 9:27:36 PM UTC+3, matthewd wrote:
>
>
> > • As long as you're releasing a new version of software, there is
> • As long as you're releasing a new version of software, there is a risk that
> something somewhere will break. It's hard (if not impossible) to guarantee
> that the software will run as expected after an upgrade, even if the change
> is a single line of code.
> • According to the descriptio
Thank you Prem for the explanation. I do understand it now. However, I'd
kindly like to raise a point.
In the documentation for the "patch" number, it says: "Only bug fixes, no
API changes, no new features. Except as necessary for security fixes."
I'm being extremely technical and specific, so be
Hello Abdullah,
The reason that Rails Core Team did 6.0.2.1 and not 6.0.3 because 6.0.2.1
is pretty much a forked branch out of 6.0.2 with a security patch applied
on top of it.
In the past, the patched version came off a stable branch (such as
6-0-stable) and contain other changes that had unint
