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> >> >> >
