-
Notifications
You must be signed in to change notification settings - Fork 31
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
Release 0.4.0 #616
Conversation
Please have a look to the updated developer notes (for the release procedure) and to the release notes. |
pyat/developers.rst
Outdated
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 |
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.
'splitted in' -> 'split into'
Are you suggesting having two top-level titles ('Bug fixes' and 'New features') only, or keeping What's Changed?
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.
I thought that any modification would fall in either "bug fix" or "new feature", but one could think of other sections.
Any idea?
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.
I was thinking 'split into' -> 'replaced with', to make it clear that the "What's Changed" heading is removed completely.
for describing the procedure to release a new version
@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? |
@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. |
for #613 let's keep it for later, there is this phase issue that needs to be understood |
@swhite2401: Is this OK now to release 0.4.0 ? I included #613 and #615 in the release notes. |
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.
All ok for me!
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:
refpts
to string patterns, regular expressions,None
,All
,End
special valuesBug fixes
New features
Incompatibilities
New Contributors
Full Changelog: pyat-0.3.0...pyat-0.4.0