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

Release 0.4.0 #616

Merged
merged 6 commits into from
Jun 16, 2023
Merged

Release 0.4.0 #616

merged 6 commits into from
Jun 16, 2023

Conversation

lfarv
Copy link
Contributor

@lfarv lfarv commented Jun 7, 2023

A new version may be released. It's a minor maintenance version before releasing 1.0
I propose to postpone the description of deprecated features to the 1.0 version.

This branch includes improved developer notes describing the proposed release procedure,

This release may still wait for the pending minor modifications.

The proposed release notes are:

Main modifications

This releases introduces:

  • Time-dependent multipole strengths (sine wave, white noise, user-defined)
  • Updated values of the physical constants
  • Compatibility with python 3.11
  • 3d element rotations (tilt, pitch, yaw)
  • Plot of the Σ beam matrix
  • Multibunch Wakefield
  • Multibunch beamloading
  • Beam monitor element (statistics on the particle distribution)
  • Extend the definition of refpts to string patterns, regular expressions, None, All, End special values
  • Improved documentation and examples

Bug fixes

New features

Incompatibilities

  • None expected

New Contributors

Full Changelog: pyat-0.3.0...pyat-0.4.0

@lfarv
Copy link
Contributor Author

lfarv commented Jun 7, 2023

Please have a look to the updated developer notes (for the release procedure) and to the release notes.
All comments are welcome.

@lfarv lfarv added the Python For python AT code label Jun 7, 2023
pyat/developers.rst Outdated Show resolved Hide resolved
pyat/developers.rst Outdated Show resolved Hide resolved
@lfarv
Copy link
Contributor Author

lfarv commented Jun 7, 2023

It would be nice to include #612, #613, #615 and #617 in the release: these are small changes. Any progress on that ?

pyat/developers.rst Outdated Show resolved Hide resolved
pyat/developers.rst Outdated Show resolved Hide resolved
The generated notes can now be copied and edited. You can then either cancel or
save the release as a draft while editing the release notes.

The ``## What's changed`` section should be splitted in ``## Bug fixes`` and
Copy link
Contributor

Choose a reason for hiding this comment

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

'splitted in' -> 'split into'

Are you suggesting having two top-level titles ('Bug fixes' and 'New features') only, or keeping What's Changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought that any modification would fall in either "bug fix" or "new feature", but one could think of other sections.
Any idea?

Copy link
Contributor

Choose a reason for hiding this comment

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

I was thinking 'split into' -> 'replaced with', to make it clear that the "What's Changed" heading is removed completely.

pyat/developers.rst Outdated Show resolved Hide resolved
pyat/developers.rst Outdated Show resolved Hide resolved
@lfarv
Copy link
Contributor Author

lfarv commented Jun 12, 2023

@swhite2401, @simoneliuzzo: any comment on the proposed release? do we postpone #613 and #615 to the next one or do you want to include them?

@swhite2401
Copy link
Contributor

@lfarv for me it is fine, at least #615 should go in. @simoneliuzzo is this ok for you? If you don't like the changes related to phase matching I can remove this part and keep it for the next one, but bug fixes should definitely go in.

@swhite2401
Copy link
Contributor

for #613 let's keep it for later, there is this phase issue that needs to be understood

pyat/developers.rst Outdated Show resolved Hide resolved
@lfarv
Copy link
Contributor Author

lfarv commented Jun 14, 2023

@swhite2401: Is this OK now to release 0.4.0 ? I included #613 and #615 in the release notes.
If you agree, can you approve this PR?

Copy link
Contributor

@swhite2401 swhite2401 left a comment

Choose a reason for hiding this comment

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

All ok for me!

@lfarv lfarv merged commit 99c483c into master Jun 16, 2023
31 checks passed
@lfarv lfarv deleted the release_0.4.0 branch June 16, 2023 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Python For python AT code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants