File: RELEASE.txt

package info (click to toggle)
mapproxy 1.13.0-1~bpo10%2B1
  • links: PTS, VCS
  • area: main
  • in suites: buster-backports
  • size: 6,332 kB
  • sloc: python: 39,206; xml: 6,328; javascript: 866; makefile: 162
file content (45 lines) | stat: -rw-r--r-- 1,347 bytes parent folder | download | duplicates (4)
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
Making a new MapProxy release
=============================

Preparation
-----------

You will need wheel and twine to build and upload a new release:

    pip install wheel twine



- Update CHANGES.txt with all important changes. Verify version and date in header line.
- Update version in `setup.py` and `doc/conf.py`.
- Commit updates changelog and version and tag the commit with (`git tag 1.12.0`).
- Push the new tag (`git push origin --tags`).


Build and upload
----------------

Build source tar.gz and wheel. (`egg_info -b "" -D` to remove date suffix from release version).

    python setup.py egg_info -b "" -D sdist
    python setup.py egg_info -b "" -D bdist_wheel


The new release can be uploaded to https://pypi.org/project/MapProxy/ with twine. You need an account on https://pypi.org and you need to be a collaborator for the MapProxy project.

    twine upload dist/MapProxy-1.12.0.tar.gz
    twine upload dist/MapProxy-1.12.0-py2.py3-none-any.whl

Be aware, you can only upload a file once. If you made a mistake (e.g. files are missing in the tar.gz) then you will need to make a new release with an updated minor version.




Announce
--------


- Add a new blog article to mapproxy.org with the most important changes
- MapProxy mailing list (copy from previous release mail as a template)
- Twitter (with link to blog)