tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Gribov <gros...@gmail.com>
Subject Re: Release process git tag
Date Tue, 30 May 2017 13:21:35 GMT
At least checkout 1.15-rc2 and tag it with 1.15.

I guess, 1.15-rc2 could be deleted afterwards. Or it could be left. I have
small preference for removing it since it gives more noise in `git tag`
output.

On Tue, May 30, 2017 at 4:12 PM Allison, Timothy B. <tallison@mitre.org>
wrote:

> All,
>   In the release process directions, I see this:
>
>
> 5. git clone https://github.com/apache/tika.git X.Y-rcN
>
> 6.  git tag X.Y && git push --tags
>   These directions appear to clone trunk and then tag _it_ as 1.15, which
> can't be right.  Changes might have been made since I cut rc2, and the
> versions in trunk now are 1.16-SNAPSHOT, etc.
>
>   What should I actually do?
>
> Some options:
>
> 1)      leave the 1.15-rc2 tag as it is and stop
>
> 2)      Add a 1.15 tag to the same commit as 1.15-rc2
>
> 3)      Add a 1.15 tag to the same commit as 1.15-rc2 and delete the
> 1.15-rc2 tag
>
> Thank you!
>
>          Best,
>
>                  Tim
>
> Timothy B. Allison, Ph.D.
> Principal Artificial Intelligence Engineer
> Group Lead
> K83E/Human Language Technology
> The MITRE Corporation
> 7515 Colshire Drive, McLean, VA  22102
> 703-983-2473 <(703)%20983-2473> (phone); 703-983-1379 <(703)%20983-1379>
> (fax)
>
> --

Best regards,
Konstantin Gribov

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