Re: A process question for core developers: how are fixes to 1.x.x.x ported to 1.2.x.x

[Larry E. Masters aka PhpNut]

1.2 has not been released.End of discussion-- /*** @author Larry E. Masters* @var string $userName* @param string $realName* @returns string aka PhpNut* @access  public*/ 

--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups "Cake PHP" group.  To post to this group, send email to cake-php@googlegroups.com  To unsubscribe from this group, send email to [EMAIL PROTECTED]  For more options, visit this group at http://groups.google.com/group/cake-php?hl=en  -~--~~~~--~~--~--~---

A process question for core developers: how are fixes to 1.x.x.x ported to 1.2.x.x

[Darian Anthony Patrick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

...since 1.2.x.x. is sort of a moving target.

In the case of a bugs being found and fixed in 1.x.x.x after 1.2.x.x
branched, how are you handling porting those fixes to 1.2.x.x in light
of the fact that the pertinent code may have been refactored or
restructured in 1.2.x.x, with the same issue possibly remaining?

- --
Darian Anthony Patrick <[EMAIL PROTECTED]>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFUpK4KpzEXPWA4IcRAovSAJ4yhMx7fF/soPDJOShwoKXFfXduVgCfX2eM
/XAKo5ng8X0lXP3gEw6NesA=
=CsM0
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
"Cake PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---