djencks commented on pull request #3299: URL: https://github.com/apache/camel-quarkus/pull/3299#issuecomment-968107469
For the camel-quarkus main branch that seems fine to do since it isn't released so no one should be using it for anything but development. However, this seems like a problem for the released branch, currently 2.4.x, which I've proposed modifying in https://github.com/apache/camel-quarkus/pull/3298. Either the documentation is going to point to a different version than the software actually supports or you'll have to release a new camel-quarkus 2.4.x related to the new main camel version. Do you do that? Both of the following seem like reasonable strategies to me: - Don't ever update the related camel version (e.g. 3.12.x) of a release camel-quarkus version, and keep the referenced camel branch docs around until the camel-quarkus version is superseded and disappears. - Keep the related camel version docs around long enough for an update release of the released camel-quarkus, e.g. moving 2.4.x from 3.12 to 3.13. In any case, it's clear to me that dropping the old main camel docs needs to happen in a separate step from adding the new version, giving everyone time to catch up. I'll change the instructions PR and my playbook PR :-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
