Skip to content

Commit f14fbda

Browse files
committed
Prepare for version 0.6.0 release
1 parent 2106350 commit f14fbda

File tree

4 files changed

+24
-13
lines changed

4 files changed

+24
-13
lines changed

RELEASE.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
# Release 0.6.0
2+
3+
This is a re-release of version 0.5.0, which was accidentally released with
4+
stale files.
5+
16
# Release 0.5.0
27

38
In Seeder, add the ability to reseed generators with either

_config.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ exclude:
55
- doc/pytorch.md
66
- doc/tensorflow_status.md
77
- fwr13y/
8-
- fwd9m_reserve/
9-
- test/README.md
8+
- test/d9m/README.md
9+
- test/d9m/might_do_menu.md
1010
- might_do_menu.md
1111
- pypi_description.md
1212
- pytorch.md

fwr13y/version.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,4 @@
1313
# limitations under the License.
1414
# ========================================================================
1515

16-
__version__ = "0.5.0"
16+
__version__ = "0.6.0"

release_procedure.md

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,13 @@ git tag v0.5.0
3434
git push origin v0.5.0
3535
```
3636

37-
## 5. Create a Source Distribution
37+
## 5. Clean the Build Environment
38+
39+
```
40+
rm -rf build dist *.egg-info
41+
```
42+
43+
## 6. Create a Source Distribution
3844

3945
```
4046
python3 setup.py sdist
@@ -49,17 +55,17 @@ can be done by viewing the `stdout` of `python3 setup.py sdist`, by viewing
4955
`framework_reproducibility.egg-info/SOURCES.txt`, or by running `tar -xf` on the
5056
source distribution file and examing the resuling directory structure.
5157

52-
Note that `framework-reproducibility.egg-info/SOURCES.txt` is read in, modified,
53-
and written back out by `python3 setup.py sdist`. Because of this, if any items
54-
are to be excluded from the distribution (e.g. via `MANIFEST.in` or the
55-
`packages` parameter of `setup()` in `setup.py`) then
58+
Note that `framework-reproducibility.egg-info/SOURCES.txt` is read in (if it
59+
exists), modified, and written back out by `python3 setup.py sdist`. Because of
60+
this, if any items are to be excluded from the distribution (e.g. via
61+
`MANIFEST.in` or the `packages` parameter of `setup()` in `setup.py`) then
5662
`framework-reproducibility.egg-info` must be deleted prior to running
5763
`python3 setup.py sdist`, otherwise the exluded items will remain.
5864

5965
Note that to install the source distribution, the user will need to have `pip`
6066
installed, a new-enough version of `setuptools` and also `wheel`.
6167

62-
## 6. Create a Universal Wheel
68+
## 7. Create a Universal Wheel
6369

6470
```
6571
python3 setup.py bdist_wheel
@@ -75,7 +81,7 @@ Note that `setup.cfg` specifies that wheels are universal by default.
7581
[Common Python Packaging Mistakes][2] is a particularly useful resource that I
7682
used in preparing the above two steps.
7783

78-
## 7. Upload to PyPI
84+
## 8. Upload to PyPI
7985

8086
Upload the source distribution and the universal wheel to the Python Package
8187
Index (PyPI).
@@ -97,7 +103,7 @@ repository: https://test.pypi.org/legacy/
97103
username: <username>
98104
```
99105

100-
### 7a. Test PyPI Server
106+
### 8a. Test PyPI Server
101107

102108

103109
```
@@ -130,7 +136,7 @@ waiting for a few minutes can resolve issues where it seems that the latest
130136
version is not yet available to install, even though you can see it should be
131137
availble according to the web page for the distribution.
132138

133-
### 7b. Real PyPI Server
139+
### 8b. Real PyPI Server
134140

135141
```
136142
twine upload --repository pypi dist/framework-reproducibility-<version>.tar.gz
@@ -147,7 +153,7 @@ venv/bin/pip install framework-reproducibility
147153
rm -rf venv
148154
```
149155

150-
## 8. Create the GitHub Release
156+
## 9. Create the GitHub Release
151157

152158
Finally, on GitHub, create a new release using the version tag created earlier
153159
(e.g. `v0.4.0`).

0 commit comments

Comments
 (0)