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 2019/12/05 13:41:44 UTC

[GitHub] [pulsar] wolfstudy commented on issue #5801: Update website for 2.4.2 release

wolfstudy commented on issue #5801: Update website for 2.4.2 release
URL: https://github.com/apache/pulsar/pull/5801#issuecomment-562133084
 
 
   @sijie I close the pull request: #5795 .
   
   > the current tool automatically cuts the documentation master (2.5.0 documentation) as 2.4.2 release documentation. Please check if we need to make adjustments to the documentation to exclude features that only exists 2.5.0.
   
   According to the current release process, I have no way to achieve this. Because if we [base master branch](https://github.com/apache/pulsar/wiki/Release-process#14-update-the-site) , we will update all the documents merged into the master branch to 2.4.2. In other words, we do not have a good way to separate each version of the document from the master, right? 
   
   The document generation method in this pr is as follows:
   
   - git checkout branch-2.4
   - yarn run version 2.4.2
   - git checkout master 
   - git checkout -b rxl/docs_release_2.4.2
   - git add .
   - git commit -sm ""
   - git push origin rxl/docs_release_2.4.2
   
   In this way we can ensure that the 2.5.0 document will not appear in 2.4.2, but I am not sure if this is a reasonable way of operation. If there is a better way to solve this problem, please let me know.
   
   @tuteng Please help check, thanks.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services