Greetings and Happy New Year 2017 from team Lucee. I’m the Lucee Product Manager, and as I mentioned in a blog post today, we’re geeked to announce a new release schedule for Lucee in 2017. We’ve been doing sprint planning for the past couple of months, and the January sprint is underway, and February is planned as well. Our goal is to ship 10 releases of Lucee in 2017, so it’s mostly a “monthly” schedule, but only 10 vs. 12 releases, in order to allow time for things like conferences/road shows, holidays/vacations, along with allowing some schedule padding to account for the normal vagaries of software development.
We’ll ship releases at the end of each month with a release, and then we’ll also publish a retrospective to discuss the release, how the sprint went, etc.
In the interests of full disclosure, here are some details about how we’re selecting tickets for the monthly sprints/releases:
- Regressions and security remediations are always a top priority.
- Upvoting and the amount of commenting activity are important indicators to us, too. The more of this activity we see, the more likely those tickets are to be chosen for sprints sooner rather than later.
- Priority relative to the Lucee product road map. Releases will include features (new and/or enhanced) as well as bug fixes, so when tickets relate to features from the product roadmap that we think it’s a good time to implement, we’ll add those to the monthly sprints.
- “Gut feel,” internal LAS discussion/debate, sponsored fixes/features, (paid for by interested parties), etc. This is a “bucket” of other considerations that may influence choosing tickets for sprints as well.
As always, we want as much interaction with the CFML community as is humanly possible. This forum will be the place to discuss Lucee sprint planning, sprints, releases, and any related topics. (But please do continue to vote and comment on individual tickets in the Lucee JIRA .)
Since this is our first effort at sprint planning, and publishing a formal Lucee release schedule to the community, keep in mind that it’s a work in progress. We will iteratively improve the process over time. Please share any and all questions/comments/feedback. In general, we’ll be posting a lot more information as an organization, including on this topic of monthly releases. Stay tuned.
Meantime, here are screenshots of the January and February sprints, with links to the ticket lists for each:
Again, holler with any input you have. Here’s to a great 2017 for Lucee and CFML!