Skip to content

FINERACT-2448: standardize on release ready, improve releases section #5379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
meonkeys wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

FINERACT-2448: standardize on release ready, improve releases section #5379

meonkeys wants to merge 1 commit into from
+10 −4

Conversation

@meonkeys
Copy link
Contributor

@meonkeys meonkeys commented Jan 23, 2026

Description

FINERACT-2448

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per our guidelines
  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
  • Create/update unit or integration tests for verifying the changes made.
  • Follow our coding conventions.
  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
  • This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

@meonkeys
FINERACT-2448: standardize on release ready, improve releases section
02bbfc0 
I want us to standardize on being "release ready". That is, we agree to do our best to keep incomplete features off `develop` and to keep the build passing.

As part of this change I also want to update the [VERSIONS section in the README](https://github.com/apache/fineract/blob/d093a089c9c13051eb8922100e38e44a3933fd9c/README.md#versions) to more accurately reflect how we do releases today.
@IOhacker
Copy link
Contributor

IOhacker commented Jan 24, 2026

LGTM

Aman-Mittal
Aman-Mittal approved these changes Jan 25, 2026
View reviewed changes
Copy link
Contributor

@Aman-Mittal Aman-Mittal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@Aman-Mittal Aman-Mittal Aman-Mittal approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@meonkeys @IOhacker @Aman-Mittal