Atomic Commits - An Easy & Proven Way to Manage & Automate Release Process

Transcript

1. Atomic Commits An Easy & Proven Way to Manage & Automate Release Process
6. __name__ = 李唯 / Wei Lee __what_i_am_doing__ = [ volunteers @ PyCon Taiwan, maintainer of commitizen-tools, ] __github__ = G Lee-W __site__ = p http://wei-lee.me $ cat speaker.py
7. File "speaker.py", line 1 __name__ = 李唯 / Wei Lee ^^^ SyntaxError: invalid syntax $ python speaker.py
8. Release
9. Release requests release history https://pypi.org/project/requests/#history
10. Software Versioning x.y.z
11. Calendar Versioning
12. One of the schemes of Calendar Versioning x.y.z Year Month Date
13. Example
14. Example
15. Example
16. And many other schemes
17. Semantic Versioning
18. Semantic Versioning x.y.z MAJOR Minor Patch
19. From @memenetes https://twitter.com/memenetes/status/1631339227785969664/photo/1 Example (meme)
20. https://hynek.me/articles/semver-will-not-save-you/
21. Even though it's not the savior, many projects are using it.
22. Example
23. Release a new version
24. Example release processes
25. Example release processes
26. Example release processes
27. Semantic Versioning 1. MAJOR: incompatible change 2. MINOR: backward compatible functionalities 3. PATCH: backward compatible bug fixes 

28. Commits from CPython What will you do if these are the changes you're going to release?
30. When developers made these changes, they knew what they were changing.
32. Concise commit messages make comprehending the changes easier
35. How to write good commit messages? 1. Separate subject from body with a blank line 2. Limit the subject line to 50 characters 3. Capitalize the subject line 4. Do not end the subject line with a period 5. Use the imperative mood in the subject line 6. Wrap the body at 72 characters 7. Use the body to explain what and why vs. how
36. Semantic Versioning 1. MAJOR: incompatible change 2. MINOR: backward compatible functionalities 3. PATCH: backward compatible bug fixes 

37. Semantic Versioning 1. MAJOR: incompatible change 2. MINOR: backward compatible functionalities 3. PATCH: backward compatible bug fixes 4. OTHER: other changes (e.g., documentation change)
38. Type of Changes 1.New Feature 2.Bug fix 3.Refactor 4.Style Change 5.Documentation 6.Improve test coverage 7.Performance 8.Build tool 9.CI/CD 10.and etc.
39. Mapping Type of change → Version
40. Mapping Type of change → Version
41. A simple rule example 
 (add the type at the end of commits)
42. A simple rule example 
 (add the type at the end of commits)
43. A simple rule example 
 (add the type at the end of commits)
44. Is there a better rule?
47. Conventional Commit Scheme Somehow set language to "Turtle" for syntax highlight works well 🤔
48. Example Commits from conventional-commit website
53. commitizen-tools
54. Please like
55. Please like, subscribe
56. Please like, subscribe and contribute
58. Install commitizen
59. Initialize commitizen
60. Initialize commitizen
61. Initialize commitizen
62. Initialize commitizen
63. Initialize commitizen
64. Initialize commitizen
65. Initialize commitizen
66. Initialize commitizen
67. Initialize commitizen
68. Initialize commitizen
69. Making a commit
70. Making a commit
71. Making a commit
72. Making a commit
73. Making a commit
74. Making a commit
75. Making a commit
76. Output commit
77. Bump version
78. Bump version
79. Bump version Generate a new commit for bumping versions
80. Bump version
81. Changelog
83. Customizable changelog WIP
84. Integrate with GitHub Actions
85. Integrate with GitHub Actions
86. Integrate with GitHub Actions
87. Integrate with GitHub Actions
88. Integrate with GitHub Actions
89. Let's wrap up the process
90. Commit flow
91. Release flow
92. Join us and 
 make commitizen-tools better ⭐
94. PyCast EP 4
95. Pyducts Pre-Order
96. Pyducts Pre-Order
97. Pyducts Pre-Order
98. Pyducts Pre-Order
99. Pyducts Pre-Order
101. Thank you