I contact, asking for his help with a simple question:
I found a mistake in the active record, very impactful for my development.
I created an ‘issue’ on github here https://github.com/rails/rails/issues/13854
The error has been corrected, but only on the master branch, which is the 4.1.0-beta.
The versions 3.2 and 4.0 do not receive corrections from active record?
I am very grateful if you could help me understand this mechanism,
because I hope to contribute much more to the rails project.
Nardele Salomon (from Brazil)
In general we only backport issues to 4-0-stable, not to 3-2 anymore.
If it hasn’t been backported to 4-0 yet, you can ask in the issue for someone to backport it (it seems a simple fix so it’s probably ok to backport).
On this specific case we will not backport it to a stable release since it can break people application
Tks for your help.
Is there any fork which are still supporting the 3.2 ?
Only the latest release series will receive bug fixes. When enough bugs are fixed and its deemed worthy to release a new gem, this is the branch it happens from.
Currently included series: 3.2.z
After the Rails 4 release: 4.0.z <<<<<==========|
(* this release does not updated any time *)
why not? apparently it very very simple approach and still documented