Re: Testimonials for potential graduation announcement?

Presently, I cannot comment on my 'at-work' usage, but would be willing to do so with my asf hat on, if that would be useful. > On Mar 14, 2017, at 4:23 PM, Myrle Krantz wrote: > > Hello Fineracters > > We are currently starting the process of graduation from the incubator. >

Re: Please help evaluate Fineract's readiness for graduation

Can you add Write access for my cwiki account: Jim Jagielski, j...@apache.org Thx > On Feb 15, 2017, at 11:20 AM, Myrle Krantz <myrle.kra...@kuelap.io> wrote: > > Hello Fineracters, > > I believe we've made enough progress to start the process of graduation. > >

Re: [Fineract] Maturity Evaluation - Quality - PMD & Findbugs integration

All good. +1 > On Feb 14, 2017, at 7:30 AM, Shaik Nazeer > wrote: > > Hi all, > > > > We are planning to integrate 'PMD' and 'Findbugs' gradle plugins as part of > Fineract build script(s) to maintain the code quality. I feel there > shouldn't be any

Re: Please help evaluation Fineract's readiness for graduation

ed to QU10, QU40, and RE50. >> >> Could you provide me access to the Apache Fineract website to address >> CO10 and then for CS10 do we want that on the Apache Fineract website >> or the wiki? >> >> Thanks, >> >> Ed >> >> On Tue, Jan 10, 2

Re: [VOTE] Release Apache Fineract 0.6.0 (incubating)

+1. Thx! > On Jan 12, 2017, at 7:36 AM, Nazeer Shaik wrote: > > Hi John, > > We have closed the Jira issue > https://issues.apache.org/jira/browse/FINERACT-357 and created two separate > jira issues for remaining two items.RAT is integrated such a way it will > check

Re: [Apache Fineract] Steps for release signing

Cool. Some projects also use bz2 in addition to gz or even instead of. > On Jan 12, 2017, at 7:40 AM, Nazeer Shaik > wrote: > > Hi all, > We have documented steps for signing Apache Fineract releases. Please find > the document location >

Re: Please help evaluation Fineract's readiness for graduation

Agreed. > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik wrote: > > On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable wrote: >> Could our Apache Fineract mentors please provide some guidance on a couple >> of the areas we need to improve upon: >> >> QU10 "*The

Re: [VOTE] [APACHE FINERACT] 0.6.0-incubating for release

+1 to all. > On Jan 10, 2017, at 7:39 AM, Myrle Krantz wrote: > > Hi all, > > +1 > > The build is working > Signatures are good > > Things we should improve by the next release: > * Create a branch in git and tag the release changeset before the call to > vote is sent out.

Re: [VOTE] Release Apache Fineract 0.5.0 (incubating)

t Conflux Technologies Private Limited or its > subsidiaries and associated companies are unable to exercise control or > ensure or guarantee the integrity of/over the contents of the information > contained in e-mail transmissions. Before opening any attachments, please > check. > &g

Re: [VOTE] Release Apache Fineract 0.5.0 (incubating)

+1 (binding) > On Dec 19, 2016, at 3:33 AM, Nazeer Shaik wrote: > > Hi all, > > We are extending voting time for another 48 hrs as we didn't get any > response. Request you to review and vote for this release. > > Thanks, > Nazeer > > On Tue, Dec 13, 2016 at 12:55

Re: [VOTE] Release Apache Fineract 0.5.0 (incubating)

> On Dec 19, 2016, at 8:46 PM, John D. Ament wrote: > > Hi, > > So to point out, release vote threads are open *at least* 72 hours. There > is no reason to add an extra 48 hours to the vote, it'll close when it > passes That's not quite 100% true... The vote doesn't

Re: [Apache Fineract] - License & Notice files for source and binary releases

They look fine... I would have prefered a 80col limit on the text though, to make it easier for humans to read. > On Dec 6, 2016, at 12:29 AM, Nazeer Shaik > wrote: > > Hi Fineract Mentors, > > We are planning to release Apache Fineract 0.5.0-incubating

JIRA vs. Email lists

There have been a few discussions which have taken place on JIRA when, ideally, they should have take place here on the dev@ list. I'd like to see us focus on using JIRA less as a communications tool and try to get more discussion and conversation here on-list.

Re: [MENTORS] Managing non-Apache code from ASF resources?

> On Nov 28, 2016, at 7:54 PM, Roman Shaposhnik wrote: > > On Tue, Nov 22, 2016 at 4:53 AM, Myrle Krantz wrote: >> Hi Mentors, >> >> As you know Apache Fineract has a UI project which Mifos did not donate to >> the ASF because it's not licensable in

Re: Fineract Board Report for November

Sounds like a plan to me :) > On Oct 30, 2016, at 7:30 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > > On Thu, Oct 27, 2016 at 10:27 AM, Jim Jagielski <j...@jagunet.com> wrote: >> Thx for the report! >> >> I would like to raise the possibility o

Re: Fineract Board Report for November

Thx for the report! I would like to raise the possibility of calling for Graduation of Fineract. What does everyone think? > On Oct 27, 2016, at 1:22 PM, Ed Cable wrote: > > Hi all, > > I've started the Board Report for November: > >

Re: [VOTE] [FINERACT] 0.4.0-incubating for release

+1

Re: Microservices release question

++1 > On May 31, 2016, at 1:21 AM, Adi Raju > wrote: > > I would expect there would be X number of microservices which are core/heart > of the application which no deployment can do away with. I would suggest > these to be released as a single

Re: [VOTE] [FINERACT] 0.1.1-incubating for release

But we don't see any issues if we prepare same release on > Linux machine. Even the mentioned test case passes without any code change. > > *So we are withdrawing the current release from voting.* > > We will work on 0.1.2-incubating release. > > Thanks, > Nazeer >

Re: Jim Jagielski: Will you be our mentor?

I am afraid that by accepting I would be "agreeing" to the statement that a "mistake" was made in my original offer to be a mentor ;) It would be my extreme pleasure to accept with that caveat > On May 5, 2016, at 2:08 AM, Myrle Krantz wrote: > > Dear Jim, > > We made a

ramping up

As people may recall, I offered to mentor fineract but we had sufficient mentors. I am starting to ramp up my actual dev involvement in anticipation of getting commit. Suggestions and focus areas welcomed.