Roadmap 25.05
Jump to navigation
Jump to search
What's new?
- Deadlines for this cycle are set and published below.
- We will try to have 3 sprints by 3 weeks each where we focus on a community chosen and driven project.
Learn more below.
What do I need to do?
Right now:
- Help any of the open bugs and patches along for release 25.05!
- Make sure your own work is ready and applies.
- Help writing release notes!
Deadline: Development IRC meeting 8 January 2025
Release Schedule
These are the dates for this cycle.
Start | End | Weeks | Event |
---|---|---|---|
2024-12-30 | 2025-01-17 | 3 | QA Sprint |
2025-01-20 | 2025-02-07 | 3 | Community Sprint 1: Tidy the whole codebase |
2025-02-10 | 2025-02-28 | 3 | Community Sprint 2: Refactor modal logic |
2025-03-03 | 2025-03-21 | 3 | Community Sprint 3: Move the REST API to OpenAPI v3 |
2025-03-31 | 2025-04-04 | 1 | Hackfest, Marseille |
2025-04-29 | (3) | Soft feature freeze | |
2025-05-13 | (2) | Hard feature freeze and string warning | |
2025-05-21 | (1) | Hard bug freeze and string freeze | |
2025-05-27 | - | 25.05 Release Day |
- Soft feature freeze: Nothing big or with a high risk of side-effects will be pushed after this date. Everything currently in Passed QA will be reviewed for this release. Please pay attention to your bugs for questions or follow-up work that might be required.
- Hard feature freeze: Nothing categorized as 'enhancement' or 'new feature' will be pushed after this date if not already marked as Passed QA. If you haven't written up nice release notes for your features and enhancements yet, now is the time!
- Hard bug freeze: Only bug fixes considered major, critical or blocker will be pushed after this date!
- String warning/freeze: Since our move to Weblate as translation platform strings are continuously updated, so translators can start translations at any time. But we will try to be done with all heavy string changes by the 'String warning' date and not to change any strings after 'String freeze'.
Community sprint projects
We will have 2 phases: sprint project proposals, sprint project election. Depending on the tight time frame and responses, we might only select the first sprint project on the first meeting and the others the one after.
We will have a first discussion and probably pick at least the first sprint project at the Development IRC meeting 8 January 2025
Status | Project | Bug/Link | Project Lead | Supporters |
---|---|---|---|---|
Sprint 1 | Tidy the whole codebase | 38664 | Jonathan Druart | Katrin Fischer
Owen Leonard |
Sprint 2 | Refactor modal logic in returns.tt / returns.pl | 38842 | Emily Lamancusa | Katrin Fischer |
Sprint 3 | Move the REST API to OpenAPI v3 | 35613 | Tomás Cohen Arazi | Katrin Fischer |
- A sprint project should be something big that needs focus from a group of people. It might require extensive changes to codebase or even a freeze of the main branch for a certain amount of time. This could be architecture changes, big template updates, etc.
- Please only add yourself as supporter if you will have time to contribute to these projects in some way.
- Please include enough information that it's clear for anyone outside of your project, what is is about.
Other development projects
Having the idea of sprints and sprint projects doesn't mean that we won't have any other new features, enhancements and beware: bug fixes. Feel free to advertise for any development projects aimed for this cycle in this area.
Status | Project | Bug/Link | Project Lead | Supporters |
---|---|---|---|---|
Planned | Security Things | David Cook | ||
Planned | Wiki cleanup | Jonathan Druart | Thomas Dukleth | |
Planned | Test::NoWarnings | Bug 25515 | Jonathan Druart | |
Planned | Auth - Store session id in userenv | Bug 37041 | Jonathan Druart | |
Planned | KohaTables improvements (code cleaning) | Blockers of Bug 36640 | Jonathan Druart | |
Signed Off | Allow LocalHoldsPriority to fill by hierarchical groups | Bug 20747 | Lisette Scheer | |
Planned | VueJS architecture rethink | Bug 38201 | Pedro Amorim | Matt Blenkinsop |
- Please only add yourself as supporter if you will have time to contribute to these projects in some way.
- Please include enough information that it's clear for anyone outside of your project, what is is about.