commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: Is there an missing bit in the instructions for making a release?
Date Fri, 15 Apr 2016 16:59:06 GMT
On Fri, Apr 15, 2016 at 12:57 PM James Carman <james@carmanconsulting.com>
wrote:

> On Fri, Apr 15, 2016 at 12:53 PM sebb <sebbaz@gmail.com> wrote:
>
>> That is effectively what the final release tag is.
>> We vote on the RC tag, and create the release tag from the successful RC
>> tag.
>>
>>
> Yep, we're not far off.  What I'm proposing is that we try to use the
> Maven Release Plugin to create our releases and push them to a staging
> repository in Nexus for a vote.  If the vote fails, drop the staging repo.
> If we truly want immutable tags, then maybe we just create the release with
> a tag of "foo-1.2.3-rc1" (as someone has pointed out, the release plugin
> can do) and then once (or if) it passes, copy it to "releases/foo-1.2.3".
> I must admit, I haven't RM'd a release in a while, mainly because I found
> it to be extremely painful.  Anything we can do to make that process easier
> could only help us release more often.  Obviously we can't sacrifice
> traceability of the code, but I think we can find a workable solution.
>

Again, we can just stick to the regular process and just "burn" version
numbers for votes that don't pass.  Versions != releases.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message