Thanks for the clarification.
We are talking about the same thing here, simply interpreting
terms differently.
I like to introduce another term, used by GitLab, times-based
released, because I think this is the clearest term we can use
for the proposed process.
We will create a release every two month with all feature
branches that were merged into the develop branch prior
to the creation of the release branch. That is my understanding.
Best,
Markus
.::YAGNI likes a DRY KISS::.
On 01/08/2016 10:57 AM, Myrle Krantz wrote:
I'm not entirely sure we are talking about the same thing.
As I wrote in the document I sent to start this thread:
https://cwiki.apache.org/confluence/display/FINERACT/Release+Management
"Release branches are created every two months at the beginning of the
following month from the changes that were merged by the last day of the
previous month.
If a feature is almost but not quite done at the end of the month, the
release is not delayed for the feature. That feature goes into the next
release scheduled for two months later."
If we choose to work according to the plan I described, then we would be
working on a date-driven cadence, at least as I understand it.
Of course we are releasing features and not tool bundles, so we won't make
a release if there are no changes merged in those two months. If there's
even one change, I would expect a release. And if that change is finished
two days after the deadline, I would expect the release to come at the next
two-monthly release.
Gitlab does something similar, but with a release period of one month:
https://about.gitlab.com/2015/12/07/why-we-shift-objectives-and-not-release-dates-at-gitlab/
Greets,
Myrle
*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
[email protected] | Skype: mkrantz.mifos.org | http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
On Thu, Jan 7, 2016 at 7:13 PM, Markus Geiss <[email protected]> wrote:
On 01/07/2016 05:36 PM, Roman Shaposhnik wrote:
On Thu, Jan 7, 2016 at 3:52 AM, Myrle Krantz <[email protected]> wrote:
Hi Fin Fans,
To start the conversation on release cycle, I've documented my suggestion
here:
https://cwiki.apache.org/confluence/display/FINERACT/Release+Management
The additions to what was there before consist of:
* release cycle length added
* soak period shortened to better match release cycle length
Would it be possible to spell out your release cadence model more
explicitly?
Is it a date-driven cadence (like Ubuntu, lets say) or a feature-driven
one?
Thanks,
Roman.
Given that we are releasing a software product, not a distribution of a
certain kind, e.g. Ubuntu, CentOS, Mint, I think a feature-driven
model.
The development of Fineract will be driven by user requirements,
specific to the platform. Bundled libraries will only have influence
on the release schedule if a security issue was detected and fixed.
Best,
Markus
.::YAGNI likes a DRY KISS::.
