You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/10/24 05:20:02 UTC

[GitHub] [pulsar] Anonymitaet commented on pull request #18143: [improve][doc] Update swagger for 2.10.2

Anonymitaet commented on PR #18143:
URL: https://github.com/apache/pulsar/pull/18143#issuecomment-1288434607

   > @Anonymitaet Will the swagger files move the `pulsar-site` repo?
   
   @urfreespace @tisonkun can you take a look at the following questions? Thank you!
   
   ### Q1. 
   
   Now the swagger files in [pulsar](https://github.com/apache/pulsar/tree/master/site2/website/static/swagger) are synced to [pulsar-site](https://github.com/apache/pulsar-site/tree/main/site2/website-next/static/swagger), can we remove swagger files in pulsar and only keep them in pulsar-site? (Does the REST API doc build process rely on the files in pulsar and must be completed in pulsar?)
   
   ### Q2. 
   
   We use swagger for generating [REST API docs](https://pulsar.apache.org/admin-rest-api/?version=master) only.
   
   Since we use one doc set now (2.10.x for 2.10.0, 2.10.1, 2.10.2, ...), does this mean we just need to generate REST API doc for 2.10.x only instead of generating for 2.10.0, 2.10.1, 210.2, ...?
   
   If yes, the [release process](https://github.com/apache/pulsar/blob/master/wiki/release/release-process.md#update-swagger-file) needs to be updated (now release managers generate swagger files for each release), that is, swagger files should be only generated for major releases (2.10.x, 2.11.x, 2.12.x, ...) instead of minor releases (2.10.1, 2.10.2, ...).
   
   cc @momo-jun @labuladong 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org