You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "David Jencks (Jira)" <ji...@apache.org> on 2021/11/18 19:40:00 UTC
[jira] [Created] (CAMEL-17208) Website release process documentation correction
David Jencks created CAMEL-17208:
------------------------------------
Summary: Website release process documentation correction
Key: CAMEL-17208
URL: https://issues.apache.org/jira/browse/CAMEL-17208
Project: Camel
Issue Type: Bug
Components: documentation
Reporter: David Jencks
Assignee: David Jencks
The network of subproject version dependencies is more complicated than we previously accounted for in the website release docs. We've recently seen that:
- camel-quarkus 2.4.x depends on camel components 3.12.x, so 3.12.x needs to remain in the docs as long as cq 2.4.x
- camel-k 1.7.x depends on camel-quarkus 2.4.x, so cq 2.4.x and camel 3.12.x need to remain in the docs as long as camel-k 1.7.x
I imagine there are a lot more subproject interdependencies that have not yet been discovered or even properly set up. It would be great to have
- each subproject clearly document which other subprojects it depends on with the versions of these other subprojects, as I've suggested in https://github.com/apache/camel-k/issues/2759.
- a centralized view of all such dependencies.
However, we should at least document that these dependencies generally exist and that removing any version from the documentation needs to check that no other subprojects are referencing it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)