Skip to content

Commit

Permalink
Merge pull request #284 from hakonanes/post-0.8.1-release
Browse files Browse the repository at this point in the history
Post 0.8.1 release updates
  • Loading branch information
harripj authored Feb 15, 2022
2 parents 49ef435 + 07879bc commit ff6e541
Show file tree
Hide file tree
Showing 4 changed files with 35 additions and 2 deletions.
3 changes: 3 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ All notable changes to this project will be documented in this file.
The format is based on `Keep a Changelog <https://keepachangelog.com/en/1.0.0/>`_, and
this project adheres to `Semantic Versioning <https://semver.org/spec/v2.0.0.html>`_.

Unreleased
==========

2022-02-14 - version 0.8.1
==========================

Expand Down
3 changes: 2 additions & 1 deletion MANIFEST.in
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,10 @@ include getting_started.rst
include LICENSE
include MANIFEST.in
include README.rst
include RELEASE.rst
include readthedocs.yml
include setup.cfg
include setup.py

recursive-include doc Makefile make.bat *.rst *.py *.ipynb *.bib
recursive-include doc/_static *.png *.svg *.css
recursive-include doc/_static *.png *.svg *.css
29 changes: 29 additions & 0 deletions RELEASE.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
How to make a new release of ``orix``
=====================================

Create a PR to the `master` branch and go through the following steps.

Preparation
-----------
- Bump ``__version__`` in `orix/__init__.py`, for example "0.8.2".
- Update the changelog `CHANGELOG.rst`.
- Let the PR collect comments for a day to ensure that other maintainers are
comfortable with releasing. Merge.

Release (and tag)
-----------------
- Create a tagged, annotated (meaning with a release text) with the name
v0.8.2" and title "orix 0.8.2". The tag target will be the ``master`` branch.
Draw inspiration from previous release texts. Publish the release.
- Monitor the publish GitHub Action to ensure the release is successfully
published to PyPI.

Post-release action
-------------------
- Monitor the documentation build at
https://readthedocs.org/projects/orix/builds to make sure the new stable
documentation is successfully built from the release.
- Make a post-release PR to ``master`` with ``__version__`` updated (or
reverted), e.g. to "0.9.dev0", and any updates to this guide if necessary.
- Tidy up and close corresponding milestone.
- A PR to the conda-forge feedstock will be created by the conda-forge bot.
2 changes: 1 addition & 1 deletion orix/__init__.py
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
__name__ = "orix"
__version__ = "0.8.1"
__version__ = "0.9.dev0"
__author__ = "orix developers"
__author_email__ = "pyxem.team@gmail.com"
__description__ = "orix is an open-source python library for handling crystal orientation mapping data."
Expand Down

0 comments on commit ff6e541

Please sign in to comment.