7 Commits

Include renames

Author	SHA1	Message	Date
Adam Monsen	97aa931a59	save 1.12.1 vote result	2025-07-27 15:39:29 -07:00
Adam Monsen	c5275cbd34	FINERACT-2306: release doc fixes ... * docs: link directly to FINERACT-873 and shorten it for brevity / clarity * fineract plugin: * print email, don't send (WIP, but I might keep this... I prefer manually sending emails for now.) * support different release date and release branch date I originally modified EmailService (disabling the actual email sending by just commenting it out) but I reverted that change per discussion with Ádám Sághy. You won't see this in the squashed final commit so I'm mentioning it here for posterity. Ádám wrote: > Is there a reason to remove the email sending? I replied: > Great question. I did think about this for a bit. I should have been more transparent about my intent. Allow me to explain. > > For the 1.12.0 release process I used the groovy code to generate email templates, but I wanted to edit the emails before sending so I disabled this line, and intentionally left it so, figuring I'd be the one using and [hopefully minimally] maintaining it for now. > > The Fineract (release) plugin appears to be more or less unmaintained for about 2 1/2 years now (save the semiautomated dependency updates). Looking at the code and history, I assumed I was the only one that would be using it now and in the near future. It also struck me how most everything it does is primarily to work around antiquated Apache release process steps that are not necessarily what we want for Fineract. Personally I think the Fineract release plugin should be simply replaced by a better release process. > > I think I'll add a comment there, and of course I welcome your feedback. > > Anyway yeah, my intent here was simply to do the simplest, safest, and most useful change here so I could keep this release plugin limping along until we improve the release process itself. No disrespect to @vidakovic and @vorburger and whomever else poured love into this code over the years. Perhaps the options for releasing Apache code have improved since then? > > Today we can of course do better (e.g. just let GitHub help us release with far fewer clicks/steps). > > Also I am not proposing we change the release process today or even soon. Maybe in a quarter or two I'll propose changes, if/when there seems to be political will around that. Ádám replied: > hmm... i am not particularly mind if you are reworking the release process, but i think having a "send" step which was meant to sending a mail but now the actual sending got commented out is misleading, no? I replied: > Yep, you're right. I think I'll just back out this change because I agree with you it's bad to just leave the send() call commented out without any other changes.	2025-05-30 09:12:44 -07:00
Adam MonsenandAdam Saghy	efabd341df	FINERACT-2231: remove links unhelpful in future releases ... The Fineract dev list thread links were specific to the 1.11.0 release. It wouldn't make sense to include them in future [VOTE] emails.	2025-04-07 12:56:54 +02:00
Adam MonsenandAdam Saghy	3f2079566c	FINERACT-2219: capture v1.11.0 lessons learned in asciidoc and fineract release plugin ... * don't bother making MD5 files, they aren't necessary * step12 changed, stub it out and reference FINERACT-1817 for future improvements (looks like svn mv is not yet supported) * use latest vote message template, based on https://lists.apache.org/thread/cs5t0ho39ktg2jxr74dqd7fg9nyfcz3k * use more explicit form of `git push` to push release tag, see https://stackoverflow.com/questions/5195859/how-do-you-push-a-tag-to-a-remote-repository-using-git * use consistent language re: tarball, file, artifact, release candidate * fix some source listings that shouldn't be using macro expansion: this messes up URLs (hides scheme) * fix asciidoc link to FINERACT-1229 * clean up copyright years: use variable properly and remove unnecessary extra copyright in preface (it appears directly above, in the license) * de-indent URL in apache license -- this makes the link clickable in rendered HTML and PDF asciidoc outputs	2025-03-24 14:30:21 +01:00
Aleksandar VidakovicandAleksandar Vidakovic	478fb55b0f	FINERACT-2036: Fix code quality	2024-01-07 19:11:13 +01:00
Aleksandar Vidakovic	97bd1ecbe6	Fineract 1.8.0 release	2022-08-28 12:09:53 +02:00
Aleksandar VidakovicandAleksandar Vidakovic	40eb547a5c	FINERACT-1470: Fineract release plugin	2022-05-04 15:11:53 +02:00