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 <edca...@mifos.org> 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 <edca...@mifos.org> 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 <sendoro@singo.africa> >> 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" <my...@apache.org> >>> To: "dev" <dev@fineract.apache.org> >>> 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 <sendoro@singo.africa> >>> 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" <sendoro@singo.africa> >>> > To: "dev" <dev@fineract.apache.org> >>> > Cc: "robertjakech Jakech" <robertjak...@gmail.com> >>> > 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" <edca...@mifos.org> >>> > To: "dev" <dev@fineract.apache.org>, "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 part of GSOC >>> > - Swagger APIs work done by Sanyam and Chirag >>> > - Apache Fineract tasks completed by GCI students. >>> > - Changes contributed by Partners including: >>> > - BOWPI Enhancements >>> > - Stellar/Fineract integration >>> > - Bug Fixes and Minor Enhancements. >>> > - PRs from the backlog >>> > >>> > >>> > Let's drive this discussion forward and then a have a synchronous >>> meeting >>> > later to hammer out details. >>> > >>> > Ed >>> > >>> > On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com> >>> wrote: >>> > >>> >> On 2/12/18 9:32 AM, Ed Cable wrote: >>> >> > Here's the link to screencast from the discussion: >>> >> > https://youtu.be/xnTGf4R2s5k >>> >> > >>> >> > Ed >>> >> > >>> >> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org> >>> wrote: >>> >> > >>> >> >> Hi all, >>> >> >> >>> >> >> Thanks to Nazeer for leading this session and the sizeable group >>> that >>> >> >> attended. Based on the process, we can clearly use the assistance >>> of >>> >> other >>> >> >> community members in the planning process and committers in the >>> release >>> >> >> process so happy we had such good attendance. >>> >> >> >>> >> >> Based on the discussion, here's a proposal of how timing might >>> look for >>> >> >> monthly release cycles with planning (a new phase) starting out six >>> >> months >>> >> >> prior to the release date. >>> >> >> >>> >> >> Screencast of session will be posted soon. >>> >> >> >>> >> >> Please comment on the notes in the table and here's proposed >>> timing for >>> >> >> the next 1.2 release: >>> >> >> >>> >> >> Plans for Release Apache Fineract 1.2 >>> >> >> >>> >> >> Planning Release - Start with a Meeting on Feb 14 >>> >> >>> >> How about starting with a discussion on this list? Relying on >>> >> synchronous meetings cuts out people who can't attend due to time >>> >> zones / other commitments. >>> >> >>> >> Phil >>> >> >> >>> >> >> Announce Release - Feb 28 >>> >> >> >>> >> >> QA - Feb 28 - March 14 >>> >> >> >>> >> >> Publish Release Notes - March 14 >>> >> >> >>> >> >> Vote on Release - March 21 >>> >> >> >>> >> >> Target release date - March 28 >>> >> >> >>> >> >> Stage >>> >> >> >>> >> >> Description >>> >> >> >>> >> >> Proposed Length >>> >> >> >>> >> >> How Far in Advance of Release (Proposed) >>> >> >> >>> >> >> How Far in Advance of Release (Currently) >>> >> >> >>> >> >> Planning of Next Release >>> >> >> >>> >> >> Discuss with community what would like to ship in next release and >>> what >>> >> >> people could work on. >>> >> >> >>> >> >> Create fix version on JIRA to assign to. >>> >> >> >>> >> >> Action: modify existing email template to open up planning process, >>> >> >> schedule a meeting to discuss and set a tentative branching date >>> (i.e. 2 >>> >> >> weeks later, if release date is a month past that). >>> >> >> >>> >> >> . >>> >> >> >>> >> >> 1 week >>> >> >> >>> >> >> 6 weeks >>> >> >> >>> >> >> Doesn’t Exist >>> >> >> >>> >> >> Announcement of Release >>> >> >> >>> >> >> Announce what is going to come in the release (should be 80% done >>> at >>> >> >> least). >>> >> >> >>> >> >> Cut a release branch and freeze release branch and then develop >>> branch >>> >> can >>> >> >> still have active work on it but only in rare cases might anything >>> >> >> additional from develop >>> >> >> >>> >> >> Email out sharing release branch details >>> >> >> >>> >> >> 4 weeks prior >>> >> >> >>> >> >> 1 - 2 months >>> >> >> >>> >> >> QA >>> >> >> >>> >> >> QA begins on the release branch - staging Server setup >>> >> >> >>> >> >> Might fix some regression issues >>> >> >> >>> >> >> 1 - 2 weeks >>> >> >> >>> >> >> 4 weeks prior >>> >> >> >>> >> >> JIRA Sanitization/Publish RElease Notes >>> >> >> >>> >> >> Sanitize release documentation >>> >> >> >>> >> >> Create release notes and email community release information with >>> links. >>> >> >> >>> >> >> >>> >> >> 2 weeks prior >>> >> >> >>> >> >> Vote >>> >> >> >>> >> >> Create artifacts, sign release, etc. Open up votes >>> >> >> >>> >> >> 1 week prior >>> >> >> >>> >> >> Release >>> >> >> >>> >> >> Tally up votes, announce, update websites and infrastructure with >>> new >>> >> >> release artifacts. >>> >> >> >>> >> >> Release date >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> On Sun, Feb 11, 2018 at 7:40 AM, Ed Cable <edca...@mifos.org> >>> wrote: >>> >> >> >>> >> >>> Hi all, >>> >> >>> >>> >> >>> This meeting is happening now for anybody that wants to join. >>> >> >>> >>> >> >>> Ed >>> >> >>> >>> >> >>> On Sat, Feb 10, 2018 at 6:07 AM, Ed Cable <edca...@mifos.org> >>> wrote: >>> >> >>> >>> >> >>>> Hi all >>> >> >>>> >>> >> >>>> Woule 1530GMT work on Sunday? Nazeer had a conflict on Saturday. >>> I'll >>> >> >>>> update the GoToTraining session. >>> >> >>>> >>> >> >>>> Ed >>> >> >>>> >>> >> >>>> On Thu, Feb 8, 2018 at 9:19 AM, Sendoro Juma >>> <sendoro@singo.africa> >>> >> >>>> wrote: >>> >> >>>> >>> >> >>>>> Hello Ed, >>> >> >>>>> >>> >> >>>>> Just in case, same Saturday(s) but starting 15:30GMT! >>> >> >>>>> >>> >> >>>>> if it is fine with Nazeer, then we will very much appreciate... >>> >> >>>>> >>> >> >>>>> Sorry our request is based on the fact on belief/religious >>> related! >>> >> >>>>> >>> >> >>>>> Cheers >>> >> >>>>> Sendoro >>> >> >>>>> >>> >> >>>>> ----- Original Message ----- >>> >> >>>>> From: "Ed Cable" <edca...@mifos.org> >>> >> >>>>> To: "dev" <dev@fineract.apache.org> >>> >> >>>>> Cc: "Nazeer Hussain Shaik" <nazeerhussain.sh...@gmail.com> >>> >> >>>>> Sent: Thursday, February 8, 2018 7:05:55 PM >>> >> >>>>> Subject: Re: Meeting to Discuss Release Management Process >>> >> >>>>> >>> >> >>>>> Hmm... We can reschedule to accommodate everyone. Weekdays >>> might be >>> >> >>>>> difficult for Nazeer with his new schedule. >>> >> >>>>> >>> >> >>>>> Ed >>> >> >>>>> >>> >> >>>>> On Thu, Feb 8, 2018 at 7:42 AM, Sendoro Juma >>> <sendoro@singo.africa> >>> >> >>>>> wrote: >>> >> >>>>> >>> >> >>>>>> Hello Ed, >>> >> >>>>>> >>> >> >>>>>> Hope you will record, >>> >> >>>>>> >>> >> >>>>>> I see two members missing from our side because of that new >>> timing. >>> >> >>>>>> >>> >> >>>>>> Cheers >>> >> >>>>>> Sendoro >>> >> >>>>>> >>> >> >>>>>> ----- Original Message ----- >>> >> >>>>>> From: "Ed Cable" <edca...@mifos.org> >>> >> >>>>>> To: "dev" <dev@fineract.apache.org> >>> >> >>>>>> Cc: "Nazeer Hussain Shaik" <nazeerhussain.sh...@gmail.com> >>> >> >>>>>> Sent: Thursday, February 8, 2018 5:05:35 PM >>> >> >>>>>> Subject: Re: Meeting to Discuss Release Management Process >>> >> >>>>>> >>> >> >>>>>> Hi all, >>> >> >>>>>> >>> >> >>>>>> Nazeer is not available till Saturday for this meeting so I am >>> going >>> >> >>>>> to >>> >> >>>>>> adjust the timing to Saturday at 1400GMT and will update the >>> >> >>>>> GoToTraining >>> >> >>>>>> session accordingly. >>> >> >>>>>> >>> >> >>>>>> Ed >>> >> >>>>>> >>> >> >>>>>> On Thu, Feb 8, 2018 at 6:46 AM, Awasum Yannick < >>> >> >>>>>> awasum.yann...@skylabase.com >>> >> >>>>>>> wrote: >>> >> >>>>>>> I already registered for it. >>> >> >>>>>>> >>> >> >>>>>>> I hope it happens. >>> >> >>>>>>> >>> >> >>>>>>> Thanks >>> >> >>>>>>> Awasum >>> >> >>>>>>> >>> >> >>>>>>> On Thu, Feb 8, 2018 at 1:23 PM, Nikhil Pawar < >>> nickr...@gmail.com> >>> >> >>>>> wrote: >>> >> >>>>>>>> Is this meeting happening? >>> >> >>>>>>>> I’ll be interested to participate. >>> >> >>>>>>>> >>> >> >>>>>>>> Regards, >>> >> >>>>>>>> Nikhil >>> >> >>>>>>>> >>> >> >>>>>>>> On Wed, Feb 7, 2018 at 10:54 AM Ed Cable <edca...@mifos.org> >>> >> >>>>> wrote: >>> >> >>>>>>>>> Nazeer, >>> >> >>>>>>>>> >>> >> >>>>>>>>> Per the other email thread, we'd like to set up a meeting to >>> >> >>>>> both >>> >> >>>>>>> discuss >>> >> >>>>>>>>> and improve our release management process and to transfer >>> >> >>>>> knowledge >>> >> >>>>>> to >>> >> >>>>>>>>> additional Apache Fineract committers who would like to help >>> >> >>>>> with the >>> >> >>>>>>>>> release management process. >>> >> >>>>>>>>> >>> >> >>>>>>>>> Hopefully after this meeting, we'll be able to update our >>> wiki >>> >> >>>>> page >>> >> >>>>>> on >>> >> >>>>>>>>> release management - >>> >> >>>>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/ >>> >> >>>>>>> Release+Management >>> >> >>>>>>>>> - with these processes and have an expanded team of release >>> >> >>>>> managers >>> >> >>>>>>> to >>> >> >>>>>>>>> help the community release more consistently and more often. >>> >> >>>>>>>>> >>> >> >>>>>>>>> Would this Friday at 1400GMT work? I'll create a >>> GoToTraining >>> >> >>>>> session >>> >> >>>>>>> in >>> >> >>>>>>>>> which others can register and join: >>> >> >>>>>>>>> https://attendee.gototraining.com/r/2808817190976822274 >>> >> >>>>>>>>> >>> >> >>>>>>>>> Thanks, >>> >> >>>>>>>>> >>> >> >>>>>>>>> Ed >>> >> >>>>>>>>> >>> >> >>>>>>>>> >>> >> >>>>>>>>> >>> >> >>>>>>>>> -- >>> >> >>>>>>>>> *Ed Cable* >>> >> >>>>>>>>> President/CEO, Mifos Initiative >>> >> >>>>>>>>> edca...@mifos.org | Skype: edcable | Mobile: >>> +1.484.477.8649 >>> >> >>>>>>>>> >>> >> >>>>>>>>> *Collectively Creating a World of 3 Billion Maries | * >>> >> >>>>>> http://mifos.org >>> >> >>>>>>>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >>>>>>>>> >>> >> >>>>>> >>> >> >>>>>> >>> >> >>>>>> -- >>> >> >>>>>> *Ed Cable* >>> >> >>>>>> President/CEO, Mifos Initiative >>> >> >>>>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >>> >> >>>>>> >>> >> >>>>>> *Collectively Creating a World of 3 Billion Maries | * >>> >> >>>>> http://mifos.org >>> >> >>>>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >>>>>> >>> >> >>>>> >>> >> >>>>> >>> >> >>>>> -- >>> >> >>>>> *Ed Cable* >>> >> >>>>> President/CEO, Mifos Initiative >>> >> >>>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >>> >> >>>>> >>> >> >>>>> *Collectively Creating a World of 3 Billion Maries | * >>> >> http://mifos.org >>> >> >>>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >>>>> >>> >> >>>> >>> >> >>>> >>> >> >>>> -- >>> >> >>>> *Ed Cable* >>> >> >>>> President/CEO, Mifos Initiative >>> >> >>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >>> >> >>>> <(484)%20477-8649> >>> >> >>>> >>> >> >>>> *Collectively Creating a World of 3 Billion Maries | * >>> >> http://mifos.org >>> >> >>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >>>> >>> >> >>>> >>> >> >>> >>> >> >>> -- >>> >> >>> *Ed Cable* >>> >> >>> President/CEO, Mifos Initiative >>> >> >>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >>> >> >>> <(484)%20477-8649> >>> >> >>> >>> >> >>> *Collectively Creating a World of 3 Billion Maries | * >>> http://mifos.org >>> >> >>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >>> >>> >> >>> >>> >> >> >>> >> >> -- >>> >> >> *Ed Cable* >>> >> >> President/CEO, Mifos Initiative >>> >> >> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >>> >> >> <(484)%20477-8649> >>> >> >> >>> >> >> *Collectively Creating a World of 3 Billion Maries | * >>> http://mifos.org >>> >> >> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >> >>> >> >> >>> >> > >>> >> >>> >> >>> > >>> > >>> > -- >>> > *Ed Cable* >>> > President/CEO, Mifos Initiative >>> > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >>> > >>> > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >>> > <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >> >> >> -- >> *Ed Cable* >> President/CEO, Mifos Initiative >> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 >> <(484)%20477-8649> >> >> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >> >> > > > -- > *Ed Cable* > President/CEO, Mifos Initiative > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 > <(484)%20477-8649> > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org > <http://facebook.com/mifos> <http://www.twitter.com/mifos> > > -- *Ed Cable* President/CEO, Mifos Initiative edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 *Collectively Creating a World of 3 Billion Maries | *http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos>
