why not? apparently it very very simple approach and still documented
Em segunda-feira, 17 de fevereiro de 2014 12h06min58s UTC-3, nardele
salomon escreveu:
>
>
>
> Em segunda-feira, 17 de fevereiro de 2014 12h05min43s UTC-3, nardele
> salomon escreveu:
>>
>> Bug fixes
>>
>> Only the latest r
Em segunda-feira, 17 de fevereiro de 2014 12h05min43s UTC-3, nardele
salomon escreveu:
>
> Bug fixes
>
> 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
Bug fixes
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
On 2014-Feb-14, at 14:15 , nardele salomon wrote:
> Hi,
>
> 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 e
Tks for your help.
Is there any fork which are still supporting the 3.2 ?
[],
Nardele Salomon
Em sexta-feira, 14 de fevereiro de 2014 17h40min58s UTC-2, Carlos Antonio
da Silva escreveu:
>
> In general we only backport issues to 4-0-stable, not to 3-2 anymore.
>
> If it hasn't been backported
On this specific case we will not backport it to a stable release since it
can break people application
Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca
On Fri, Feb 14, 2014 at 5:40 PM, Carlos Antonio da Silva <
carlosantoniodasi...@gmail.com> wrote:
> In g
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).
Hope that clarifies it :)
On Fri, Feb 14, 2014 at 5:15 PM, nardele salomon w
Hi,
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.
