* bump minor number and make a release when changes amount counts ~N (let's
say 500).
I think we should focus on a predictable release plan based on dates and
not the number of changes/commits. It's better for the end users and
companies if they can rely on a stable release plan.
Michal
On 11/1/26 09:02, Tomek CEDRO wrote:
Hello Alin :-)
Which one would you prefer and would help your work as our Release Manager??
Maybe there is some third option available like:
* bump patch number / intermediate release when security or other important
fixes are needed right away when ready (not only 90 days).
* bump minor number and make a quarterly release every ~3 months.
* bump minor number and make a release when changes amount counts ~N (let's
say 500).
If there are too many changes to process quarterly maybe a release based on
changes count world help you in the process with smaller but more frequent
steps?
Answering your question, both options work for me if they work for you,
thus my question which one is the best for you, I will follow :-)
Thank you for your amazing work Alin!! :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Sat, Oct 31, 2026, 15:38 Alin Jerpelea <[email protected]> wrote:
Hi all,
during past 3 years NuttX had a quarterly release plan
for the past year we had the following releases:
31-12-2025 12.12.0
02-04-2026 12.13.0
12-07-2026 13.0.0
04-10-2020 13.1.0
each release containing around 800 PR
Since security reports have increased I started doing 90 days intermediate
releases
15-09-2026 13.0.1
15-11-2026 13.1.1 (under release)
For each 90 day release I was planning to include fixes, QOL improvements
and security fixes
*For 90 days releases *
*-would you like to have just security fixes ?*
*-should include non breaking fixes and improvements ?*
Best regards
Alin J
