File tree Expand file tree Collapse file tree 2 files changed +10
-2
lines changed
Expand file tree Collapse file tree 2 files changed +10
-2
lines changed Original file line number Diff line number Diff line change @@ -247,8 +247,9 @@ sdist-tests:
247247bdist-egg-tests :
248248 $(PYTHON ) -c ' from nisext.testers import bdist_egg_tests; bdist_egg_tests("nibabel")'
249249
250- source-release : clean
250+ source-release : distclean
251251 python -m compileall .
252+ make distclean
252253 python setup.py sdist --formats=gztar,zip
253254
254255venv-tests :
Original file line number Diff line number Diff line change @@ -142,12 +142,15 @@ Release checklist
142142 make doctest
143143 cd ..
144144
145+ * Check everything compiles without syntax errors::
146+
147+ python -m compileall .
148+
145149* The release should now be ready.
146150
147151* Edit :file: `nibabel/info.py ` to set ``_version_extra `` to ``'' ``; commit.
148152 Then::
149153
150- make distclean
151154 make source-release
152155
153156* Once everything looks good, upload the source release to PyPi. See
@@ -194,6 +197,10 @@ Release checklist
194197 If this is just a maintenance release from ``maint/1.0.x `` or similar, just
195198 tag and set the version number to - say - ``1.0.2.dev ``.
196199
200+ * Push tags::
201+
202+ git push --tags
203+
197204* Make next development release tag
198205
199206 After each release the master branch should be tagged
You can’t perform that action at this time.
0 commit comments