Skip to content

Commit

Permalink
mnt: bumped release numbers
Browse files Browse the repository at this point in the history
  • Loading branch information
zerothi committed Jan 28, 2022
1 parent fa468bf commit 9e7cc11
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 36 deletions.
5 changes: 4 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,10 @@ 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) once
we hit release version 1.0.0.

## [Unreleased] - YYYY-MM-DD
## [UNRELEASED] - YYYY-MM-DD


## [0.12.0] - 2022-1-28
### Added
- Geometry.sub_orbital is added
- BrillouinZone.volume enables easy calculation of volumes for BZ integrals
Expand Down
4 changes: 2 additions & 2 deletions CITATION.cff
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ authors:
given-names: "Nick"
orcid: "https://orcid.org/0000-0003-3038-1855"
title: "sisl"
version: "0.11.0"
version: "0.12.0"
doi: 10.5281/zenodo.597181
url: https://github.com/zerothi/sisl
repository-code: https://github.com/zerothi/sisl
Expand All @@ -19,4 +19,4 @@ keywords:
- DFT
- LCAO
- NEGF


38 changes: 5 additions & 33 deletions DEPLOY.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,50 +16,22 @@ below sequence.

The release cycle should be performed like this:

1. Increment the release numbers in the top-directory
setup.py script
These are
1. Update released versions in `CHANGELOG.md` and `CITATION.cff`

MAJOR
MINOR
MICRO
2. Commit changes.

Alltogether the version number _is_:
`VERSION=MAJOR.MINOR.MICRO`
In the following `VERSION` should be replaced by the correct release
numbers

2. Set the variable:

ISRELEASED = True

3. Set the variable `GIT_REVISION` to the latest commit.
This means that the revision specification for the release
actually corresponds to the commit just before the actual release.
You can get the commit hash by:

git rev-parse HEAD

GIT_REVISION = <git rev-parse HEAD>

4. Add `setup.py` to the commit and commit using:

git commit -s -m "sisl release: VERSION"

with the corresponding version number.

5. Tag the commit with:
3. Tag the commit with:

git tag -a "vVERSION" -m "Releasing vVERSION"

6. Create tarballs and wheels and upload them
4. Create tarballs and wheels and upload them

rm -rf dist
python setup.py sdist bdist_wheel
twine upload dist/sisl-VERSION*.tar.gz
twine upload dist/sisl-VERSION*.whl

7. Create conda uploads.
5. Create conda uploads.

The conda uploads are based on conda-forge and an associated
sisl-feedstock is used. To update it, follow these steps:
Expand Down

0 comments on commit 9e7cc11

Please sign in to comment.