We’re planning to release Bahmni 0.89 in April, and we want to use TRUNK-425 to speed up our patient searches by leveraging Lucene. (Thanks @raff for shepherding this, and @adamg for doing a lot of the work!)
Therefore we would like to release Platform 2.1 sometime in March.
Historically the Platform has been released once a year, but we’ve been having discussions since the Singapore meeting about allowing motivated organizations to do more frequent releases, but perhaps to treat them as “non-LTS” releases or something like that. The Bahmni team is ready to be the guinea pigs for doing this the first time.
My request to others in the community is to help us do this. Particularly, please help us understand what expectations you have for having us do this mid-cycle release.
- I expect that we’ll have a much shorter cycle of public UAT than for our “main” annual releases, but the Bahmni QA team will do a lot of testing via the Bahmni workflows.
- I expect that the will not drop Platform 1.11 from the list of supported versions until Platform 2.2 gets released at the end of the year.
- Otherwise I expect nobody is especially concerned about this “early” release, as long as our team puts in the effort to do it. (Though it will slightly increase the burden on folks who are merging PRs and backporting code, because now they’ll have to backport to 2.1.x, 2.0.x, 1.12.x, and 1.11.x, instead of the historical 3 release lines.)
Thoughts? Concerns? Encouragement?
(Also, does anyone have any work-in-progress I should be tracking, that they’d really like to get into an April release instead of an end-of-year release?)