Re: Planned Features for Fineract 1.2 Release

[Ed Cable]

For the sake of transparency to the community, we're going to miss the
target ship date of this Fineract 1.2 release which was today, March 28.

We've not been able to begin QA yet because we still need to review and
merge the pull requests for features that were ready to be shipped
documented at https://issues.apache.org/jira/projects/FINERACT/versions
/12342856

These
include:

Swagger API work: https://github.com/apache/fineract/pull/409
GSIM & GLIM work: https://github.com/apache/fineract/pull/445
Support for MySQL 5.7: https://github.com/apache/fineract/pull/448
Fix for Fineract-546: https://github.com/apache/fineract/pull/446
Fix for Fineract-574: https://github.com/apache/fineract/pull/441
Fix for Fineract-431: https://github.com/apache/fineract/pull/437

Fineract committers, could you please help with review of these pull
requests so we can move towards the monthly release cycle the community's
been yearning for.

Thanks,

Ed

On Thu, Mar 8, 2018 at 11:06 AM, Ed Cable  wrote:

> Fineract Committers,
>
> We need to merge the pull requests at https://issues.apache.org/
> jira/projects/FINERACT/versions/12342856 into develop branch so we can
> push this to our staging server and QA can begin. Could I please get some
> help with the review and merge of these PRs.
>
> Thanks,
>
> Ed
>
>
>
> On Fri, Mar 2, 2018 at 9:47 AM, Ed Cable  wrote:
>
>> Hi all,
>>
>> Just so we can keep in line with the target that we had given initially
>> around dates for the 1.2 release, here's a pseudo-announcement of the
>> release.
>>
>> The features that were ready as of the cut-off dates during our planning
>> period have been tagged and put in this fix version:
>>
>> https://issues.apache.org/jira/projects/FINERACT/versions/12342856
>>
>> They include the Swagger API Documentation by Chirag Sanyam and GSIM/GLIM
>> enhancements by Nikhil.
>>
>> Apart from small issues or enhancements that I might have missed that are
>> already complete, for 1.2 we won't be shipping any major work apart from
>> there.
>>
>> We're getting our boards configured to visualize the planning for each
>> release and are now starting the planning for 1.3 so if you have work that
>> you're planning to contribute, please make sure it has a corresponding JIRA
>> ticket.
>>
>> Thanks,
>>
>> Ed
>>
>> On Tue, Feb 27, 2018 at 9:22 AM, Ed Cable  wrote:
>>
>>> Myrle,
>>>
>>> Thanks for adding that clarity as my initial email was probably
>>> confusing. We are moving to time-driven releases and the initial planning
>>> period I mentioned was to determine which features or work was ready to be
>>> integrated and could be included in the cut-off date for that time-driven
>>> release.
>>>
>>> I have set up a scrum board and requested karma to grant Robert access
>>> so he can assist in planning out the next release, Apache Fineract 1.2
>>>
>>> Ed
>>>
>>> On Wed, Feb 14, 2018 at 4:01 AM, Sendoro Juma 
>>> wrote:
>>>
 Dear Myrle,

 I see your point:

 I think primarily we should agree that it is time-driven:

 Features listed or to be listed should be taken only as way of making
 focus and pushing for tasks to be completed in-time as per release
 schedule, should they fall short of time... we should move on... with our
 primary commitment which is time.

 How about that?

 Best Regards
 Sendoro



 - Original Message -
 From: "Myrle Krantz" 
 To: "dev" 
 Sent: Wednesday, February 14, 2018 1:55:03 PM
 Subject: Re: Planning Apache Fineract 1.2 Release

 Our release can either be feature-driven or time-driven.  Not both.
 If it's feature-driven, we don't release until the features are in
 there.  If it's time-driven, we release on a certain date, based on
 what's made it in.

 Are we in agreement that we wish to make a time-driven release?  Then
 we should be adding a feature to the list for a given release when
 that feature is integrated, and not before.

 Best Regards,
 Myrle


 On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma 
 wrote:
 > Hello Ed,
 >
 > +1 on all you mentioned!
 >
 > I would propose additional point which you have kind of mention it
 already on item related to API Swagger, but just as emphasize
 >
 > - APIs related issues/Enhancements that has been discovered by Mobile
 or Web client application side.
 >
 > This is so,  because we might take longer in addressing issues
 already known from client application side; buy just because of missing
 visibility;
 > So having this branch in Wiki page will remind us.
 >
 >
 > Best Regards
 >
 > - Original Message -
 > From: "Sendoro Juma" 

Re: Planned Features for Fineract 1.2 Release

[Ed Cable]

Fineract Committers,

We need to merge the pull requests at https://issues.apache.org/jira
/projects/FINERACT/versions/12342856 into develop branch so we can push
this to our staging server and QA can begin. Could I please get some help
with the review and merge of these PRs.

Thanks,

Ed



On Fri, Mar 2, 2018 at 9:47 AM, Ed Cable  wrote:

> Hi all,
>
> Just so we can keep in line with the target that we had given initially
> around dates for the 1.2 release, here's a pseudo-announcement of the
> release.
>
> The features that were ready as of the cut-off dates during our planning
> period have been tagged and put in this fix version:
>
> https://issues.apache.org/jira/projects/FINERACT/versions/12342856
>
> They include the Swagger API Documentation by Chirag Sanyam and GSIM/GLIM
> enhancements by Nikhil.
>
> Apart from small issues or enhancements that I might have missed that are
> already complete, for 1.2 we won't be shipping any major work apart from
> there.
>
> We're getting our boards configured to visualize the planning for each
> release and are now starting the planning for 1.3 so if you have work that
> you're planning to contribute, please make sure it has a corresponding JIRA
> ticket.
>
> Thanks,
>
> Ed
>
> On Tue, Feb 27, 2018 at 9:22 AM, Ed Cable  wrote:
>
>> Myrle,
>>
>> Thanks for adding that clarity as my initial email was probably
>> confusing. We are moving to time-driven releases and the initial planning
>> period I mentioned was to determine which features or work was ready to be
>> integrated and could be included in the cut-off date for that time-driven
>> release.
>>
>> I have set up a scrum board and requested karma to grant Robert access so
>> he can assist in planning out the next release, Apache Fineract 1.2
>>
>> Ed
>>
>> On Wed, Feb 14, 2018 at 4:01 AM, Sendoro Juma 
>> wrote:
>>
>>> Dear Myrle,
>>>
>>> I see your point:
>>>
>>> I think primarily we should agree that it is time-driven:
>>>
>>> Features listed or to be listed should be taken only as way of making
>>> focus and pushing for tasks to be completed in-time as per release
>>> schedule, should they fall short of time... we should move on... with our
>>> primary commitment which is time.
>>>
>>> How about that?
>>>
>>> Best Regards
>>> Sendoro
>>>
>>>
>>>
>>> - Original Message -
>>> From: "Myrle Krantz" 
>>> To: "dev" 
>>> Sent: Wednesday, February 14, 2018 1:55:03 PM
>>> Subject: Re: Planning Apache Fineract 1.2 Release
>>>
>>> Our release can either be feature-driven or time-driven.  Not both.
>>> If it's feature-driven, we don't release until the features are in
>>> there.  If it's time-driven, we release on a certain date, based on
>>> what's made it in.
>>>
>>> Are we in agreement that we wish to make a time-driven release?  Then
>>> we should be adding a feature to the list for a given release when
>>> that feature is integrated, and not before.
>>>
>>> Best Regards,
>>> Myrle
>>>
>>>
>>> On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma 
>>> wrote:
>>> > Hello Ed,
>>> >
>>> > +1 on all you mentioned!
>>> >
>>> > I would propose additional point which you have kind of mention it
>>> already on item related to API Swagger, but just as emphasize
>>> >
>>> > - APIs related issues/Enhancements that has been discovered by Mobile
>>> or Web client application side.
>>> >
>>> > This is so,  because we might take longer in addressing issues already
>>> known from client application side; buy just because of missing visibility;
>>> > So having this branch in Wiki page will remind us.
>>> >
>>> >
>>> > Best Regards
>>> >
>>> > - Original Message -
>>> > From: "Sendoro Juma" 
>>> > To: "dev" 
>>> > Cc: "robertjakech Jakech" 
>>> > Sent: Wednesday, February 14, 2018 1:38:01 PM
>>> > Subject: Re: Planning Apache Fineract 1.2 Release
>>> >
>>> > Hello Ed,
>>> >
>>> > +1 on all mentioned!
>>> >
>>> > I would propose additional point which you have kind of mention
>>> already on API Swagger it, but just as emphasize
>>> >
>>> > - APIs related issues/Enhancements that has been discovered by Mobile
>>> or Web Client Application side.
>>> >
>>> > This is so,  because we might take longer in addressing should known
>>> from client application side by juts because of missing visibility;
>>> > So having this branch in Wiki page will remind us.
>>> >
>>> >
>>> > Best Regards
>>> > Sendoro
>>> >
>>> >
>>> >
>>> > - Original Message -
>>> > From: "Ed Cable" 
>>> > To: "dev" , "robertjakech Jakech" <
>>> robertjak...@gmail.com>
>>> > Sent: Wednesday, February 14, 2018 9:41:07 AM
>>> > Subject: Planning Apache Fineract 1.2 Release
>>> >
>>> > That is a great suggestion Phil and of course any synchronous meeting
>>> would
>>> > only complement the discussion on the list and 

Planned Features for Fineract 1.2 Release

[Ed Cable]

Hi all,

Just so we can keep in line with the target that we had given initially
around dates for the 1.2 release, here's a pseudo-announcement of the
release.

The features that were ready as of the cut-off dates during our planning
period have been tagged and put in this fix version:

https://issues.apache.org/jira/projects/FINERACT/versions/12342856

They include the Swagger API Documentation by Chirag Sanyam and GSIM/GLIM
enhancements by Nikhil.

Apart from small issues or enhancements that I might have missed that are
already complete, for 1.2 we won't be shipping any major work apart from
there.

We're getting our boards configured to visualize the planning for each
release and are now starting the planning for 1.3 so if you have work that
you're planning to contribute, please make sure it has a corresponding JIRA
ticket.

Thanks,

Ed

On Tue, Feb 27, 2018 at 9:22 AM, Ed Cable  wrote:

> Myrle,
>
> Thanks for adding that clarity as my initial email was probably confusing.
> We are moving to time-driven releases and the initial planning period I
> mentioned was to determine which features or work was ready to be
> integrated and could be included in the cut-off date for that time-driven
> release.
>
> I have set up a scrum board and requested karma to grant Robert access so
> he can assist in planning out the next release, Apache Fineract 1.2
>
> Ed
>
> On Wed, Feb 14, 2018 at 4:01 AM, Sendoro Juma 
> wrote:
>
>> Dear Myrle,
>>
>> I see your point:
>>
>> I think primarily we should agree that it is time-driven:
>>
>> Features listed or to be listed should be taken only as way of making
>> focus and pushing for tasks to be completed in-time as per release
>> schedule, should they fall short of time... we should move on... with our
>> primary commitment which is time.
>>
>> How about that?
>>
>> Best Regards
>> Sendoro
>>
>>
>>
>> - Original Message -
>> From: "Myrle Krantz" 
>> To: "dev" 
>> Sent: Wednesday, February 14, 2018 1:55:03 PM
>> Subject: Re: Planning Apache Fineract 1.2 Release
>>
>> Our release can either be feature-driven or time-driven.  Not both.
>> If it's feature-driven, we don't release until the features are in
>> there.  If it's time-driven, we release on a certain date, based on
>> what's made it in.
>>
>> Are we in agreement that we wish to make a time-driven release?  Then
>> we should be adding a feature to the list for a given release when
>> that feature is integrated, and not before.
>>
>> Best Regards,
>> Myrle
>>
>>
>> On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma 
>> wrote:
>> > Hello Ed,
>> >
>> > +1 on all you mentioned!
>> >
>> > I would propose additional point which you have kind of mention it
>> already on item related to API Swagger, but just as emphasize
>> >
>> > - APIs related issues/Enhancements that has been discovered by Mobile
>> or Web client application side.
>> >
>> > This is so,  because we might take longer in addressing issues already
>> known from client application side; buy just because of missing visibility;
>> > So having this branch in Wiki page will remind us.
>> >
>> >
>> > Best Regards
>> >
>> > - Original Message -
>> > From: "Sendoro Juma" 
>> > To: "dev" 
>> > Cc: "robertjakech Jakech" 
>> > Sent: Wednesday, February 14, 2018 1:38:01 PM
>> > Subject: Re: Planning Apache Fineract 1.2 Release
>> >
>> > Hello Ed,
>> >
>> > +1 on all mentioned!
>> >
>> > I would propose additional point which you have kind of mention already
>> on API Swagger it, but just as emphasize
>> >
>> > - APIs related issues/Enhancements that has been discovered by Mobile
>> or Web Client Application side.
>> >
>> > This is so,  because we might take longer in addressing should known
>> from client application side by juts because of missing visibility;
>> > So having this branch in Wiki page will remind us.
>> >
>> >
>> > Best Regards
>> > Sendoro
>> >
>> >
>> >
>> > - Original Message -
>> > From: "Ed Cable" 
>> > To: "dev" , "robertjakech Jakech" <
>> robertjak...@gmail.com>
>> > Sent: Wednesday, February 14, 2018 9:41:07 AM
>> > Subject: Planning Apache Fineract 1.2 Release
>> >
>> > That is a great suggestion Phil and of course any synchronous meeting
>> would
>> > only complement the discussion on the list and collaboraton on the wiki
>> > that we'll be having.
>> >
>> > Taking up Phil's suggestion, let's begin the discussion on this new
>> thread
>> > for planning what should goi into Apache Fineract 1.2. To assist in that
>> > I've set up a wiki page at
>> > https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
>> +Apache+Fineract
>> >
>> > Based on what I know others have been working on, here's my take on
>> some of
>> > the work that could be included in the release.
>> >
>> >- GSIM/GLIM Work from Nikhil as