Looks like the first line of technical hurdles is cleared to get to inventory of all that is needed for an 1.0.0 alpha release of Ozone. A big chunk of the remaining effort is about releasing O3 alpha itself, see:
@achachiez to test two Ozone distro and Docker pending items, and then do PRs for them and we should be good to go 
Elsewhere:
RA-1993: @ruhanga raised a PR, @ibacher to review:
@reagan is reviewing a PR for Ozone FOSS’ data extract reports:
Previous updates:
From here on Slack.
A bit of stalling on Ozone distro and Docker related tasks. Even though @achachiez made some progress already until yesterday, he is now stuck on internal projects until tomorrow (Thu).
The objective is to have Ozone Pro as of now up on the dev server by Monday.
@ruhanga to oversee the practical release of Ref App 3.0.0, starting with the backend, through being assigned RA-1994 (Release of Distro Ref App 3.0.0 (alpha)).
Elsewhere:
Ozone FOSS data extract reports now properly generated, @reagan to test that they can be imported easily into Superset.
These updates are very very helpful Dimitri!! Please keep this up
@achachiez got us Ozone (Pro) on the dev server again It’s been a while.
He reported small issues with SSO (so only affecting the Pro version), namely:
Emmanuel will keep fixing the above and @mksrom and him will work the way to have this perfectly hooked to all necessary CI/CD processes.
This is a huge step now, it’s back online somewhere (here actually, use jdoe/Admin123) 
Elsewhere:
⇒ QA QA QA, with starting to dive into automated QA 
Nice!! Would this be mostly for the non-O3 component products?
FWIW for O3: we have a few things going on re. QA automation for you to be aware of.
Yes, QA is primarily focused on what makes Ozone what it is, therefore all aspects that touch the integration between the components.
But of course this will often spill to validating that the components themselves behave how they should, and that’s mostly O3 (since the other components are very stable).
A good example of this spilling is the following.
While testing Ozone Analytics, we realised that there was no allergies in our flattened datasets, that simply came from the fact that the form to record allergies is broken in O3.
We have an issue with Debezium that intermittently stops working after a short while, this is what @achachiez is focusing on right now. This is a little nasty as it seems to not happen locally but does happen once deployed on AWS.
Unfortunately this is slowing down most of our QA process, since the whole integration layer can’t be tested, at least online.
(Ozone Pro) Otherwise Emmanuel had fixed all HTTPS-related issues that we had behind the proxy, as well as the issue with Odoo not loading its OIDC settings. All good there now.
Elsewhere (still roughly the same):
@ruhanga cleared the last large issue that we had with the EIP layer under SSO here:
kudos for that one
The QA process has actively resumed between @enochb and @nuhuhmutebi and we are gathering feedback as it goes. A configuration issue has been identified in regards to the ERP integration, Nuhuh is defining the issue fully before attempting to address it.
Elsewhere:
service-account-eip’ user automatically.(Ozone Pro only) We uncovered an issue with the TTL of OAuth tokens, this was temporarily fixed by @achachiez by setting a long TTL in Keycloak, but otherwise this ticket should be used to fix the issue:
Otherwise we are still going through the inventory of all that it takes to release Ozone, and there is a bunch of things on top of what is needed to release O3 Ref App, among others:
Elsewhere:
(Ozone Pro only) Not a blocker for the alpha release (but it is a blocker for the beta) but we see intermittent issues with having two concurrent instances of Debezium consuming OpenMRS’s MySQL bin log. @achachiez is on it with two scenarios at hand:
Elsewhere:
The team at Mekom keeps on with QA-ing Ozone. An issue has been found with a misalignment between OCL concepts defining the dispensing and dosing units and Odoo configuration for the UoM, @nuhuhmutebi is looking into it.
Elsewhere:
A lot was done over the past 10 days in advancing the alpha release process of Ozone. We have released almost all Ozone-specific artefacts (that are not O3 artefacts):
A couple are still pending that will be released in the next couple of days:
After that the release process of Ozone will only hinge on that of O3, @ibacher @grace @raff → 
. Specifically the frontend release of O3 (since the backend release is ready to go). So readers should rather follow:
Elsewhere:
A post was split to a new topic: Ozone - Credentials not working
A post was split to a new topic: 
Ozone 1.0.0-alpha.1 Released