1. 18 Aug, 2022 1 commit
  2. 01 Apr, 2022 3 commits
  3. 25 Mar, 2022 1 commit
  4. 18 Mar, 2022 2 commits
  5. 25 Mar, 2022 4 commits
  6. 18 Mar, 2022 4 commits
  7. 14 Mar, 2022 1 commit
  8. 30 Dec, 2021 1 commit
  9. 29 Jan, 2022 1 commit
  10. 30 Dec, 2021 1 commit
  11. 10 Mar, 2022 4 commits
  12. 04 Mar, 2022 1 commit
  13. 03 Mar, 2022 2 commits
  14. 30 Dec, 2021 5 commits
  15. 27 Jan, 2022 1 commit
  16. 26 Jan, 2022 3 commits
  17. 24 Dec, 2021 2 commits
    • Dan Villiom Podlaski Christiansen's avatar
      NEWS: 1.0b1 release · 311e9a57959e
      Dan Villiom Podlaski Christiansen authored
      311e9a57959e
    • Dan Villiom Podlaski Christiansen's avatar
      versioning: create branch 1.0.x · 08347725306b
      Dan Villiom Podlaski Christiansen authored
      The upcoming release will be called 1.0 rather than 0.11.0. The main
      motivation for this is that I consider hg-git “ready”. In order for
      semantic versioning to make sense, something has to eventually be good
      enough. With the changes to user experience, I personally consider
      this good enough to actually use. And besides, if this isn't 1.0, when
      should it be? When development ceases?
      
      I've updated `CONTRIBUTING.rst` to specify an explicit compatibility
      policy.
      08347725306b
  18. 26 Jan, 2022 3 commits