"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "RELEASE.txt" between
scikit-image-0.18.1.tar.gz and scikit-image-0.18.3.tar.gz

About: scikit-image is a collection of algorithms for image processing in Python.

RELEASE.txt  (scikit-image-0.18.1):RELEASE.txt  (scikit-image-0.18.3)
skipping to change at line 25 skipping to change at line 25
Before you start, make sure you have all the required write Before you start, make sure you have all the required write
permissions (if not, you will need to ask an owner to grant you permissions (if not, you will need to ask an owner to grant you
access), specifically to: access), specifically to:
- https://github.com/scikit-image/scikit-image-wheels - https://github.com/scikit-image/scikit-image-wheels
- https://pypi.org/project/scikit-image/ - https://pypi.org/project/scikit-image/
- https://github.com/scikit-image/scikit-image-web - https://github.com/scikit-image/scikit-image-web
- Check ``TODO.txt`` for any outstanding tasks. - Check ``TODO.txt`` for any outstanding tasks.
- Branch v<major>.<minor>.x from master. This is the "release branch", where - Branch v<major>.<minor>.x from `main`. This is the "release branch", where
you will make your changes gearing up for release, and cherry-pick them as you will make your changes gearing up for release, and cherry-pick them as
appropriate to master. appropriate to `main`.
- On the release branch, update the release notes: - On the release branch, update the release notes:
1. Review and cleanup ``doc/release/release_dev.rst``. 1. Review and cleanup ``doc/release/release_dev.rst``.
2. Make a list of merges, contributors, and reviewers by running 2. Make a list of merges, contributors, and reviewers by running
``tools/generate_release_notes.py -h`` and following that file's usage. ``tools/generate_release_notes.py -h`` and following that file's usage.
3. Paste this list at the end of the ``release_dev.txt``. 3. Paste this list at the end of the ``release_dev.txt``.
skipping to change at line 57 skipping to change at line 57
6. Rename the file to ``doc/release/release_<major>.<minor>.txt`` 6. Rename the file to ``doc/release/release_<major>.<minor>.txt``
7. Copy ``doc/release/release_template.txt`` to 7. Copy ``doc/release/release_template.txt`` to
``doc/release/release_dev.txt`` for the next release. ``doc/release/release_dev.txt`` for the next release.
8. Copy relevant deprecations from ``release_<major>_<minor>.txt`` 8. Copy relevant deprecations from ``release_<major>_<minor>.txt``
to ``release_dev.txt``. to ``release_dev.txt``.
- Submit the release notes for review by other project maintainers: - Submit the release notes for review by other project maintainers:
- Create a PR from v<major>.<minor>.x branch to master (at this point, - Create a PR from v<major>.<minor>.x branch to `main` (at this point,
the difference should show the full contents of the release notes). the difference should show the full contents of the release notes).
- Discuss with others, and make the changes directly to v<major>.<minor>.x bra nch. - Discuss with others, and make the changes directly to v<major>.<minor>.x bra nch.
- Once the consensus is found, ask the project maintainers to merge - Once the consensus is found, ask the project maintainers to merge
the PR. the PR.
- Cherry pick the change onto the release branch. - Cherry pick the change onto the release branch.
- On the master branch, update the version number in ``skimage/__init__.py`` - On the main branch, update the version number in ``skimage/__init__.py``
to the next ``.dev0`` version, commit, and push. This should follow PEP440 to the next ``.dev0`` version, commit, and push. This should follow PEP440
meaning that the appropriate version number would look something like meaning that the appropriate version number would look something like
``0.20.0.dev0`` with the period between ``0`` and ``dev`` and a trailing ``0.20.0.dev0`` with the period between ``0`` and ``dev`` and a trailing
``0`` immediately after ``dev``. The final ``0`` is necessary to ensure ``0`` immediately after ``dev``. The final ``0`` is necessary to ensure
that that
`NumpyVersion <https://github.com/scikit-image/scikit-image/pull/4947>`_ `NumpyVersion <https://github.com/scikit-image/scikit-image/pull/4947>`_
correctly interprets the version number. correctly interprets the version number.
- On the master branch, edit ``doc/source/_static/docversions.js``, - On the main branch, edit ``doc/source/_static/docversions.js``,
add the release, e.g., `0.15.x`, and commit. Cherry-pick this add the release, e.g., `0.15.x`, and commit. Cherry-pick this
change back to the release branch. change back to the release branch.
- Make sure you have all the required write permissions (if not, you will - Make sure you have all the required write permissions (if not, you will
need to ask Stéfan or Juan to grant you the access), specifically, to: need to ask Stéfan or Juan to grant you the access), specifically, to:
- https://github.com/scikit-image/scikit-image-wheels - https://github.com/scikit-image/scikit-image-wheels
- https://pypi.org/project/scikit-image/ - https://pypi.org/project/scikit-image/
- https://github.com/scikit-image/scikit-image-web - https://github.com/scikit-image/scikit-image-web
skipping to change at line 211 skipping to change at line 211
- scikit-image@python.org - scikit-image@python.org
- scipy-user@python.org - scipy-user@python.org
- scikit-learn@python.org - scikit-learn@python.org
- Update the version and the release date on Wikipedia - Update the version and the release date on Wikipedia
https://en.wikipedia.org/wiki/Scikit-image https://en.wikipedia.org/wiki/Scikit-image
- Make a PR to scikit-image with any updates you might have to these notes - Make a PR to scikit-image with any updates you might have to these notes
- If making a patch release (v<major>.<minor>.<patch>), forward-port the - If making a patch release (v<major>.<minor>.<patch>), forward-port the
release notes to the master branch and make a PR. release notes to the main branch and make a PR.
Conda-forge Conda-forge
----------- -----------
**Note**: conda-forge now has an automated bot who makes the below PR for you. **Note**: conda-forge now has an automated bot who makes the below PR for you.
Now all you have to do is to look at pull requests at Now all you have to do is to look at pull requests at
https://github.com/conda-forge/scikit-image-feedstock/pulls https://github.com/conda-forge/scikit-image-feedstock/pulls
and check for a new one for this version. Wait for all the continuous and check for a new one for this version. Wait for all the continuous
integration checks to go green, then merge. integration checks to go green, then merge.
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)