|
38 | 38 | ## Releasing a new version
|
39 | 39 | 1. Make a new branch of `xdmod-data` and:
|
40 | 40 | 1. Make sure the version number is updated in `xdmod_data/__version__.py`.
|
41 |
| - 1. Update the Open XDMoD compatibility matrix in the `README.md`. |
42 |
| - 1. Update `CHANGELOG.md` to change "Main development branch" to, e.g., `v1.0.1 (2024-06-XX)`. |
| 41 | + 1. In `README.md`: |
| 42 | + 1. Under the main heading, |
| 43 | + 1. In the sentence that begins, `This documentation is for ...`, |
| 44 | + replace the version number in bold, e.g.: |
| 45 | + ``` |
| 46 | + This documentation is for **v1.0.2**. |
| 47 | + ``` |
| 48 | + 1. Update the Open XDMoD compatibility matrix. |
| 49 | + 1. Update `CHANGELOG.md` to: |
| 50 | + 1. Change the `development branch` to, e.g., `v1.0.1 (2024-06-XX)`. |
| 51 | + 1. Add a summary of the changes in the version. |
| 52 | + 1. In `setup.cfg`, update the `long_description` to change the version number in the URL to the new version. |
43 | 53 | 1. Create a Pull Request for the new version.
|
44 | 54 | 1. After the Pull Request is approved (but not merged yet), follow these steps in a cloned copy of the branch:
|
45 | 55 | 1. Start up a virtual environment, e.g.:
|
|
88 | 98 | 1. Where it says `Attach binaries`, attach the built distribution that was uploaded to PyPI.
|
89 | 99 | 1. Click `Publish release`.
|
90 | 100 | 1. Go to the [GitHub milestones](https://github.com/ubccr/xdmod-data/milestones) and close the milestone for the version.
|
| 101 | +1. If this is a minor or patch release to a version that is not the most recent major version, |
| 102 | + 1. For each major version above this release's major version, |
| 103 | + 1. Add the entry for this version to the `CHANGELOG.md`. |
| 104 | + 1. In the `README.md`: |
| 105 | + 1. Add an item to the top of the bulleted list for |
| 106 | + the new version, making sure to replace the version number in |
| 107 | + the link text and in the URL. |
| 108 | + 1. Update the Open XDMoD compatibility matrix. |
91 | 109 |
|
92 | 110 | ## After release
|
93 |
| -1. Make a new branch of `xdmod-data` and: |
94 |
| - 1. Make sure the version number is updated in `xdmod_data/__version__.py` to a pre-release of the next version, e.g., `1.0.1-01`. |
95 |
| - 1. Update `CHANGELOG.md` to add a section at the top called `Main development branch`. |
96 |
| - 1. Go to the [GitHub milestones](https://github.com/ubccr/xdmod-data/milestones) and add a milestone for the version. |
97 |
| - 1. Create a Pull Request for the new version. |
98 |
| - 1. Once the Pull Request is approved, merge it into `main`. |
| 111 | +
|
| 112 | +1. In a Pull Request to the `main` branch of `xdmod-data`: |
| 113 | + 1. Make sure the version number is updated in `xdmod_data/__version__.py` |
| 114 | + to a development pre-release of the next version, e.g., `1.0.1.dev1`. |
| 115 | + 1. In `README.md`, under the main heading, in the sentence that begins, |
| 116 | + `This documentation is for ...`, replace the version number in bold, |
| 117 | + e.g.: |
| 118 | + ``` |
| 119 | + This documentation is for **v1.x.y (main development branch)**. |
| 120 | + ``` |
| 121 | + 1. Update `CHANGELOG.md` to add a section at the top called `v1.x.y (main |
| 122 | + development branch)`, replacing `1` with the major version under |
| 123 | + development. |
| 124 | + 1. Go to the [GitHub milestones](https://github.com/ubccr/xdmod-data/milestones) |
| 125 | + and add a milestone for the version under development. |
0 commit comments