~sschwarzer/ftputil

ftputil/doc/README.release -rw-r--r-- 980 bytes
77f2ca24 — Stefan Schwarzer Move item "Push to repository" a month ago 
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

Things to do for a new release:

- Do commits

- Write announcement in announcements.txt

- Increase version number in `VERSION` (`ftputil/version.py`
  and `ftputil.txt` are handled by the `sed` invocation through
  `make patch`)

- `make patch`

- Do outstanding commits due to patching

- Run `tox` for testing (`make tox_test`)

- `make dist`

If everything looks fine ...

- Tag release (tags are formed like "v5.0.3-alpha2")

- Add new version to `versions.md` page for the website

- Update pre-release documentation (if necessary)

- Push to repository

- Post announcement to ftputil mailing list at
  `ftputil@lists.sschwarzer.net` (after possibly
  updating the documentation, see below)


Only for non-alpha/beta releases:

  _Before_ sending announcement to mailing list ...

  - Update website

  - Upload new version to PyPI (`make upload`)

- Send announcement to `python-announce-list@python.org`
  XXX: No longer do this. Last time I did, I got a lot more spam.