Hi all. Some folks have asked for a fresh discussion topic to cover the current sprint, which will produce Lucee 5.2.7-RC. We still have some spare cycles for March, so please put any and all sprint-related questions/comments/commentary here. Thanks! cc @Zackster
now that letsencrypt offers wildcard support ACME v2 and Wildcard Certificate Support is Live - Issuance Policy - Let's Encrypt Community Support, can all the updates/downloads start using https?
server and extension updates are insecurely downloaded over http
https://luceeserver.atlassian.net/browse/LDEV-1506
Do you have an estimated timeframe for when 5.2.7 would be released (versus RC)?
Yes, we currently allow 4 weeks between RC and Release in order to identify possible regressions and bugs.
I would like to ask, if someone from the Lucee team would at least want to read the following ticket, and give a reply: [LDEV-694] - Lucee
It has never had a response in over 2 years. The work I have already done on the mod_cfml side, which is an attempt to improve ease of configuration for Lucee users, took quite long, and is getting stale waiting for any response.
Thanks in advance, keep up the good work 
Paul Klinkenberg
Thanks, and the RC drops within a few days of 3/31?
https://lucee.daemonite.io/t/2018-release-schedule/3409
Shameless plug for my ticket that prevents me from being able to use Lucee 5: [LDEV-1712] - Lucee
Hey Jamie. Yes, the RC is generally ready really quickly after the end of the sprint, since there’s less that we have to prepare in the way of announcement/release notes/etc. You can keep an eye on the forum, and/or the downloads site.
Also, the entire 2018 schedule is published, in case you hadn’t seen it:
https://lucee.daemonite.io/t/2018-release-schedule/3409
We stick to that like stink on a pig, as the old saying goes. 
Finally, thanks for the heads-up on ticket 1712. It’s on my radar now. Keep an eye on it for updates.
I’ll take a look now, Paul. Stay tuned!
Thanks, Zac. SSL has been on our agenda for a bit, so this prompt from you is helpful. I’ve added review of the ticket to my to-do list. More soon.
Thanks for adding the labels (L5A, NextSprint), @IamSigmund.
What do they signify? (May sprint? March Sprint?)
Hi, I would see [LDEV-1575] - Lucee also on one of the next sprints with priority. Caching mechanisms in Lucee are for us very important.
Hi Jamie. Both labels are used in our ticket tracking (aging reports, sprint planning, etc. etc.). “L5A” indicates a ticket affecting one’s Lucee 5 adoption, which is our top priority. We really don’t want anyone in the community lingering on 4.5.x, so that’s why we flag any tickets that are directly blocking upgrading to Lucee 5.x. The “NextSprint” label marks a ticket for inclusion in an upcoming sprint, and then we run ongoing reports to make sure a ticket doesn’t linger too long with this label. Holler with other questions/comments!
Hi Alex. I’ve marked that ticket for an upcoming sprint, and also added it to my watch list. Stay tuned!
Installing new version of Extension doesn’t reload plugin
https://luceeserver.atlassian.net/browse/LDEV-1022
@IamSigmund Please add [LDEV-1494] - Lucee to the sprint. It was previously marked as fixed but it created a regression that I fixed and have an open pull request for.
How about some native mqtt support (subscriber /publisher).
a couple of open pull requests i’d like to see in 5.2.7
improve DirectoryWatcher Logging and error handling
https://luceeserver.atlassian.net/browse/LDEV-1768
allow overriding titles in admin extensions
https://luceeserver.atlassian.net/browse/LDEV-1762
cfajaxproxy throw error while try to access the component
https://luceeserver.atlassian.net/browse/LDEV-1494
also this one
Double spaces in filename combined to one in cfdirectory name attribute
https://luceeserver.atlassian.net/browse/LDEV-678
Hi Zac. 1768 and 1762 are new, and thus won’t make it into 5.2.7-RC, but I’ll put them on my watch list. Looks like 1494 is already done (in 5.2.6). 678 is in progress, so we’ll see where that one goes.