-
Notifications
You must be signed in to change notification settings - Fork 86
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
Match media testing guard and bug fix #470
Conversation
@@ -47,6 +47,17 @@ Changelog is rather internal in nature. See release notes for the public overvie | |||
|
|||
## Version 2.0.0 | |||
|
|||
- [#470] |
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.
Could you please move this istem to the "Upcoming version"?
The current items in the "Version 2.0.0" are already released. I will rename this section to "Version 2.0.0-beta0 (released)" to make it clearer. If you have some others ideas of what may help, let me know.
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.
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.
From my experience looking through dependency updates for many different JS packages - I have found the style of having changes only mentioned in alphas, betas, and rcs and not in the final release much more difficult to parse, especially when looking for breaking changes. I'd recommend not separating the changelog in this way, and see the beta releases as try outs for what the final release will be.
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.
That makes sense and will be ideal in the long term.
This is temporary only to help us now when we're in the transition towards re-introducing a stable release process. We already have beta with release notes so that we can start introducing and regression testing. Without them, it'd be difficult because we were postponing releases and accumulated lots of breaking changes. So release notes were created in advance and with that we will need to keep track for some time what other changes need to be eventually added.
This should get better with more frequent releases. With @marcellamaki and @thanksameeelian, we decided to cleanup the release notes from all betas and merge them for the final release as soon as it's ready so that should address it. On that occasion we can do one last changelog cleanup and merge all sections for v2.
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.
Alternatively, we could just add a comment to the changelog to indicate where the release notes end. I tried something like that already, but it seems it's hard to notice for devs. In any case, I'd be okay with any (shared) way of making it easier for us to track where the existing release notes end in the changelog, if you have any other ides.
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.
Will rebase now to move this.
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.
Thanks
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.
Code additions look correct to me. Thanks @rtibbles
d746c53
to
9814654
Compare
Updated! |
I wanted to note that I only jumped in to notify about changelog, but didn't review myself. If there is anything needed from my side, let me know. |
so that we do actually unbind our previously bound listeners.
9814654
to
75e1515
Compare
Rebased again to resolve the CHANGELOG merge conflict. At the risk of sounding needy, I do need approval - the changes are fairly straight forward so would be a quick review. |
I skimmed it too now and haven't noticed anything blocking. Leaving only one minor note. |
- **Description:** Fix bug and add test guard in MediaQuery implementation | ||
- **Products impact:** none | ||
- **Addresses:** - | ||
- **Components:** none |
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.
Just a note that here, all affected components would ideally be included here even though it doesn't modify them directly, it's something that's used under the hood (this will help with 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.
No need to do anything about it, I already prepared the release notes for this item too. Just jumping into PRs and using them as spreading the word.
@@ -6,6 +6,17 @@ Changelog is rather internal in nature. See release notes for the public overvie | |||
|
|||
<!-- All new changelog items should come here --> | |||
|
|||
- [#470] | |||
- **Description:** Fix bug and add test guard in MediaQuery implementation | |||
- **Products impact:** none |
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.
Description
Issue addressed
Fixes failing tests seen in develop on Kolibri
Fixes unreported bug that would stop listeners from being unbound
Testing checklist
changelog