-
Notifications
You must be signed in to change notification settings - Fork 383
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
Add PRs and issues from the 1.0 milestone to the changelog #1189
Conversation
Mainly use PRs, except where there was extensive discussion on an issue. Most entries don't list the corresponding issue for a pull request. This is in reverse-chronological order. And it goes from the bottom up: https://github.com/Automattic/amp-wp/milestone/7?closed=1
Before, I had paraphrased some PR titles in the changelog. Other edits include wrapping HTML elements in `
To improve the dispaly in Markdown. Also, remove 'Gutenberg' from 'Gutenberg blocks.' It sounds like that name won't be present once it's merged into Core.
@kienstra instead of sorting in reverse chronological order, could they be generally sorted by importance? What I have in mind is something similar to the “what's new” posts for Gutenberg, for example: https://make.wordpress.org/core/2018/05/18/whats-new-in-gutenberg-18th-may/ |
Sounds good, @westonruter. I'll sort these by order of importance, like in the Gutenberg post you mentioned. |
With their relative importance in mind. Of course, this is subjective.
Hi @westonruter, |
Hey @kienstra, this makes my job easier and looks better than before! Thanks for this! 🎆 |
…n forced by filter Fix notice of trying to get property of non-object
…sanitization impact term status
Request For Review
Hi @westonruter,
Could you please review this update to the Changelog?
https://github.com/Automattic/amp-wp/milestone/7?closed=1
1.0
. Maybe we could do that for the production release.Closes #1108.