Discrepancies in Fuse EAP container image

1. Fuse EAP image registry.redhat.io/fuse7/fuse-eap-openshift:1.8 has WILDFLY_CAMEL_VERSION as 5.6.0.fuse-780027-redhat-00001 which is not available in any of the Red Hat public GA maven repositories[1][2].

If there are any earlyaccess images, they should be tagged as such. Currently, all the images are tagged as Generally Available.

This will help the users select the correct bom version in their pom.xml.

2. Also, patched images should be tagged as such and the patch information (such as updated components and their versions) should be available with them.

3. The dockerfile sometimes doesn't show the correct EAP version. For example, the 1.6 dockerfile says it is running EAP 7.2.1 and when we inspect the image the version is different :

$ docker image inspect registry.redhat.io/fuse7/fuse-eap-openshift:1.6  | grep "JBOSS_EAP_VERSION"
                "JBOSS_EAP_VERSION=7.2.8.GA",

4. Looks like the build date of the OpenShift Fuse EAP image is before the "Official Release date" of Fuse (EAP) itself?

Release date of Red Hat Fuse 7.8.0 on EAP Installer = 12/16/2020 12:03 PM EDT
Build date of EAP OpenShift image = "2020-12-01T12:59:44.241750"

Can we have the container image available around the same time or after the official Fuse on EAP release?

5. Is it possible to include the shipped fuse version in the container image tag. Right now there is not much correlation between them.

E.G. registry.redhat.io/fuse7/fuse-eap-openshift:fuse-eap-openshift:1-9-fuse7.8.0-patch-1

6. Do we release a new fuse eap bom in case dependencies change due to patches? For every release, it should tell what exact dependencies that image holds (BOM) and where to find them.

[1] https://catalog.redhat.com/software/containers/fuse7/fuse-eap-openshift/5aba4fc629373834f089f07c?container-tabs=dockerfile
[2] https://maven.repository.redhat.com/ga/org/wildfly/camel/wildfly-camel-bom/