Changelog 5.6: running changelog. (#8192)

* Changelog 5.6: create base for changelog. * Update changelog with 5.5.1 info. * Changelog: add #7930 and #8238 * Changelog: add #8076 * Changelog: add #8100 * Changelog: add #8117 * Changelog: add #8141 * Changelog: add #8143 * Changelog: add #8147 * Changelog: add #8149 * Changelog: add #8153 * Changelog: add #8173 * Changelog: add #8184 * Changelog: add #8196 * Changelog: add #8199 * Changelog: add #8093 * Changelog: add #8171 * Changelog: add #8182 * Changelog: add #8202, #8222 * Changelog: add #8228 * Changelog: add #8240 * Changelog: add #8251 * remove AL card change
Automattic · Nov 28, 2017 · 7844644 · 7844644
1 parent e5fd42f
commit 7844644
Show file tree

Hide file tree

Showing 3 changed files with 79 additions and 27 deletions.
diff --git a/changelog.txt b/changelog.txt
@@ -1,5 +1,19 @@
 == Changelog ==
 
+= 5.5.1 =
+
+* Release date: November 21, 2017
+* Release post: https://wp.me/p1moTy-6Bd
+
+**Bug fixes**
+* In Jetpack 5.5 we made some changes that created errors if you were using other plugins that added custom links to the Plugins menu. This is now fixed.
+* We have fixed a problem that did not allow to upload plugins using API requests.
+* Open Graph links in post headers are no longer invalid in some special cases.
+* We fixed warnings happening when syncing users with WordPress.com.
+* We updated the way the Google+ button is loaded to match changes made by Google, to ensure the button is always displayed properly.
+* We fixed conflicts between Jetpack's Responsive Videos and the updates made to Video players in WordPress 4.9.
+* We updated Publicize's message length to match Twitter's new 280 character limit.
+
 = 5.5 =
 
 * Release date: November 7, 2017

diff --git a/readme.txt b/readme.txt
@@ -1,7 +1,7 @@
 === Jetpack by WordPress.com ===
 Contributors: automattic, adamkheckler, aduth, akirk, allendav, alternatekev, andy, annezazu, apeatling, azaozz, batmoo, barry, beaulebens, blobaugh, cainm, cena, cfinke, chaselivingston, chellycat, csonnek, danielbachhuber, davoraltman, daniloercoli, designsimply, dllh, drawmyface, dsmart, dzver, ebinnion, eliorivero, enej, eoigal, erania-pinnera, ethitter, gcorne, georgestephanis, gibrown, goldsounds, hew, hugobaeta, hypertextranch, iammattthomas, iandunn, jacobshere, jblz, jeherve, jenhooks, jenia, jgs, jkudish, jmdodd, Joen, johnjamesjacoby, jshreve, koke, kraftbj, lamdayap, lancewillett, lschuyler, macmanx, martinremy, matt, matveb, mattwiebe, maverick3x6, mcsf, mdawaffe, michael-arestad, migueluy, mikeyarce, mkaz, nancythanki, nickmomrik, obenland, pento, professor44, rachelsquirrel, rdcoll, ryancowles, richardmuscat, richardmtl, roccotripaldi, samhotchkiss, scarstocea, sdquirk, stephdau, tmoorewp, tyxla, Viper007Bond, westi, yoavf, zinigor
 Tags: Jetpack, WordPress.com, backup, security, related posts, CDN, speed, anti-spam, social sharing, SEO, video, stats
-Stable tag: 5.5
+Stable tag: 5.5.1
 Requires at least: 4.7
 Tested up to: 4.9
 
@@ -103,6 +103,37 @@ There are opportunities for developers at all levels to contribute. [Learn more
 
 == Changelog ==
 
+= 5.6 =
+
+* Release date: December 5, 2017
+* Release post: https://wp.me/p1moTy-6zt
+
+**Major Enhancements**
+* Google Analytics: Add support for universal analytics for WooCommerce.
+* Performance: minify all JavaScript files used in the plugin.
+* Performance: add new Lazy Images module.
+* Protect: add new mechanism allowing you to send yourself an email with a link to the form when you are locked out of your site.
+
+**Enhancements**
+* Custom CSS: add new set of font properties that can be used in the CSS editor.
+* Photon: do not remove `width` and `height` attributes from image tags when known.
+* Sitemaps: add CLI commands to purge and built the sitemaps.
+* Sitemaps: only display the reporter log success messages if `JETPACK_DEV_DEBUG` is defined.
+* WordPress.com API: add new endpoints to allow for better comment management in third party interfaces like WordPress.com.
+* WordPress.com Toolbar: prevent dns prefetching for logged out users.
+
+**Improved compatibility**
+* Stats: remove function deprecated in PHP 7.2.
+
+**Bug fixes**
+* Comment Likes: make sure Like text is properly translated.
+* General: only load stats code when necessary.
+* Related Posts: allow site owners to exclude multiple blog posts from the list of Related Posts.
+* Sharing: remove inline JavaScript used in the email sharing form.
+* Search: Maintain ordering of the search filters in the widget.
+* Sync: avoid PHP notices during the synchronization process.
+* WordPress.com Toolbar: avoid broken link when using the sign out button.
+
 = 5.5.1 =
 
 * Release date: November 21, 2017

diff --git a/to-test.md b/to-test.md
@@ -1,43 +1,50 @@
-## 5.5
+## 5.6
 
-### Connection process
+### Google Analytics
 
-We made some changes to reduce the number of connection issues that may happen on a site when switching from HTTP to HTTPs. To test this, if your site uses HTTPs, make sure you can still interact with your site via WordPress.com (try publishing or editing posts for example), and check to see that things like Related Posts still work on your site.
+Jetpack Professional customers using the WooCommerce plugin and needing some in-depth Google Analytics reports will be happy with this release. We've added support for universal analytics to Jetpack in this release. To test this new feature, follow the instructions [in this PR](https://github.com/Automattic/jetpack/pull/8182).
 
-We have also improved the connection process to make sure other plugins can't interfere with the connection. To test this, try the following:
+### Lazy images
 
-1. Start with a disconnected site and user, and multiple other plugins active. If you'd like, you can use [jurassic.ninja](https://jurassic.ninja/) to get a brand new site quickly.
-2. Visit the dashboard and confirm that the Connect button has an appropriate URL and that you can connect
-3. After connecting, login in with a non-admin user and confirm that the banner button that reads "Connect to WordPress.com" works and has a good href.
-4. Confirm that you can cycle the connection. Connect Jetpack, get back to the admin page. Disconnect, and try to connect again without refreshing the page.
+We've added a new module, Lazy Images, to improve page load times by only loading an image when it is visible in the viewport.
 
-### Carousel
+To test, try the following:
 
-We have made some performance improvements to the Carousel feature. It would be great if everyone could test every aspect of Carousel in this release:
-- Does it work well on single images when the image is set to link to an attachment page?
-- Does it work well with standard WordPress galleries?
-- Does it work well with Tiled Galleries?
-- Are you able to comment on a Carousel image, whether you are logged in or logged out of your WordPress account?
+1. Go to `https://yoursite.com/wp-admin/admin.php?page=jetpack_modules` and enable the "Lazy Images" module.
+2. Visit pages when you have inserted single images, galleries, slideshows. You'll want to test this on pages where the images are at the top of the page, but also on pages where you have to scroll to see the images. You will want to make sure that images get loaded as you scroll down the page, and that [no JavaScript error appears in your browser console](http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors).
+3. Try in as many browsers as possible.
 
-### Custom CSS
+### Photon
 
-The next version of WordPress, 4.9, will be released very soon and will include [a lot of changes to its code editors](https://make.wordpress.org/core/2017/10/22/code-editing-improvements-in-wordpress-4-9/). As part of those changes, the CSS editor will now have its own syntax highlighter. Until now, there was no syntax highlighting in the CSS editor unless you used Jetpack and its Custom CSS module.
+Until now, when filtering content, Photon removed `width` and `height` attributes from image tags. This was done to make sure images were never distorted, regardless of how they were inserted in a post.
 
-You will consequently want to test 4 things:
-- What happens when you use the current version of WordPress (4.8.2) with the new version of Jetpack? Does syntax highlighting still work? Can you save CSS changes?
-- What happens when you then use [this plugin](https://wordpress.org/plugins/wordpress-beta-tester/) to update WordPress to the 4.9 Beta version on your site? Does your CSS remain? Are there any issues during the migration? I would suggest to try this update after having added a lot of CSS to the editor.
-- What happens when you use the CSS editor with WP 4.9 Beta? Does syntax highlighting work well?
-- Does everything work regardless of whether the Custom CSS module is active or not?
+We've now improved this process and avoid removing those attributes when we can. To test, try inserting images in test posts. Use multiple methods to insert your images: slideshows, galleries, custom (non Jetpack) galleries, single images, images hosted somewhere else. You will want to make sure no image gets distorted, and that the `width` and `height` attributes are there. Ensure that you're "viewing source" to check this as opposed to using your browser's dev tools.
 
-### Gallery Widget
+### Protect
 
-The next version of WordPress will now include its own [Gallery Widget](https://make.wordpress.org/core/2017/09/25/introducing-the-gallery-widget/). If you previously used a Jetpack Gallery Widget on your site, that widget will disappear and will be replaced by the new WordPress gallery widget.
+We've created a new setting one can use to change the default WordPress log in form, and add a new field with an option to send yourself an email with a link to log in when you got locked out of your site.
 
-To test this, start by adding a Jetpack Gallery Widget on your site, Then, update to WordPress 4.9 Beta. You can use [this plugin](https://wordpress.org/plugins/wordpress-beta-tester/) to update WordPress on your site. Once you have done so you should see the new WordPress widget under Appearance > Widgets and Appearance > Customize. Try to use one the Tiled Gallery types, and make sure it is displayed properly.
+Follow the instructions below to test the feature:
 
-### Misc
+1. Set the following constant in your `wp-config.php`: `define( 'JETPACK_ALWAYS_PROTECT_LOGIN', true );`
+2. Now when you go to wp-login.php you will be asked to enter an email.
+3. After receiving the email you should be able to login again or change your password.
+4. The token that you get in the email is only valid for 15 minutes.
 
-- [Always] Try to connect with a brand new site, and also cycle your connections to existing sites.
+### Shortcodes
+
+In this release we started using minified JavaScript files for all the shortcodes that rely on JavaScript in the plugin. You will consequently want to try testing the following shortcodes:
+- Brightcove
+- Gist
+- Instagram
+- Presentations
+- Quizzes
+- Recipes
+- Slideshows
+
+You can find instructions on how to use each shortcode [here](https://jetpack.com/support/shortcode-embeds/).
+
+For each shortcode, you will want to make sure they work as expected, and that [no JavaScript error appears in your browser console](http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors).
 
 ### Final Notes