<@U070SQMD1> We've been using v1.2.0.0-SNAPSHOT of...
# lucee
d
@zackster We've been using v1.2.0.0-SNAPSHOT of the Image Extension in production, but that's no longer available from downloads.lucee.org and our provisioning scripts are now broken. There was never an official release of the v1.2.x branch. The v1.2 code has been stable and includes the Twelve Monkeys libraries, but v1.0.0.50 does not. How is the state of the 2.0 betas? Are any reliable enough to use in production or should I just downgrade our version?
z
sorry, i think micha removed them, no sure. they are gone from the s3 bucket good news is 2.0.0.21-beta is a really solid, even now supports reading and even writing webp files
we have a shit load of new tests. 1.2 was abandoned for a full rewrite with 2
d
How close do you think you are to an official release of 2?
z
waiting on feedback, but pretty much done n dusted
d
Ok, I'll do some testing today and let you know what I find.
Is there a reason 2.0.0.21 hasn't gone to an RC?
z
not really, just got built
d
Thanks for the info!
z
d
Our unit tests are all passing under 2.0.0.21. Our image test coveraging really assumes the image code in CFML is working as expected, but there are a number of test cases for images that previously caused issues with ACF's image functionality.
z
2.0.0.22 is out, this enables the twelve monkeys jpeg codecs
d
Is there a changelog anywhere?
once micha stops hacking I'll be writing up a release post
d
Running tests on 2.0.0.22 now...
Our unit tests on 2.0.0.22 all passed.
j
good news is 2.0.0.21-beta is a really solid, even now supports reading and even writing webp files
between getting
luceedebug
working (and well-documented) and the lucee crew getting webp working (haven't tried out the writes yet), i have already had a happy holiday 🎄
🎉 1