Use next instead of pre-release display label

[davsclaus]

We have latest / pre-release today as indicator for the next version.

If we use pre-release then we have to keep updating the version, and the display is long.
Instead we can just use next which is what we mean. The next upcoming version.

[djencks]

I like the idea of changing the display-version to include "next" rather than a concrete version, and I think it would also make sense to change the version to next, so that will show up in URLs. Doing this may also detect anything still linking to "latest" :-)

Although "next" has some implications of "prerelease", I think it is a bad idea to leave out the (prerelease) without doing anything else. Antora calculates the latest version as "latest version that isn't a prerelease". Therefore, in xrefs from other components, if we leave out the version, it will link to the last released version. Including the "(prerelease)" in the display version will make it clear to those familiar with Antora that this version will not be linked to.

Alternatively perhaps we could add an attribute in the component descriptor

prerelease: WARNING: This version is not yet released and should not be used in production

and at the top of every page

{prerelease}

and when we branch set the attribute to blank so this warning doesn't appear

[djencks]

I'd like to implement this soon, over all camel subprojects:

• change version from latest to next
• mark next prerelease
• set display_version to Next or Next (Prerelease)

I've decided I slightly prefer Next (Prerelease) but if that seems to long to others I'm fine with just Next

I expect this will flush out a lot of incorrect xrefs that use the latest version name.

[djencks]

Changing the version to 'next' is going to affect .htaccess, we'll need to redirect from /latest/ to /next/.
Did the old website have only the equivalent of today's 'latest, prerelease' version? I'm not very comfortable directing people by default to the prerelease version, but I suppose if that is what they were viewing on the old website it's OK.

[djencks]

As part of this I plan to make the manual into an unversioned component, which will remove the 'latest' version segment from the urls. This also will need a rewrite rule in .htaccess.

[djencks]

PRs for this:
#654

camel:

• [new branch] main-latest-to-next -> main-latest-to-next change 'latest' to 'next', and make manual unversioned camel#6336
• [new branch] camel-3.12.x-latest-to-next -> camel-3.12.x-latest-to-next Camel 3.12.x latest to next camel#6337
• [new branch] camel-3.11.x-latest-to-next -> camel-3.11.x-latest-to-next camel 3.11.x latest to next camel#6338
• [new branch] camel-2.x-latest-to-next -> camel-2.x-latest-to-next camel 2.x latest to next camel#6339

camel-spring-boot
main-latest-to-next apache/camel-spring-boot#397

camel-quarkus

• [new branch] main-latest-to-next -> main-latest-to-next camel quarkus main latest to next camel-quarkus#3232
• [new branch] 2.4.x-latest-to-next -> 2.4.x-latest-to-next camel quarkus 2.4.x latest to next camel-quarkus#3233

camel-karaf

• [new branch] main-latest-to-next -> main-latest-to-next camel karaf main change latest to next version camel-karaf#93

camel-kafka-connector

• [new branch] main-latest-to-next -> main-latest-to-next camel kafka connector main latest to next camel-kafka-connector#1275
• [new branch] camel-kafka-connector-0.11.x-latest-to-next -> camel-kafka-connector-0.11.x-latest-to-next camel kafka connector 0.11.x latest to next camel-kafka-connector#1276

camel-k

• [new branch] main-latest-to-next -> main-latest-to-next camel k main latest to next camel-k#2716
• [new branch] release-1.6.x-latest-to-next -> release-1.6.x-latest-to-next camel-k 1.6.x latest to next camel-k#2717

camel-k-runtime

• [new branch] main-latest-to-next -> main-latest-to-next camel-k-runtime main latest to next camel-k-runtime#747
• [new branch] release-1.9.x-latest-to-next -> release-1.9.x-latest-to-next camel-k-runtime 1.9.x latest to next camel-k-runtime#748

camel-kamelets

• [new branch] main-latest-to-next -> main-latest-to-next camel-kamelets Main latest to next camel-kamelets#552

[davsclaus]

Did you forget Camel 3.7.x LTS branch from the core camel project?

[djencks]

I had already fixed the problems there :-)
I think we can close this now.