Docs:

• Camel Quarkus timer
• Camel 3 timer

Camel Quarkus ENG Component Planning Document

• document maps the progress of porting the Camel 3 components, dataformats, languages, EIP (TBD), others into Camel Quarkus runtime - JVM and Native mode

Definition of done:

• identify and fill the high-level features/use cases (even the ones it brings via transitive dependency on Camel 3 or Quarkus)
• identify transitive dependencies on quarkus extensions and make sure it is supported on upcoming Quarkus release
• identify if the use cases/features are present in quickstarts/camel-quarkus-examples
• identify the test coverage of the high-level features in integration-test or the quickstarts
• PM/ENG/QE agree on if everything of the features is supported in the product
• review if the tests contains test for each high level feature of the component

Other Topics to consider for future

• Camel-K uses different OCP resources when from(timer/quartz) is used -> CronJob
• Currently, Camel Quarkus relies on Quarkus for deploying and they support to deploy as regular OCP `Deployment` or a KNative `Service`. No magic.

QE:

• considering it done for TP1 and JVM only

ENG:

• ppalaga: done for TP1 and JVM