[
https://issues.apache.org/jira/browse/LUCENE-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182824#comment-17182824
]
Uwe Schindler commented on LUCENE-9474:
---------------------------------------
bq. 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?
Yes, that was the intention back on some very old discussion.
When setting this up, we wanted to make sure that only releases packaged by us
have the official "version number", if somebody checks out from git or source
file and builds his own version, we wanted to have this a "snapshot" by
default. The reason for this was especially people having wrong toolchain (like
Java versions, Unicode versions,...). So only official binary builds have the
official version number.
Nevertheless, we can change this separate, I just replicated what Ant was/is
still doing and whats documented in the release documentation for the release
manager. The important thing for me is "-Dversion.suffix=XXXX", for Jenkins
compatibility.
> 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
