With option 2) how are we going to prepare a release for 1 or 2 micro services?
Regards, Nazeer On Tue, Dec 12, 2017 at 2:30 PM, Ippez Robert <[email protected]> wrote: > Option #2 can accommodate us. > > Regards > Ippez Robert > > On Tue, Dec 12, 2017 at 11:05 AM, Sendoro Juma <[email protected]> > wrote: > > > Hello Myrle, > > > > #2 is for me moderate and preferably > > > > Both #1 and #3 will bring complexity which may end-up bring volume of > > emails for just clarifications purpose only etc. > > > > Best Regards > > Sendoro > > > > ----- Original Message ----- > > From: "Myrle Krantz" <[email protected]> > > To: "dev" <[email protected]> > > Sent: Tuesday, December 12, 2017 10:01:44 AM > > Subject: [DISCUSS] Fineract CN issue tracking > > > > Hey all, we need to decide how to do issue tracking for Fineract CN. > > > > I see a couple of possibilities: > > 1.) We do it under Fineract and create new components for the Fineract > > CN components. > > 2.) We request a new Jira project for Fineract CN. > > 3.) We request a new Jira project for each of our 33 Fineract CN > > repositories. > > > > I recommend we go with option #2. Option #1 is likely to cause > > confusion. Option #3 would force us to request a new jira project > > each time we add a repo. > > > > What do you all think? > > > > Regards, > > Myrle > > > > > > -- > Ippez Roberts > Founder/C.E.O - Swift3 Technologies (U) Ltd > "Redefining Next Generation I/O Systems" > P.O.Box 155, Moyo > UGANDA. > Tel: +256788725408/770602630 > Skype ID: ippez.robert1 > Email: [email protected] >
