Hi Lucites! I hope everyone is having a great summer. As we’re now into the second half of 2019, I wanted to send along a quick status update to the community.
The July sprint is underway, and we’ll be wrapping that up the week of August 5, and that will produce an RC for Lucee 5.3.4. According to the 2019 development schedule, we’ve got 2 more sprints left this year, followed by 2 more RC/planning periods. However, for a few different reasons, we may tweak that a bit.
First and foremost, 2019 has seen the most torrid development pace for us in several years, since I took the post as Product Manager. Probably the best example was the 5.3 release that went through so many different builds it ended up with a 3-digit build number, a first for Lucee. While we’re proud of having shipped that much code this year, quality is absolutely more important to us than quantity. And, as we’ve been discussing with some especially active community members, and also amongst some of the member organizations (who tend to have some of the larger and most complex Lucee installations), we’re seeing some slippage when it comes to our quality control. Specifically, we’re seeing a slight increase in regressions, and also in a few cases of missed coverage on the part of our testing efforts. While these are still a tiny percentage of the overall production of our small but mighty development team, we are nonetheless going to be taking a closer look at this in the coming weeks and months.
There’s actually a bit of good news in this. It’s a sign of the increasing adoption of Lucee, and along with this an increase in the size and complexity of applications being built with it. Demands are at an all-time high for prioritization of Lucee development across a widening range of use cases. And this is coming not just from the community at large, but we’re also seeing an increase in requests for sponsored (paid) development, on the part of both member and non-member organizations.
We’re grappling with ORM, Oracle, and everything in between!
In agile-speak, our velocity is too high. That’s right–we’re speeding. So we’re going to tap the brakes in August. If necessary, we’ll re-arrange the remaining development schedule to make sure our quality control stays high. Nothing is more important for Lucee. Beyond the monthly sprints, we also have Lucee 6 to attend to, so that too will be a factor in how we schedule the rest of the year.
In discussing this with some members of the community, there were some questions about the organizational side of Lucee, and we discovered there was some confusion about makeup of the Lucee team, so in case anyone else is wondering, I wanted to share some clarifying info.
Lucee remains a predominantly volunteer effort. Finance, marketing, business development (sales), product management (ahem), testing, tech support–these and related functions are 100% volunteer efforts. The primary expense for Lucee is the paid development team, but even this isn’t fully funded just yet, and much of Lucee core development is also a volunteer contribution.
Considering this, we are definitely “punching above our weight,” to borrow a phrase from boxing. It’s also important to remember if you see us take a punch or two, and maybe wobble a bit. If you’ve seen a regression sneak in, or a deployed fix miss your use case, not to worry–we’re aware, and we’ll make sure we correct.
Continuing the boxing analogy, my job as the PM (and also in my dual role as a board member, along with the rest of the board and member organizations) is to make sure we punch hard, and punch often. But we also need to make sure we’re “beefing up” Team Lucee, so that we can take on bigger and better challenges. That’s the focus as we head into the second half of 2019.
Finally, on a personal note, I’ll be away from my keyboard for a bit of vacation, returning Monday, August 5. So don’t worry if you don’t get a reply from me in the coming weeks. I’ll look forward to connecting with you all when I’m back.
Thanks for listening,