[
https://issues.apache.org/jira/browse/LUCENE-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182813#comment-17182813
]
Dawid Weiss commented on LUCENE-9474:
-------------------------------------
bq. allow for release manager to make a release: -Dversion.release=9.0.0 (in
the release manage's guide we never commit the version to SVN, we just set Tag.
My question is: why? I somehow fail to see why a release isn't made from a
particular commit (that would have the version number set correctly). It is
strange to me - this means the release's git commit would have a snapshot
version inside the code?
A release commit doesn't have to be automatically built - it would be enough to
create an anonymous commit off a given branch and tag it (this can be done in a
number of ways; most easily by creating a local release branch and never
pushing it to the repo).
> Change Jenkins jobs to use Gradle for trunk
> -------------------------------------------
>
> Key: LUCENE-9474
> URL: https://issues.apache.org/jira/browse/LUCENE-9474
> Project: Lucene - Core
> Issue Type: Test
> Components: general/build
> Reporter: Erick Erickson
> Assignee: Uwe Schindler
> Priority: Major
>
> I rushed the gate and pushed LUCENE-9433 without coordinating, my apologies
> for the confusion.
> Meanwhile, Uwe has disabled Jenkins jobs for the weekend and we'll fix this
> up Real Soon Now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
