Announcing Lucee 5.2.7-RC


#1

Shipping software on Friday the 13th? Isn’t that bad luck? Luck’s got nothing to do with it! The development team works hard to make sure every Lucee release is better than the last, and 5.2.7-RC is no different.

P.S. We actually posted 5.2.7-RC to the downloads site last Friday, April 6. We’re not crazy–shipping software on Friday the 13th is a terrible idea. :wink:

The March 2018 sprint gave us a clear indication of the benefits of the new-and-improved release schedule for 2018.

This latest RC resolved an eye-popping 49 tickets! Here’s the full list:

The “yellow” sprint/release candidate testing period is underway. Please grab a copy of the 5.2.7 RC and let us know any and all feedback as we work towards shipping a final release of 5.2.7 at the end of April/beginning of May. And, we’re now planning for the next “green” sprint in May, which will produce the next release candidate. Send us your ticket comments, upvotes, forum post comments, or whatever other creative means you can think of to get one or more of your tickets into an upcoming Lucee release.

Finally, as mentioned previously, we’re prepping the next beta release of Lucee! Our goal is to give the community a beta of Lucee 5.3 by the end of April. Keep your eye on the forum here for an announcement!

Thanks for listening, and Happy Friday the 13th!

black_cat


#2

Thanks for the post !


#3

Well done team! just did some basic performance testing with the docs build all process

basically, I run the local serve .script, wait for things to settle and then repeatably
refresh the http://127.0.0.1:4040/build_docs/all/ build all page, here are the results

the local build of docs, when run via a web browser writes these logs out to \server\performance.log

/build_docs/all/ 48,562ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 29,936ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 27,620ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 27,596ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 26,837ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 27,749ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 27,646ms, 4 import threads, 4 build threads, 5.2.6.60
/build_docs/all/ 28,619ms, 4 import threads, 4 build threads, 5.2.6.60

/build_docs/all/ 51,853ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 29,109ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 27,602ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 27,672ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 27,797ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 27,446ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 27,740ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 28,602ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT
/build_docs/all/ 28,446ms, 4 import threads, 4 build threads, 5.2.7.61-SNAPSHOT


#4

@IamSigmund Just spun up the RC using CommandBox using this little trick:

start cfengine=http://update.lucee.org/rest/update/provider/forgebox/5.2.7.61-RC

The first thing I noticed was this notice in the admin:

There are some updates available for your installed Extensions.

  • MySQL
  • Microsoft SQL Server (Vendor Microsoft)
  • S3 Resource Extension
  • PDF Extension
  • Form Tags

I know this has been a point of confusion for people. They expect a final release of Lucee to come with the latest and greatest versions of extensions. Are all of those updates above actually beta versions which is why they’re not installed by default? I remember we talked about this at some point and Micha was going to work on finding a better way to make it clear what is a stable update for an extension and what is a beta update. Is that not in place yet or are the extensions just out of date for this release?