You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2018. It is now read-only.
-[ ] Install `zest.releaser` with recommended addons: `pip install zest.releaser[recommended]`.
4
+
-[ ] Check if long description of packege is looking OK (`longtest` command).
5
+
-[ ] Inspect changes from last release (`lasttaglog` command from `zest.releaser`) and update `ChaneLog` (`addchangelogentry` command is usefull) if needed.
6
+
-[ ] Run `fullrelease` command (it is commig from `zest.releaser`). Steps bellow should be handled by `zest.releaser`.
7
+
-[ ] Run `pyaroma` to check for following packaging best practicies.
8
+
-[ ] Run `check-manifest` to check if `MANIFEST.in` is correct.
9
+
-[ ] Enter version using semantic versioning.
10
+
-[ ] Make sure that version is bumped in correct place (`__version___`).
11
+
-[ ] Commit new version.
12
+
-[ ] Add a tag.
13
+
-[ ] Checkout tag and investigate if everything is OK.
14
+
-[ ] Do not upload package.
15
+
-[ ] Enter new development version using semantic versioning.
16
+
-[ ] Do not push to main repo.
17
+
-[ ] Look at the log and diff again to see if everything is looking as you intended.
18
+
-[ ] Push to main repo (`git push`).
19
+
-[ ] Wait for tests to pass on CI.
20
+
-[ ] Push tags (`git push --tags`).
21
+
-[ ] Check the PyPI listing page to make sure that it is looking OK (files, description, etc.).
22
+
-[ ] Check if new version can be installed `pip install pydot_ng`
0 commit comments