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 @Zac_Spitzer
I would like to ask, if someone from the Lucee team would at least want to read the following ticket, and give a reply: https://luceeserver.atlassian.net/browse/LDEV-694
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
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:
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.
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 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.