1. 21 8月, 2020 1 次提交
  2. 19 8月, 2020 1 次提交
    • Update release.json and versions.json (#7847) · 6cae4afa
      冉小龙 提交于
      Signed-off-by: Nxiaolong.ran <rxl@apache.org>
      
      ### Motivation
      
      Currently, when the official website 2.6.1 document is released, we should first let 2.6.0 continue as the default version, wait for version 2.6.1 to appear in the historical version, and then try to use version 2.6.1 as the default version. If we directly publish the 2.6.1 version of the document, the search function will be unavailable.
      
      ### Modifications
      
      - Update versions.json
      6cae4afa
  3. 18 8月, 2020 1 次提交
  4. 18 6月, 2020 2 次提交
  5. 17 6月, 2020 1 次提交
  6. 20 5月, 2020 1 次提交
  7. 19 5月, 2020 1 次提交
  8. 25 4月, 2020 1 次提交
    • G
      Adjust version order (#6817) · 1f852eed
      guangning 提交于
      Motivation
      After the search is available, set 2.5.1 to the top
      Modifications
      After the search is available, set 2.5.1 to the top
      1f852eed
  9. 23 4月, 2020 1 次提交
    • G
      Update website (#6780) · d459eb9b
      guangning 提交于
      
      ### Motivation
      
      * Update website
      
      ### Modifications
      
      * Add 2.5.1 release document
      
      ### Verifying this change
      
      Local test pass
      d459eb9b
  10. 17 1月, 2020 1 次提交
  11. 11 12月, 2019 1 次提交
    • Update website stable version to 2.4.2 (#5830) · 9231d4f5
      冉小龙 提交于
      ### Motivation
      
      Apache Pulsar 2.4.2 has been done, but we can see that the stable version of the [website](https://pulsar.apache.org/en/) is 2.4.1. That was done intentionally to get around the website indexing issue. 
      
      Currently, Apache Pulsar's website indexing uses the **Algolia** framework, which takes some time. In Apache Pulsar 2.4.1,  users are complaining the website search is broken, this is the problem.
      
      So in release 2.4.2, we published 2.4.2 documentation but didn't promote it as the current stable. We will make sure the  **Algolia** index works before moving 2.4.2 as the current stable.
      
      In next release, we can think about how to improve the website update process for a release.
      
      ### Modifications
      
      - Update website stable version to 2.4.2
      9231d4f5
  12. 06 12月, 2019 1 次提交
  13. 04 9月, 2019 1 次提交
  14. 05 7月, 2019 1 次提交
  15. 31 5月, 2019 1 次提交
  16. 14 4月, 2019 1 次提交
  17. 21 2月, 2019 1 次提交
  18. 01 1月, 2019 1 次提交
  19. 25 10月, 2018 1 次提交
  20. 19 9月, 2018 1 次提交
  21. 03 8月, 2018 1 次提交