Agreed. 1.10.1. I’ll try to get to those tasks tomorrow and then call for a vote on Monday.
If I can finish that up, and If a few people are able to do the build and confirm, then we can close the vote by Thursday w final ceremonies on Friday before the holiday week in the US. If not, we’ll have an extended voting period and the release will hopefully happen Dec 29-Jan 3rd. On Sat, Dec 14, 2024 at 9:16 AM Adam Monsen <amon...@mifos.org> wrote: > I suggest we use *1.10.1* for the release version number and use the > extant, signed, and valid build artifacts sitting in > https://dist.apache.org/repos/dist/dev/fineract/1.10.1/ . They include > changes in 227bdf6e > <https://github.com/apache/fineract/commit/227bdf6e4f0d271e19193fe6f9d59f36720a772a> > that were done to work around a problem building the documentation. I'm > concerned if we try to go back and re-build 1.10.1 we'll have to do some or > all of that over again, and it seems more important to just have the public > line in the sand as far as when the release happened, it's immortal > identifier (1.10.1), known/working build artifacts, and (perhaps most > importantly) the release notes. We'll get plenty of practice on future > releases and if any code/infra changes are needed it'd be better to be > working on all that near HEAD / tip of develop. > > I suggest deleting the 1.10 release on GitHub and creating a 1.10.1 > release, listing all PRs from "1.9.0" to "1.10.1". > > I suggest renaming the release notes wiki page > <https://cwiki.apache.org/confluence/display/FINERACT/1.10.0+-+Apache+Fineract> > to 1.10.1. > > Thoughts? >
