Greetings, Lucites! Short and sweet indeed, just like (hopefully) our new-and-improved release cycle. We're actually still getting into a good rhythm with the new schedule--it's not quite as short and sweet as we've envisioned. Specifically, we're looking for the sprints to be 2 weeks max, with a ticket list in the range of 10 or so tickets (which will obviously vary based on the complexity of the tickets in a given sprint), with release candidate periods of about 2 weeks. But we're definitely moving the right direction.
Today we’re announcing the next Lucee release candidate–184.108.40.206. As I noted above, we pulled in quite a few additional tickets after the sprint started, in order to keep pushing for more and more stability, which in turn will help us fully get into that shorter/sweeter sprint rhythm. Here’s the list of tickets covered:
Please grab a copy from the downloads site, give it a spin, and let us know any and all feedback.
Thanks for listening.
Thanks @IamSigmund, I’m looking forward to this release. I noticed ticket https://luceeserver.atlassian.net/browse/LDEV-1196 is included in 5.3.6 but there have been no new commits listed in JIRA and no comments to indicate the missing bits were added, or how they were accomplished. Is there a way to get confirmation on how LDEV-1196 has been re-addressed?
Also, for you CommandBox users, ALL Lucee versions are now autopubished to ForgeBox. So you can spin up the new RC in box like so for testing:
server start email@example.com-RC
@isapir is going to add a comment or two to the ticket.
The number of regressions in the last few releases is mounting up, is it possible to list all the know regressions when asking people to go and test a RC?
There is a recurring problem with people trying out RCs, just encountering unresolved regressions which have been already reported during the sprint
Here’s a rough jira list of known regressions
Hi Zac. First, yes, as I noted in Monday’s post, we’re still not in the groove we need to be in with regard to our shorter sprints, and in particular with regard to getting caught up on regressions. That said, your list is not accurate. It’s worth noting that our regression analyses are the most time-consuming part of the limited Lucee development schedule. They often take at least hours, if not days, and in most cases we end up determining with reporters that they are not, in fact, regressions.
Now, with all that said, we will certainly add this list of yours to our next standup meeting agenda. Stay tuned.
@IamSigmund I’m still waiting for the comments and commit details to be added to ticket LDEV-1196. As of right now, JIRA shows no additional work at all has been done, it just appears the ticket was completed. The three commits on that ticket are from April of 2019 and the questions and concerns in the comments have been left unaddressed.
Mail-servers don’t verify in this version as well, as described in here:https://dev.lucee.org/t/email-not-sending-lucee-5-3-5-92/
Will this be fixed before a final release?
New bug filed, the test email should be sent with async=false, otherwise the test email is spooled and the error happens in the background
Have the async part been added? I am still setup to work on this. I can add that.
Thanks for the information.
There’s another regression (in that list) since 220.127.116.11 which causes a 1m hang on shutdown with scheduled tasks. That extra delay sucks in production (and dev, especially with testing snapshots)