Set main version to 999-SNAPSHOT

[cescoffier]

No description provided.

[gsmet]

Do we really want to do that?

I mean in all the projects I know, we push the next version as a SNAPSHOT. Couldn't it be part of the release process to set the next version?

[cescoffier]

It's actually very tricky as conflicts may happen if something touches the pom.xml while the release process is in progress.

Yes the conflict can be managed if the release is cut manually, but we want a fully automated release process, and in this case, it can be tricky.

[gsmet]

For Hibernate projects, we have a fully automated process, it just takes the next version as input.

Frankly, this 999-SNAPSHOT is ugly and I don't think it's a good idea.

[cescoffier]

How do you deal with conflicts?

[cescoffier]

it's actually the mechanism we are using right now.

[dmlloyd]

The rationale is that "999-SNAPSHOT" is better than "1.0.0.Alpha1-SNAPSHOT" especially in light of the fact that we'll never release a "1.0.0.Alpha1". We don't want to bother updating master every time there is a new tag, and we especially don't want to start doing so only after we've passed "1.0.0" because that's just silly.

[gsmet]

This is automatically done via the Maven release plugin. The only issue I see would be with the Quickstarts but it could be easily scripted as we just have to change the quarkus.version.

I mean all the other Open Source projects I know are not doing that, it really is a bad practice IMHO.

[dmlloyd]

Updating the head version after every release? Yes that's a bad practice because it creates merge conflicts pointlessly.

[cescoffier]

PR: #1256