Greetings everyone,

I'm Luis Espinoza, Project Manager at Fiter. I've been discussing important
organization improvements on the Fineract Release process with a few of us
and I'd like to share these with the whole community. Here are some of the
suggestions.

   - Taking advantage of Jira we could create Release Sprints. For example
   we could start with version1.5.1. I've already created this Sprint with an
   end of June due date.
   - These Sprints could have a specific due date and most important a goal
   or a theme. For example 1.5.1 could be loan functionalities oriented, or
   security oriented, take your pick, and it would be a month long. Maybe
   since we'll be starting with this version we could just include items that
   are most urgent and are confident will be worked on.
   - So we would inform the community (devs and reporters) what is the goal
   and due date of the sprint. Then, if anyone feels we can include their work
   or suggestions in the release theme, then they would need to include that
   particular ticket on the sprint and follow it's progress.
   - To make code revision easier we would only go over the tickets marked
   as Done within the active Sprint.
   - From what I discussed with Aleks the easiest way to do this is cherry
   picking these commits, and they should be small changes so unit testing is
   more effective. So breaking down tasks into 1 week tickets at the most
   could be very helpful (and easier if we use this Release Sprints method).
   - The community could still keep working on tasks outside the next
   release, just maybe could wait until we reach a specific theme to commit.
   Or if it is a well tested and important enough change, an exception could
   be made to include it in the current release.
   - The version, theme and due dates of the Release Sprints could be sent
   to the community whenever we're about to release a version and start a new
   one.

I truly believe this would help to have releases more often and they would
be more focused, easier to check and more useful to the community. I hope
this information was useful for you and I'd be happy to get some feedback
and together we can go over this idea and help make it happen.

Best Regards.

-- 
[image: Logo] <https://www.fiter.io/>
*Luis Espinoza* *| Project Manager*
*e:* [email protected]
*w:* fiter.io <http://www.fiter.io/>
*m:* +591-72285850
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>

Reply via email to