Enforcing specific SNAPSHOT version on back branches?

[Guillaume Smet]

Hi,

For LTS releases, we update the version to X.Y.999-SNAPSHOT at some point in the release process (I'll be honest: usually, it's when QE complains about it :]).

For example, the version we have in Quarkus core for 3.20 is 3.20.999-SNAPSHOT.

We only do it for LTS releases - it's historical: it required more work and only LTS releases are here for a long time and making working with several branches a pain.

So the version we have in the 3.21 branch is 999-SNAPSHOT, same version as we have in the main branch.

However, with Jan, we were wondering if we should generalize (and automate!) that and adjust the version automatically when we branch meaning all back branches would have a X.Y.999-SNAPSHOT version.

We would also do it for the Platform.

WDYT? Should we go forward? Do you see any drawbacks?

--

Guillaume

[Max Rydahl Andersen]

+1 on doing it when branching.

Only "downside" is that you potentially have to build a bit more when swapping branches as the x.y.999 version wont be there
but the advantage is that you won't by accident mix up main with branched releases dependencies.

/max

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo87ApuhUGdWHnvY1vMqwts%2BMWc4X9BgRO43O3%2BhfeVnZA%40mail.gmail.com.

[Guillaume Smet]

On Thu, Apr 10, 2025 at 11:43 AM 'Max Rydahl Andersen' via Quarkus Development mailing list <quark...@googlegroups.com> wrote:

+1 on doing it when branching.

Only "downside" is that you potentially have to build a bit more when swapping branches as the x.y.999 version wont be there
but the advantage is that you won't by accident mix up main with branched releases dependencies

Well if you actually want to test X.Y.999-SNAPSHOT, you really need to build anyway so I don't think it will save you anything when swapping.

And as you said, you will avoid not testing the correct version.

Note that I haven't checked if it would be easy to do it, I'll have a look once things are settled :]

--

Guillaume

[Georgios Andrianakis]

+1

--

You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo-7E1aGNFC68H5nFUvAejO1BnFRud-o0JGJzmu%2B1fyZfQ%40mail.gmail.com.

[George Gastaldi]

+1 

--

You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo87ApuhUGdWHnvY1vMqwts%2BMWc4X9BgRO43O3%2BhfeVnZA%40mail.gmail.com.

[Alexey Loubyansky]

+1 definitely 

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAMmsnJiR%3D%3D%2B5Md%2BPOuT31jnXtHPhU7QVREHT%2Bwddq90zMZuNfg%40mail.gmail.com.

[Guillaume Smet]

Ah ah, you thought I forgot about this? Nope!

I'm experimenting with this in the 3.25 branch - and hopefully will make it fully automatic for our next 3.26 release.

-- 

Guillaume

[Foivos Zakkak]

Sounds great, thanks Guillaume.

--

You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo-NYohe75ZEd8akDF%2BTnwJrOPSFJV6zR7ybysurx1b0bg%40mail.gmail.com.

--

Foivos Zakkak
Software Engineer at Red Hat (Contractor)
7B4069D929BAAE91C0B3220A0846BFD103F04EA1