Release 2.5.1

[squakez]

We have identified and fixed a few regressions which requires the release of a patch version. However, I advocate to wait the release of Camel core 4.8.2 and related runtimes in order to default to this version which has also fixed a series of bugs.

[squakez]

@hernanDatgDev I know you were interested in this. I don't have an ETA when Camel core would be releasing the next patch for 4.8.x. We can wait the beginning of next month to understand that and decide if it makes sense to start a release or wait accordingly. WDYT?

[hernanDatgDev]

Hey @squakez, I'm okay with waiting until the new month for an update from the core camel team. At that point if there's no ETA or it's too far out, I believe my team agrees that going with 2.5.1 is okay for now. We can always wait for another release (like 2.5.2) since we're not technically using the "contract first" rest DSL yet.

[squakez]

Camel 4.8.2 core is under voting process. Once this is over we can wait to have the Camel Quarkus release and finally we can start to do the release for Camel K Runtime to align all those dependencies. With that over we can release Camel K version 2.5.1, I guess by mid of December if there are no problems during the release train.

[squakez]

Hello. It seems that the Quarkus should align the release to Camel core 4.8.2 by mid January. We can do a patch release including the fixes on the operator side only if we are good with that. I will start the process during this week.