Release 1.1.0 #262
Merged
Release 1.1.0 #262
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
@mottosso if I look at what's been written for all pre-releases since 1.0.0, this is quite a lot, but very informative. I'm thinking we could just copy-paste that in that chronological order and remove the pre-release numbers. What do you say? |
Collaborator
Author
|
Actually, we should take some time and write down what's clear in this release, as it is a big release. I've started a new release draft (doesn't seem like I can link to it from here). @mottosso could you complete the headers corresponding to your work? |
Collaborator
Author
|
I just added members which were added since 1.0.0 to the 1.1.0 release draft in https://github.com/mottosso/Qt.py/releases @mottosso these remain to be documented for the release:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's assemble what should be written in the release notes for 1.1.0.