Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.6.0 #744

Merged
merged 10 commits into from
Apr 29, 2022
Merged

v0.6.0 #744

merged 10 commits into from
Apr 29, 2022

Conversation

CagtayFabry
Copy link
Member

@CagtayFabry CagtayFabry commented Apr 28, 2022

Changes

release 0.6.0

How to release

A short primer in the steps needed to release a new version of the weldx package

create release PR

  • create a PR that finalizes the code for the next version
    • name the PR according to the version vX.Y.Z and add the release
      tag (example here)
    • make sure CHANGELOG.rst is up to date and enter current date to the release version
    • add summarized release highlights where appropriate
    • update the CITATION.cff version number and date
    • search the project for deprecated and remove deprecated code
  • wait for CI jobs to finish
  • check the readthedocs PR build
  • wait for reviews

Merge the Pull Request

  • merge normally and wait for all CI actions to finish on the main branch

add Git(hub) tag

  • tag and release the current master version on GitHub using the Releases feature
    • name the release git tag according to the version released (e.g. v0.3.3)
    • name the GitHub release accordingly, omitting the v prefix (this can be change later so don't worry, in
      doubt use vX.Y.Z everywhere)
    • copy the changes/release notes of the current version into the description
      (this website can be used to convert rST -> MD)
  • wait for all Github Actions to finish

ReadTheDocs update

  • check the build processes for latest, stable and vX.Y.Z get triggered on RTD (the tag build can get
    triggered twice, resulting in a failed/duplicated build, no need to worry)

pypi release

  • check the automatic release to pypi after the build action completes here

conda-forge release

  • pypi release should get picked up by the conda-forge bot and create the new
    pull-request here
  • carefully check the meta.yaml in the pull request, manually update all changes in the build and run dependencies
  • merge with 2 or more approved reviews

@github-actions
Copy link

github-actions bot commented Apr 28, 2022

Unit Test Results

       1 files  ±0         1 suites  ±0   2m 36s ⏱️ - 1m 8s
2 146 tests ±0  2 146 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit cd47450. ± Comparison against base commit a1e7184.

♻️ This comment has been updated with latest results.

@CagtayFabry
Copy link
Member Author

@codecov
Copy link

codecov bot commented Apr 28, 2022

Codecov Report

Merging #744 (cd47450) into master (a1e7184) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #744      +/-   ##
==========================================
- Coverage   95.85%   95.82%   -0.04%     
==========================================
  Files          92       92              
  Lines        6520     6516       -4     
==========================================
- Hits         6250     6244       -6     
- Misses        270      272       +2     
Impacted Files Coverage Δ
weldx/asdf/file.py 96.20% <ø> (-0.40%) ⬇️
weldx/asdf/util.py 90.32% <0.00%> (-0.33%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a1e7184...cd47450. Read the comment docs.

Comment on lines -596 to -598
# try to obtain key from underlying dict.
with pytest.raises(KeyError), pytest.warns(WeldxDeprecationWarning):
_ = self.fh.data[protected_key]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can this be deleted now? @marscher

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason the first line below "changes" in the RTD version of the changelog is shown in bold letters:

https://weldx--744.org.readthedocs.build/en/744/changelog_link.html

Checked the changelog file and the only difference to the other lines that I could find is that the line in question has only a single space between the - and the text while all others have 2 spaces. I am not that familiar with RST, but I guess that's the problem.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CagtayFabry you were absolutely right about this deletion.

@vhirtham RST is sometimes also very picky with missing line breaks. But this should not cause usage of bold setting...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good find @vhirtham , let's see if it is fixed with the spaces (otherwise we can reformat later)

Copy link
Collaborator

@vhirtham vhirtham Apr 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marscher argh... this should have been an extra comment ... ooops. Well let's see what fixes it

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

Co-authored-by: vhirtham <volker.hirthammer@bam.de>
********************

This release includes major changes to the handling and support of units in the API and ASDF schemas. All classes now support and require quantities where appropriate. Pure unitless numbers are no longer supported.

Copy link
Collaborator

@vhirtham vhirtham Apr 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Furthermore, a new class called `GenericSeries` was added. It provides a common interface to describe coordinate-based data either by discrete values or mathematical expressions. A built-in mechanism lets you derive specialized series with specific requirements. For more information, have a look [at the new tutorial](https://weldx.readthedocs.io/en/v0.6.0/tutorials/generic_series.html)

Since somebody already merged the suggestion while I was editing it for additional content 😄

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

safer to edit directly in the file I guess 😉

@CagtayFabry CagtayFabry merged commit b7f599a into master Apr 29, 2022
@CagtayFabry CagtayFabry deleted the v0.6.0 branch April 29, 2022 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants