Heads-up, I'm using "Affects Version/s:" to indicate a known issue we intend to fix in/for a particular release.
#fineract 2025-12-19
see the 1.14.0 release note to understand what I mean
see that "Known issues" list? That's built based on which issues have `affectedVersion = 1.14.0`. If we were trying to be literal/pedantic, we might set the affected version for every open issue to every previous release. Instead, maybe we can use it the way I'm proposing: To indicate a known issue that an admin/user might have to do something about (e.g. implement a workaround themselves).
Otherwise, why would we bother admins/users with our in-progress work? We have 425 unresolved issues, see `project = FINERACT AND status not in (Resolved, Closed) AND (affectedVersion <= 1.14.0 OR affectedVersion is EMPTY)`
Feedback welcome, as always. Please let me know if this makes sense and if you're +1 / -1. I should also send this to the dev list soon for posterity.
To keep the "Known issues" list brief and useful on the 1.14.0 release note wiki page, I unset `affectedVersion` for FINERACT-2392, FINERACT-2404, FINERACT-2422, and FINERACT-2423.
Hmm, perhaps we are already doing what I'm proposing. A couple examples were tickets that didn't make it into 1.13.0 and we were thinking of releasing in a 1.13.1 patch release (we didn't end up making that patch release though): FINERACT-2390, FINERACT-2396.
w00t, voting underway! https://release-test.apache.org/vote/fineract/1.14.0 :racing_car:
who's going to be the first person to vote using this fancy new system? 🙂
@Terence thx for bug report! ASF is looking into it. I can get the page but can't download with curl. Will you try rsync?
https://the-asf.slack.com/archives/C049WADAAQG/p1766246169337129
https://the-asf.slack.com/archives/C049WADAAQG/p1766246169337129
ATR is working now (and we don't need it):
https://lists.apache.org/thread/rxmqbpk623cypt9rggzj06jnwg87blk0
https://lists.apache.org/thread/rxmqbpk623cypt9rggzj06jnwg87blk0