-
Notifications
You must be signed in to change notification settings - Fork 34
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
Release v0.4.2 #100
Release v0.4.2 #100
Conversation
The old docs/input_parameters.md file was not included in the document. The new file with rst format is added to the documentations in: docs/source/input_parameters.rst
Addine the new input_parameters to index.rst and removing the old file.
pypi test release on push for main branch
Setting Workflows (issue #71)
I have made minor edits to correct small typos or improve clarity
Input pars doc
Fix and enhance documentation
Our previous settings are deprecated since September 25th 2023 https://blog.readthedocs.com/migrate-configuration-v2/
Mimimum required readthedocs config file
…ommand-cli Hotfix/hidden result files command cli
Fixed a few small spelling errors.
Fixed the mismatch between a title length and the underlying line of "~" symbols, as requested by the reviewers
This fixes the problem currently blocking PR #96
Fix/docs errors
updating the secrets for API Token for the automatic test release of software after Pushes and PRs to developemnt and main
using kebab-case for skip-exisiting and repository-url
solving the test.pypi release issue #96
The new features added will allow the user to perform some data analysis and visualization routines: changes ------ *. ramp/post_process/post_process.py - the class Plot is the main class carrying on the plotting and data analysis functionalities with custom APIs providing access to some pd.DataFrame features also easy to plot functions conencting to plotly and matplotlibe methods. - different plotting classes that include a specific plot type visualiztion using two different engines (plotly & matplotlib) *. ramp.__init__.py - adding the Plot class to the init. documentation ------------- - the functions API docuemntation is added to the API documentaiton - A full example titled "Plot class" is added to the example gallery describing the full potential of the new functionalities
Plot class for ramp visualization and data analysis routines (isse #63)
@Bachibouzouk I would add black and maybe isort to the list! |
Then we should do this in separate PRs and then I will rebase the release branch on the dev branch once this has been merged. Normally the release branch should not have too much "work" done into it, only release related stuff: because for black one could apply black and setup a github action which rejects not black linted code. For that we need to pin a black version in the requirements. I would not consider those "release related" commits. Edit --> I did open a PR in #101 |
I think it would be great if we could also quickly address issue #83 as part of the new release since that is blocking several old-school users, while it seems that we have found a relatively easy fix in the related GitHub thread. I can implement myself the proposed fix if needed, but it would make more sense for @Bachibouzouk to set up a PR since he proposed such a fix. |
Gladly, I just cannot promise I'll to do it by tomorrow :) I will do it after the lint PR is accepted so I can work with linted code :) |
Sure, no hurry! (: Thanks |
Having finalised PR #102 , we should proceed with the new code release. This was originally meant to be v0.4.2, but we agreed in the last developers meeting to name it instead v0.5.0. So, I think that what needs to happen here is to update the changelog to call this v0.5.0. Are there any other missing things? The Zenodo publication of the new release has been automated via the Zenodo web interface, so it will automatically happen. |
I guess another thing is indeed to update the AUTHORS file to add those who will be part of the JOSS paper but are not yet mentioned there |
I would rather create a new branch What needs to be done is already listed in this PR's description |
Taken cared of in #106 |
Remaining TODO in this PR:
main
do not delete the branch but merge it intodevelopment