For those who missed today's community call
<https://cwiki.apache.org/confluence/display/FINERACT/2025-10-08+Meeting+notes> with
some stake/interest in our releases, I wanted to welcome your
discussion/feedback on what I presented today about release engineering.
This will inform future work (including mine). Note the in-progress
release
<https://lists.apache.org/thread/30w4xo1snl8o9nlkg2rd48d0pc7n5q0x> will
continue per the existing process
<https://fineract.apache.org/docs/current/#_releases>.
Here are my notes from the meeting, and you can also find the recording
online
<https://app.fireflies.ai/view/Fineract-Community-Call::01K6X2TZJXGCAQWMXWA48F7VMD>
(trying to get that downloaded as well).
*
goals for releases
o
( consider these value-driven goals first, then get to
improvements, ideal frequency, automation )
o
stable, reliable, frequent, well-documented
o
avoid vendor lock-in, leverage open source, release from any
platform
o
reproducible? non-goal, for now
<https://lists.apache.org/thread/b9f1lyxnxz9dvvhoo31yzlm82obcs569>
*
current
o
complex and manual
o
robust and inefficient
o
large codebase, gradle tasks, project & roadmap management, ASF
policies
*
proposed and in-progress work and other notes
o
understand, simplify, standardize, automate
o
test/evaluate ATR (Apache Trusted Release) tool
<https://lists.apache.org/thread/767n32q7dnwkm5mrdoqtq4yf3bqy7sb4>
o
policy/culture improvements to ease releasing
+
keep |develop| clean: be careful with WIP code/features
+
maintain your issues
o
improve documentation and release plugin, or shift to other
automation
o
we don’t currently maintain releases, vendors could do this
o
what is ideal release frequency? depends on type of fix … we may
need/want to differentiate between major, minor, patch/hotfix
releases (e.g. full ceremony doesn’t make sense for a hotfix)
--
Adam Monsen
Software Engineer ~ Mifos Initiative
Apache Fineract Release Manager
PGP key id 0xA9A14F22F57DA182
