Fred - we are NOT voting here. different thread. see https://lists.apache.org/[email protected] [VOTE] FSIP-9: Standardize on PostgreSQL
James Dailey James Dailey On Mon, Mar 23, 2026 at 3:41 PM Fred Amaral via dev <[email protected]> wrote: > +1 on my side. > > On Mon, Mar 23, 2026 at 7:40 PM James Dailey <[email protected]> > wrote: > >> Sifiso - did you mean to vote +1 (plus one) ? >> >> From your email it sounded like you are concerned about the 40 MFIs >> that need migration. In that case you *could* register a -1 (opposed) >> or a +0 (neutral) on the vote. >> >> Please have a few of those MFIs come to the dev list with their >> particulars - what version are they running? (release date of fineract ) >> and if they have custom code, how extensive is it, and if they are intent >> on upgrading to the latest, when would they want to do that? >> Then, perhaps we could have them register the specifics in a jira ticket >> and someone could work on it. >> >> Specifics matter. >> >> James Dailey >> >> >> >> On Mon, Mar 23, 2026 at 2:35 PM VICTOR MANUEL ROMERO RODRIGUEZ < >> [email protected]> wrote: >> >>> Sifiso and Campbell, >>> >>> There is an ongoing vote about the use of Postgres DB only in Apache >>> Fineract. >>> >>> You can participate as non-binding >>> >>> Regards >>> >>> Victor >>> >>> El lun, 23 mar 2026 a las 13:23, Sifiso Mtetwa (< >>> [email protected]>) escribió: >>> >>>> Hi James, >>>> >>>> We have around 40 MFIs running on MariaDB and it would be an absolute >>>> necessity that we have migration scripts to facilitate this new move to >>>> Postgres. Without it they would be stuck on the old fork. >>>> >>>> Regards, >>>> >>>> *From:* Campbell Burgess [mailto:[email protected]] >>>> *Sent:* Monday, 23 March 2026 19:19 >>>> *To:* [email protected] >>>> *Subject:* Re: End support of mySQL and MariaDB; migration tooling >>>> related to FSIP-9, >>>> >>>> >>>> >>>> We'll help sponsor that. >>>> >>>> Campbell >>>> >>>> On 3/23/2026 11:25 AM, James Dailey wrote: >>>> >>>> The vote on FSIP-9 entails the idea that *someone* should make efforts >>>> to build migration scripts. As that vote ends in 48 hrs, now is another >>>> good moment of focus. >>>> >>>> >>>> >>>> "With this proposal we will make an effort but *we are not committing* to >>>> migration guides, scripts, tests, tools, wizards, and case studies easing >>>> database migrations. The community is strongly encouraged to *gather >>>> real-world data*, to share and discuss this proposal with all users, >>>> encouraging them to create or sponsor creation of these >>>> critically important migration materials." >>>> >>>> >>>> >>>> As with all things on this open source project, if there is interest in >>>> doing it, it can occur. >>>> >>>> >>>> >>>> First up is "Gather real world data". How many entities require this >>>> migration work? Can we get at least two good examples? More? >>>> >>>> >>>> >>>> I suspect that any organization still using mySQL or MariaDB is on a >>>> very old fork of the project and has no interest in upgrading to the latest >>>> releases. If that is wrong, someone should provide data to support that. >>>> They have not spoken up specifically. We must hear from them. >>>> >>>> >>>> >>>> For scripts and guides to have meaning, they need users. >>>> >>>> >>>> >>>> -- >>>> >>>> Herring BANCORP ® >>>> >>>> >>>> *C. Campbell Burgess*President/CEO >>>> Office: (806) 373-3921 | Direct: (806) 242-3704 >>>> >>>> [email protected] >>>> >>>> >>>> *Herring Bancorp* >>>> 2201 Civic Circle, Suite 1000 >>>> Amarillo, TX 79109 >>>> >>>> www.herringbank.com >>>> >>>> CONFIDENTIALITY NOTE: This e-mail is intended only for the use of the >>>> individual or entity to which it is addressed and may contain information >>>> that is privileged, confidential and exempt from disclosure under >>>> applicable law. If the reader of this e-mail message is not the intended >>>> recipient, or the employee or agent responsible for delivery of the message >>>> to the intended recipient, you are hereby notified that any dissemination, >>>> distribution or copying of this communication is prohibited. If you have >>>> received this e-mail in error, please notify us immediately by telephone at >>>> (303) 565-7001 and also indicate the sender's name. Thank you. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>
