~sschwarzer/ftputil

ref: c6d0136bf66260c302304a9c53848e08337d405d ftputil/doc/README.release -rw-r--r-- 977 bytes
c6d0136bStefan Schwarzer Mention that `account` and `session_factory` normally aren't needed 6 years 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
44
45
Things to do for a new release:

- Do commits

- Update info on new version in `README.txt`

- 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 && make docs`

- Do outstanding commits due to patching

- Run `tox` for testing

- `make dist`

- Tag release (tags are formed like "release2_0_3b2")

- Push to main and Bitbucket repositories

- Add new version to Trac issue tracker

- Add new version to Download page on the website

- Mark corresponding milestone as completed

- Update pre-release documentation

- Post announcement to ftputil mailing list (after possibly
  updating the documentation, see below)


Only for non-alpha/beta releases:

  _Before_ sending announcement to mailing list ...

  - Update documentation on the website

  - Register new version with PyPI

- Send announcement to comp.lang.python.announce