We should, as tech-preview
We should start getting them built and tested by CI starting from master
The project artifacts are containers, no RPMs at all. The job above build and push containers to
quay.io/rgolangh .
If there is no official registry namespace for ovirt yet, now its the time to create it.
No, I just bumped the tag for next release :) but github is probably announcing a new release when a tag is pushed.
So, just to be sure, we are not going to release any artifact built from ovirt-openshift-extensions in 4.3 right?
Hi,
Are we missing a release of ovirt-openshift-extensions?
It wasn't included in 4.3.2 RC2
Thanks,
--
--
--