apache / apache/camel-quarkus

Compatibility matrix: Should the content be improved ?

Open
#4,398 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
302
Forks
232
Avg merge
1d 20h
Merged PRs (30d)
114

Description

There was a discussion [upstream](https://camel.zulipchat.com/#narrow/stream/257302-camel-quarkus/topic/camel-quarkus.202.2E14.2Ex.20and.20camel.203.2E18.2E2) with possible improvement to the compatibility matrix.

Should the matrix point to branch, like
`2.13.x | 3.18.x | 2.13.x | 22.3.x |   | 2.13.x ...` instead of
`2.13.x | 3.18.3 | 2.13.5.Final | 22.3.0 |   | 2.13.x`

Also some versions looks wrong. camel-quarkus `2.15.x` is said to be compatible with camel `3.18.2`.
Should it be declared to be compatible with camel `3.19.x` instead ?

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the compatibility matrix in the camel-quarkus repository and read the upstream Zulip discussion linked in the issue. Compare the matrix's current Camel Quarkus, Camel, and Quarkus version entries with the proposed branch-based format and the 2.15.x compatibility example; done means the intended changes and corrected versions are agreed and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.