Starting this thread as I didn’t see another option; LMK if I should post elsewhere.
Update provided to the PM Team this Monday: The platform 2.4 release is no longer blocked by needing to address the standalone build but this will be addressed in a subsequent minor version update. This means that this week @gcliff will put together the alpha for other implementers/volunteers to test.
@gcliff presented to the TAC last week that in addition to the existing tests running alongside the builds, the primary method of testing at the moment has been this suite of manual API queries:
or REST-WS module we are using this google sheet(https://docs.google.com/spreadsheets/d/1vrVYIjVZqxzS2FHmD63KGV2wqvpJN-x-k77atS6TtIM/edit#gid=0 ) to log testing activities. Later, data from the sheet will be used to develop an automated rest endpoint testing system and we will deprecate the manual testing of rest endpoints for future releases. We are only proceeding with the manual testing due to time constraints and absence of an established end to end rest-endpoint testing system for platform releases. Anything to add to that @gcliff?
Tracking Remaining Tasks
@gcliff can you just confirm - is this the list or search query you’re using in Jira to track the remaining work, or is there another place in Jira you’re using? https://issues.openmrs.org/browse/TRUNK-5970?filter=22950
The guidance from the TAC call was as follows:
- Make sure RefApp 2.11 starts & runs on platform 2.4 - @gcliff, who is owning this?
- QA environment running platform 2.4 that people can try the RefApp against - @gcliff this is what you’re working to get ready this week, right?
Testing that different setup workflows work
- MariaDB and mySQL tests have errors - suggests possible issue with platform standing up against plain mySQL server; could block docker
Check that Implementers’ Distributions run with platform 2.4:
- PIH to try to update their snapshot to run on platform 2.4 - matter of finding time if it doesn’t start (@mogoodrich can you post your findings here if/when you manage to do this? )
Thanks all, and huge kudos to Cliff for continuing to move this important work forward.