Hi y'all,
release ready
I was able to shorten the last release from 17 to 6 days because the
develop branch was already in a release-able state
<https://lists.apache.org/thread/70j8s1wkk7mj2ho86kr5vnmf96yls04s>.
I propose we try to do this always
<https://github.com/apache/fineract/pull/5379>. That is, we keep the
build passing and keep incomplete features off develop. Thoughts?
vNext release manager
Is anyone interested in doing this for the next (quarterly) release (in
March)? Let me know. Ideally you're already a member of the PMC, but it
may be possible for any committer to do it.
I was discussing with James the other day how it would be good to have
redundancy here. The instructions
<https://fineract.apache.org/docs/current/#_releases> should be up to
date, and I'm happy to pair with someone on this since the process has
changed a bit.
release branch/merge strategy
Just to tie up an old loose end: I researched, discussed, and formalized
<https://github.com/apache/fineract/commit/67272d1aea163da9bebdf6ff56ead270bd47632d>
this process. I made no changes to branching: This is straightforward,
you just need a good commit to start from. I changed merging as
documented to use a /traditional/ merge so git describe works as expected.
Best and thanks,
-Adam
--
Adam Monsen
Software Engineer » Mifos Initiative
Release Manager » Apache Fineract
Author » Steadfast Self-Hosting
PGP key » 0xA9A14F22F57DA182
