From aa8a222544c0277694ac8a1ed38abbc94099fd59 Mon Sep 17 00:00:00 2001 From: Jeremy Herve Date: Fri, 9 Nov 2018 17:30:28 +0100 Subject: [PATCH] Changelog: prep for 6.7.1 (#10576) * Changelog: prepare for the next release. * changelog: prep for 6.7.1 * Changelog: add #10566 * changelog: add testing list. * changelog: add #10579 --- changelog.txt | 53 +++++++++++++++++++++++ readme.txt | 12 +++++- to-test.md | 116 ++++++-------------------------------------------- 3 files changed, 77 insertions(+), 104 deletions(-) diff --git a/changelog.txt b/changelog.txt index 345faa7ade838..c1d436a06faea 100644 --- a/changelog.txt +++ b/changelog.txt @@ -2,6 +2,59 @@ **This is a list detailing changes for all the past Jetpack releases. For more information about the current release, see [the readme](https://github.com/Automattic/jetpack/blob/master/readme.txt).** += 6.7 = + +* Release date: November 6, 2018 +* Release post: https://wp.me/p1moTy-aEq + +**Major Enhancements** + +* Site acceleration: new toggle to serve both your images and static files (like CSS and JavaScript) from our CDN. +* Activity: update Jetpack dashboard to include links to our Activity page, where you can view a record of every change and update on your site. + +**Enhancements** + +* Admin page: add site Activity card. +* Blocks: provide a mechanism so editor blocks can be translated. +* Blocks: enqueue Jetpack blocks in the block editor when blocks are available. +* Debug tools: add information about missing XML extension in self-help tools. +* REST API: introduce endpoint for retrieving related posts of a particular post. +* Search: add an advanced `excess_boost` param which can be adjusted with filters to fine tune query scoring. +* Sharing / Publicize: change the icons used in the Jetpack dashboard to clarify where the configuration links lead. +* Secure Sign On: update wording on admin pages to avoid confusion. +* Shortcodes: update the Polldaddy shortcode to use the new brand, Crowdsignal. +* Sitemaps: coding standards changes. +* Site Verification Tools: improve display of the tool's description on mobile devices. +* Unit Tests: improve process for faster tests. + +**Improved compatibility** + +* Themes: ensure compatibility between Jetpack features and the new WordPress default theme, Twenty Nineteen. +* AMP: add support for GitHub's Gist shortcodes. +* PHP 7.3: update Infinite Scroll to avoid PHP warnings when using the latest version of PHP. +* Protect: fix output of Protect's Math challenge on login forms created by third-party plugins. +* Plugins: add a WordPress.com themed plugins page for users managing their plugins via the WordPress.com interface. +* Site Verification Tools: do not enable Google's Auto-verification option when a site using a maintenance / coming soon plugin. + +**Bug fixes** + +* Blocks: update the VR block to be fully compatible with the latest version of WordPress and Gutenberg. +* Comment Likes: only prefetch domains used by the feature. +* CSS Concatenation: make sure all concatenated CSS is up to date. +* Featured Content: no longer hides the "featured" tag from the WordPress.com Editor or the mobile apps. +* Geolocation: avoid a PHP notice when setting location for a post in the WordPress.com post editor. +* Likes: ensure that the Likes column is accessible. +* REST API: Ensure only strings as escaped as URLs. +* Search: avoid PHP warning with Search widget. +* Sharing: improve accessibility of email sharing button. +* Simple Payments / Widget Visibility: avoid potential Fatal errors on some specific server configurations when updating Jetpack. +* Sitemaps: remove double encoding of site name in news sitemap. +* Sitemaps: ensure homepage is only included once. +* Sitemaps: provide richer "not found" message to site admins. +* Sitemaps: ensure sitemap is refreshed faster after upgrading Jetpack. +* Sitemaps: avoid protocol mismatches between the sitemaps and the site. +* Site Verification Tools: make sure we validate meta tags when saving. + = 6.6.1 = * Release date: October 10, 2018 diff --git a/readme.txt b/readme.txt index dcacb865f81fa..38344787031de 100644 --- 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, clickysteve, 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, jblz, jasmussen, jeffgolenski, jeherve, jenhooks, jenia, jessefriedman, jgs, jkudish, jmdodd, joanrho, johnjamesjacoby, jshreve, keoshi, koke, kraftbj, lancewillett, lschuyler, macmanx, martinremy, matt, matveb, mattwiebe, maverick3x6, mcsf, mdawaffe, MichaelArestad, migueluy, mikeyarce, mkaz, nancythanki, nickmomrik, obenland, oskosk, 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: 6.6.1 +Stable tag: 6.7 Requires at least: 4.8 Tested up to: 4.9 @@ -100,6 +100,16 @@ There are opportunities for developers at all levels to contribute. [Learn more == Changelog == += 6.7.1 = + +* Release date: November 14, 2018 +* Release post: https://wp.me/p1moTy-ceQ + +**Improved compatibility** + +* Spellcheck / Grammar: we've made sure the Jetpack feature did not create any error when using the block editor. +* Twenty Nineteen: ensure compatibility with Jetpack's widgets. + = 6.7 = * Release date: November 6, 2018 diff --git a/to-test.md b/to-test.md index 3662206ad66f7..2c38db00480d0 100644 --- a/to-test.md +++ b/to-test.md @@ -1,111 +1,21 @@ -## 6.7 +## 6.7.1 -### Block Editor +This release focuses on making Jetpack fully compatible with the Block Editor, also known as Gutenberg, that will be part of the new version of WordPress scheduled to be released on November 19th. -We've made numerous changes to the infrastructure that will provide Jetpack blocks to the new Block editor in WordPress. We've added a first block, for the Markdown feature. You can test it by going to Posts > Add New on your site after installing the Gutenberg plugin, or switching to WordPress 5.0 Beta. +To test this Beta, it's best to be running the latest Beta version of WordPress, 5.0 Beta 3 at the moment. You can also install the new default theme, Twenty Nineteen, to test our plugin's compatibility with this as well. -Try adding the module to your posts, use it, switch between editing and previewing, and let us know what you think about it. +To install the Twenty Nineteen theme on your site, start by downloading the latest version of the theme from [here](https://github.com/WordPress/twentynineteen/archive/master.zip). Unzip it, rename the folder to `twentynineteen`, rezip it, then upload and activate it on your site. -### Calypsoify +Once you are ready to start testing, we would recommend that you try the following actions: -If you are used to manage your site via the WordPress.com interface, you can now click on the "Plugins" link in Calypso and be redirected to a WordPress.com themed Plugins page in your site's dashboard (wp-admin). +- Activate different features, and deactivate others under Jetpack > Settings. +- Go to Posts > Add New, and ensure that you can publish new posts. +- Try updating old posts as well, and see that you can. +- Try adding some of [our shortcodes](https://jetpack.com/support/shortcode-embeds/) to your posts, and see that they work well. +- Try adding [the classic editor](https://wordpress.org/plugins/classic-editor/) plugin and see that there are no errors in the editor. +- Try publishing posts and see that Publicize and subscriptions still work. +- Try adding widgets to your site, and see that they look good with the Twenty Nineteen theme. -To test this change, try the following: - -**Pre-testing:** - -- You must have an active Jetpack connection -- Open/watch your browser console for errors. - -**Plugins:** - -- Visit `/wp-admin/plugins.php?calypsoify=1`: see the new skin -- Visit `/wp-admin/` with no params. Skin should be removed. Note: you can also click to go "back" to Calypso, and then when in Calypso, click "wp-admin". -- Repeat the above steps after collapsing the WordPress menu -- Repeat the above steps with multiple admin color schemes -- Install a few plugins that have settings pages and ensure that they are displaying properly when Claypsoified. -- Ensure that none of the .js or .css are loading when not Calypsoified in both the admin and front end. - -**Gutenberg:** - -- Install the Gutenberg plugin -- Visit `wp-admin/post-new.php?calypsoify=1` to view the Calypso skin -- You should not see the sidebar (It's meant to be a "full screen" experience) - -**RTL** - -- Enable an RTL language. -- Repeat the above testing instructions to ensure everything looks ok - -### Site accelerator - -In Jetpack 6.6 we started beta-testing a new Jetpack feature that allows you to serve a lot of CSS and JS files from the WordPress.com CDN instead of using your site's resources. In Jetpack 6.7, we're removing the Beta label and making that feature available to everyone! - -To test this, you can go to Jetpack > Settings > Writing in your dashboard and turn the feature on. - -- You can choose to speed up both images and static files, thus enabling the image CDN (formerly known as Photon) and the new feature. -- You can choose to only turn one of the features on. - -When turning on the file feature, you should see the following: - -1. All Jetpack's CSS and JS files are now served from a CDN, using the `c0.wp.com` domain. -2. All core WordPress CSS and JS files are also served from the CDN. -3. If you use the WooCommerce plugin on your site, its files should also benefit from the CDN. - -You can check your site's source code for that domain once you've activated the feature. - -### Shortcodes - -As you may know, [Polldaddy has changed its name to Crowdsignal](https://crowdsignal.com/2018/10/18/introducing-crowdsignal/). We are consequently updating the shortcode and embed methods available in Jetpack to match the new service. From now on, both the old embed methods and the new ones (using the new domains) should work. - -To test this, you can try adding polls and surveys to your site using both the old and the new domains. You can create new polls and surveys [here](https://polldaddy.com/dashboard/). Once you've done so, try inserting them into your posts using any of the methods available: -- By pasting an embed code with some JavaScript. -- By pasting a URL on its own line in the WordPress editor. -- By pasting a `[polldaddy]` or `[crowdsignal]` shortcode provided in the "Collect responses" area of your Crowdsignal dashboard. - -Try to replace polldaddy by crowdsignal in all the tests you make, and check that both the new and old domains work. - -We've also made some changes to [the Gist shortcode](https://en.support.wordpress.com/gist/) in this release. It should now be fully compatible with the AMP plugin. - -To test this, try installing the AMP plugin on your site (either the current Stable version or [the Beta](https://github.com/Automattic/amp-wp/releases/tag/1.0-RC1-built)), and try adding Gists, using different formats, to one of your posts. Here are some examples: - -```html -oEmbed: Full gist: - -https://gist.github.com/sebastianbenz/1d449dee039202d8b7464f1131eae449 - -oEmbed: Linking to a file via in a Gist: - -https://gist.github.com/sebastianbenz/1d449dee039202d8b7464f1131eae449#file-sw-html - -oEmbed: Linking to file without username in URL. - -https://gist.github.com/1d449dee039202d8b7464f1131eae449#file-sw-html - -Example from WordPress.com docs: - -[gist https://gist.github.com/2314628 /] - -Second example from WordPress.com docs: - -[gist]2314628[/gist] -``` - -### Sitemaps - -We've made multiple changes to the Sitemaps feature in this release. To test this: - -- Try visiting the Sitemaps right after upgrading. -- Try deactivating the sitemaps feature, activate it back, and then immediately visit the Sitemaps pages. -- Under Settings > Reading, set a static front page and a blog page, and check that they both appear in the sitemaps, without being duplicated. - -### Twenty Nineteen - -This release also includes support for the new default theme, Twenty Nineteen. To test, start by installing the latest version of the theme from [here](https://github.com/WordPress/twentynineteen/archive/master.zip). Then, try to use the following features: - -- Add Infinite Scroll support. -- Support for Responsive Videos. Test this by inserting videos in your posts and seeing them on mobile devices. -- Add Content Options support for author-bio, blog-display, post-details, and featured-images. You can see those settings under Appearance > Customize > Content Options. -- Style widgets and shortcodes to match the style of the theme. Try this by adding Jetpack widgets and shortcodes to your site. +**At any point during your testing, remember to [check your browser's JavaScript console](https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis) and see if there are any errors reported by Jetpack there.** **Thank you for all your help!**