WordPress 3.7 introduces automatic background updates<\/strong> for security and minor releases (like updating from 3.7 to 3.7.1). These are really easy to test \u00a0\u2014 RC 1 will update every 12 hours or so to the latest development version, and then email you the results. (You may get two emails: one for debugging, and one all users of 3.7 will receive.)\u00a0If something went wrong, you can report it.<\/p>\n Think you\u2019ve found a bug?\u00a0<\/strong>Please post to the\u00a0Alpha\/Beta area in the support forums<\/a>. If any known issues come up, you\u2019ll be able to\u00a0find them here<\/a>.<\/p>\n To test WordPress 3.7 RC1, try the\u00a0WordPress Beta Tester<\/a>\u00a0plugin (you\u2019ll want \u201cbleeding edge nightlies\u201d). Or you can\u00a0download the release candidate here<\/a>\u00a0(zip).\u00a0If you\u2019d like to learn more about what’s new in WordPress 3.7, visit the awesome About screen in your dashboard ( Developers,<\/strong>\u00a0please test your plugins and themes against WordPress 3.7, so that if there is a compatibility issue, we can figure it out before the final release. Make sure you post any issues to the support forums.<\/p>\n WordPress three seven<\/em> The first release candidate for WordPress 3.7 is now available! In RC 1, we’ve made some adjustments to the update process to make it more reliable than ever.\u00a0We hope to ship WordPress 3.7 next week, but we need your help to get there.\u00a0If you haven\u2019t tested 3.7 yet, there\u2019s no time like the present. (Please, […]<\/p>\n","protected":false},"author":5286302,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"episode_type":"","audio_file":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","date_recorded":"","explicit":"","block":"","filesize_raw":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5,14],"tags":[168],"class_list":["post-2718","post","type-post","status-publish","format-standard","hentry","category-development","category-releases","tag-3-7"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-HQ","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/2718","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/users\/5286302"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=2718"}],"version-history":[{"count":2,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/2718\/revisions"}],"predecessor-version":[{"id":2722,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/2718\/revisions\/2722"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=2718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=2718"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=2718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/i0.wp.com\/core.svn.wordpress.org\/branches\/3.6\/wp-content\/themes\/twentyten\/images\/wordpress.png?ssl=1\")
\u00a0\u2192 About<\/strong>\u00a0in the toolbar). There, you can also see if your install is eligible for background updates.\u00a0WordPress won\u2019t automatically update,\u00a0for example,\u00a0if you\u2019re using version control like Subversion or Git.<\/p>\n
\nA self-updating engine<\/em>
\nLies beneath the hood<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"