[GitHub] [camel-quarkus] djencks edited a comment on pull request #3299: Upgrade Camel to 3.13.0

[GitBox <gi...@apache.org>]

djencks edited a comment on pull request #3299:
URL: https://github.com/apache/camel-quarkus/pull/3299#issuecomment-970553321


   I still don't understand the nature of the working relationship between cq code and main camel code: if there is one, I'd expect changing the camel version referred to by cq 2.4.x would not be appropriate, even just for the documentation.
   
   Camel-quarkus 2.4.x docs refer to the camel 3.12.x documentation. 3.12.x is not LTS, so it's about to disappear from the website without a change in policy.  Do you want to drop cq 2.4.x from the website also?
   
   A couple months ago this didn't show up as a problem because the released cq docs branch was totally broken, not showing any extensions at all.  Apparently only I noticed...
   
   I can think of a couple of changed policies that might work...
   
   1. Release cq branches use the latest LTS camel branch. The main camel LTS branch is likely to stick around longer than the cq branch.  This might give an opportunity to have LTS cq branches as well, I don't know if that's desirable.
   2. We keep all the non-LTS branches referred to by subprojects around as long as they are referred to.  This would mean that, instead of dropping 3.12.x later this week, we keep it at least until the next cq release, which will depend on 3.13.x.
   3. Actually release an e.g. 2.4.1 depending on camel 3.13.


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org