Andrea Peruffo

I'm not an expert, but, using tags and branches we should be able to provide e.g. a `3.X` ( as `branch` name) and `3.0.1` (as `tag` name) version.

Rolling forward is a possibility, using branch names another. Yup, it would need a little bit of work to connect the dots, but looks pretty much feasible.

> So I don't know, it might be a bug in JOSDK? Would you be up doing a pairing session on this? This PR should go in anyhow I guess...

I attempted to migrate this plugin to Maven 4 [here](https://github.com/mojohaus/flatten-maven-plugin/compare/master...andreaTP:flatten-maven-plugin:maven-4) but I'm having troubles with DI and I don't really know how to fix it. Maybe @gnodet can help here...

> This specific problem has been fixed in Maven 4 master already. It will be part of rc-3. Tested and I can confirm, the problem is fixed in `master`, thanks...

Now that we are at it: https://www.oracle.com/java/technologies/java-se-support-roadmap.html Java 11 is almost out of the support phase, would it make sense to bump directly to Java 17?

I do agree with this analysis, but the proposed resolution is probably going to make things more inconsistent. Let me try to explain: - upload some yaml content - the...

cc. @jponge @cescoffier While working on this prototype, we are encountering(and solving) various challenges and trade-offs. By applying it in Apicurio Registry, we can be confident that any bugs or...

In the spirit of "self serving" I went ahead and created [this PR](https://github.com/quarkiverse/quarkiverse-devops/pull/355), let me know!

> I'd like to avoid a "known acronyms list" Completely agreed. I think that the examples are completely decidable with an algorithm and without heuristics: `externalID` -> trailing uppercase characters...