Publishing latest release
mkarg opened this issue · 9 comments
@cbeust Latest release is many months old, so I would kindly propose publishing the latest changest added by me and others. Thanks.
See also #534. Would like to help if I can as I've also been waiting more than 6 months for some fixes.
@cbeust Can you please share your ideas with us why not publishing the latest release? Is there a specific schedule we do not know of?
Hi Markus,
My only excuse is that I have a lot of things going on right now which have prevented me from releasing that new version. Will do my best to make this happen soon, but in the meantime, I'd love to explore how I can make you a release manager as well, so that you can release a new version of JCommander whenever you think makes sense.
How can we make this happen?
Cedric, I would feel honoured to become a realease manager. What we need for this is IMHO the following:
- Committer rights for my user on Github, as releasing implies creating branches and pushing release numbers
- I assume you release via OSSRH, so we need to create a ticket for OSSRH JIRA that asks to add my OSSRH user to press the release button for the group ID
com.beust(unfortunately JCommander is not usingcom.beust.jcommanderso you need to trust me more than essentially needed). - It would be nice if you could briefly sketch the technical commands you actually apply to release JCommander, as there are plenty of solutions we could perform this, but it makes sense if I do it the same way you did it so far.
- You should script some brief rules that outline a policy how you want me to manage the releases, so I am acting in the sense you intend it. For example, minimum time between release or list of tests to pass before releasing.
Thanks for the suggestions, Markus. Can you email me at cbeust@gmail.com? We can continue the discussion there.
For the impatient: Meanwhile I am in the role of a release manager, and I am currently preparing release 1.83 together with @cbeust. Stay tuned! :-)
I published the release some weeks ago on Maven Central, but note that the groupId changed to "org.jcommander"! :-)
@mkarg Thanks for doing this! I don't suppose you have access to publish a relocation pom under the old coordinates so that people will receive more-or-less automated notification that a new release has been published under new coordinates?