[
https://issues.apache.org/jira/browse/LUCENE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393530#comment-13393530
]
Robert Muir commented on LUCENE-4150:
-------------------------------------
Right, i think its correct now. If someone builds a snapshot, they get
4.0-SNAPSHOT.
to make an alpha release we use -Dversion=4.0-ALPHA.
About jira, after we release i do think we should make the version in JIRA so
people
can report bugs against it. But I don't think we should do that now (or people
will get
confused about what version to terget things).
The only trick here for alpha/beta is the internal number LUCENE_MAIN_VERSION
used
by IndexWriter only internally must be bumped after alpha to 4.0.0.1 or
something,
so that we know which exact version of lucene wrote the segment. it must be a
number
so that various comparators etc work. but thats totally internal to indexwriter
and
no users see it.
> Change version properties in branch_4x to "4.0-ALPHA-SNAPSHOT"
> ---------------------------------------------------------------
>
> Key: LUCENE-4150
> URL: https://issues.apache.org/jira/browse/LUCENE-4150
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Affects Versions: 4.0
> Reporter: Steven Rowe
> Priority: Minor
>
> The next release off branch_4x will be named "4.0-ALPHA", so the current
> version string should be "4.0-ALPHA-SNAPSHOT".
> (Similarly, after 4.0-ALPHA is released, the version string should be changed
> to "4.0-BETA-SNAPSHOT".)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
