-
Notifications
You must be signed in to change notification settings - Fork 10
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
v0.6.0 #744
Conversation
draft of the GitHub release: https://github.com/BAMWelDX/weldx/releases/tag/untagged-b904093fe4d4ade154f6 |
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
# try to obtain key from underlying dict. | ||
with pytest.raises(KeyError), pytest.warns(WeldxDeprecationWarning): | ||
_ = self.fh.data[protected_key] |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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...
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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
Check out this pull request on 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. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 😄
There was a problem hiding this comment.
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 😉
Changes
release
0.6.0
How to release
A short primer in the steps needed to release a new version of the
weldx
packagecreate release PR
vX.Y.Z
and add therelease
tag (example here)
CHANGELOG.rst
is up to date and enter current date to the release versionCITATION.cff
version number and datedeprecated
and remove deprecated codeMerge the Pull Request
add Git(hub) tag
doubt use vX.Y.Z everywhere)
(this website can be used to convert rST -> MD)
ReadTheDocs update
latest
,stable
andvX.Y.Z
get triggered on RTD (the tag build can gettriggered twice, resulting in a failed/duplicated build, no need to worry)
pypi release
build
action completes hereconda-forge release
pull-request here
meta.yaml
in the pull request, manually update all changes in the build and run dependencies