1. 24 11月, 2022 2 次提交
  2. 23 11月, 2022 1 次提交
  3. 22 11月, 2022 2 次提交
  4. 21 11月, 2022 2 次提交
  5. 18 11月, 2022 3 次提交
  6. 17 11月, 2022 2 次提交
  7. 16 11月, 2022 1 次提交
  8. 13 11月, 2022 1 次提交
  9. 11 11月, 2022 3 次提交
  10. 10 11月, 2022 1 次提交
  11. 09 11月, 2022 1 次提交
    • J
      [chore] Separate Python API into another repository (#12779) · 1347a8f9
      Jay Chung 提交于
      Currently, our Python API code is a module in apache/dolphinscheduler codebase,
      each time users change Python API code, they need to run all requests CI check
      for dolphinscheduler and Python API, But if the user does only change Python
      code, it could be merged if Python API CI pass and do not dependent on others CI.
      
      Besides, we release Python API as the same version of dolphinscheduler. It is
      easy for user to match Python API version. But when Python API does not change
      any code, but dolphinscheduler release a bugfix version, Python API has to
      release the new version to match dolphinscheduler. This happened when we
      released Python API 2.0.6 and 2.0.7. 2.0.6 and 2.0.7 is bugfix version, and
      Python API does not change any code, so the PyPI package is the same.
      
      Separate Python API also makes our code more sense, we will have more
      distinguished code in dolphinscheduler and Python API new repository.
      Have separate issue tracker and changelog for information to users.
      
      ref PR in other repository: apache/dolphinscheduler-sdk-python#1
      
      see more detail in mail thread: https://lists.apache.org/thread/4z7l5l54c4d81smjlk1n8nq380p9f0oo
      1347a8f9
  12. 07 11月, 2022 2 次提交
  13. 03 11月, 2022 1 次提交
  14. 01 11月, 2022 1 次提交
  15. 31 10月, 2022 4 次提交
  16. 30 10月, 2022 1 次提交
  17. 29 10月, 2022 1 次提交
  18. 27 10月, 2022 3 次提交
  19. 26 10月, 2022 1 次提交
  20. 24 10月, 2022 1 次提交
  21. 19 10月, 2022 1 次提交
  22. 18 10月, 2022 1 次提交
  23. 17 10月, 2022 1 次提交
  24. 16 10月, 2022 1 次提交
  25. 14 10月, 2022 2 次提交