[
https://issues.apache.org/jira/browse/SOLR-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525318#comment-17525318
]
ASF subversion and git services commented on SOLR-16159:
--------------------------------------------------------
Commit a2c44cf549ddff13ab0b15b3837f6f0cdd9c8391 in solr's branch
refs/heads/main from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a2c44cf549d ]
SOLR-16159: Add prerelease suffixes to non-released ref-guide versions. (#812)
> Add prerelease version to non-released branches for ref-guide
> -------------------------------------------------------------
>
> Key: SOLR-16159
> URL: https://issues.apache.org/jira/browse/SOLR-16159
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The ref-guide build will include all release-branches in the ref-guide build
> (branch_x_y). This means whenever we cut the branch for the next minor
> release, it will automatically be added to the official ref-guide. In order
> to mitigate this, we should include a prerelease tag until the release is
> complete. This will tell users that it is not a fully released version.
> Instead of {{-SNAPSHOT}} or {{-prerelease}} as the version suffix for all
> unreleased versions, I think we should go with something shorter that looks
> better in the drop-down.
> for x.0 releases So the first release of a major version, the prerelease
> suffix should be {{-alpha}} and for x.1-99 releases, the suffix should be
> {{{}-beta{}}}, since we know it is a bit more stable than the x.0 release.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
