On 1/30/06, Charles Thornton <ceo / hawthorne-press.com> wrote:
> 2) Now for the "I will probably be stoned answer" -- If anybody employed
>     either full time or consultant UPGRADES Language Release without
>     being aware of any compatility issues between one version and the next
>     I'd fire his butt.
> 3) Nobody is FORCED to Upgrade and break code.  It is a CHOICE beween
>     Adjusting your code or living with your current verion (say 1.8.4).
>     Which by the way works very well.  I only languages I know of that
>     don't break something between major releases are DEAD ONES.

Amen. It's already been determined that 2.0 will be a non-compatible
release. Anyone that upgrades from 1.8.x to 2.0 will have to fix
*something*, and this can be one of those somethings. If you document
the breakage in BIG RED LETTERS, I don't see any problem with
including the optimized version alone in 2.0 (and by extension in 1.9,
which is the development branch for 2.0).

As far as making it available for 1.8.x, just create a shim-patch in
the form of a gem or whatever other form of package you want. Early
adopters who can't run 1.9 for some other reason can apply the patch
and be ahead of the game for the ->2.0 upgrade where they'll only need
to remove the require line for the patch.

Jacob Fugal