[
https://issues.apache.org/jira/browse/SOLR-16880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796849#comment-17796849
]
ASF subversion and git services commented on SOLR-16880:
--------------------------------------------------------
Commit 0fc72e2b179852bb99f56d50fd0f12ae88b869e1 in solr's branch
refs/heads/branch_9x from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=0fc72e2b179 ]
SOLR-16880: Add OAS to release automation (#2125)
Modifies our 'assembleRelease' gradle task and smoketester to handle a
new release artifact: an OpenAPI spec ("OAS") covering Solr's v2 APIs.
The spec (along with associated checksum and signature files) are made
available under a separate 'openApi' directory, similar to our 'changes' files.
---------
Co-authored-by: Houston Putman <[email protected]>
> Make OpenAPI spec a release artifact
> ------------------------------------
>
> Key: SOLR-16880
> URL: https://issues.apache.org/jira/browse/SOLR-16880
> Project: Solr
> Issue Type: Improvement
> Components: v2 API
> Reporter: Jason Gerlowski
> Priority: Major
> Attachments: Skjermbilde 2023-12-07 kl. 11.01.57.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> SOLR-16346 added OpenAPI spec generation to Solr - allowing us to produce a
> detailed description of our v2 APIs (or at least - those APIs implemented
> using JAX-RS).
> These spec files have a lot of potential uses - from generating
> documentation, to API clients, to web UIs. These have a lot of promise, but
> it will take the community time to implement and adopt some of them.
> We should make the OpenAPI spec available as a release artifact, so that
> users can more easily take advantage of it. Having it published on each
> release will also allow us to compare specs across versions, as a way to
> detect backcompat breaks before changes go out the door.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
