Plase don't let us reinvent the wheel.
3.1.0-SNAPSHOT would be simply wrong, as 3.1.0 is already released. So it should be 3.1.1-SNAPSHOT.
Omitting master would be confusing, as every newcomer assumes there is a master and it is the way towards the next major release.
IMHO the best we could do is merge release-4.0 into master and in turn drop release-4.0 branch.
-Markus
Von: James Perkins [mailto:jperkins@xxxxxxxxxx]
Gesendet: Donnerstag, 24. August 2023 16:27
An: Jakarta Rest project developer discussions
Cc: Markus Karg
Betreff: Re: [rest-dev] [External] : Removing outdated branches
Along these lines, the master branch seems in an odd state to me. The version is set to 3.1.0 which is really not great if you build it locally as it pollutes your local Maven repository. Especially if it does include new features. At minimum, IMO, the version should be set to 3.1.0-SNAPSHOT. It should likely be changed to something else, but SNAPSHOT is critical.
Should we just remove the master branch and use the release-$version branches?
I have removed all branches on Github other than master, release-4.0, release-3.1.x and gh-pages.
-Markus
Von: Santiago Pericasgeertsen [mailto:santiago.pericasgeertsen@xxxxxxxxxx]
Gesendet: Donnerstag, 24. August 2023 15:14
An: Markus Karg
Cc: Jakarta Rest project developer discussions
Betreff: Re: [External] : [rest-dev] Removing outdated branches
Markus,
I noticed that we piled up several outdated branches.
If nobody objects, I'd like to remove all of them but just keep the following:
I was thinking about this yesterday, so no objections. Did you check how master and release-3.1.x differ BTW?
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
--