Community Events: Update timezone-related `@since` tags to `5.5.2`.

r49145 and r49146 were originally planned for 5.6 when they were committed, but are now planned for 5.5.2.

See #51130.

Built from https://develop.svn.wordpress.org/trunk@49152


git-svn-id: http://core.svn.wordpress.org/trunk@48914 1a063a9b-81f0-0310-95a4-ce76da25c4cd

wp-admin/includes/class-wp-community-events.php

@@ -77,7 +77,7 @@ class WP_Community_Events {
 	 * mitigates possible privacy concerns.
 	 *
 	 * @since 4.8.0
-	 * @since 5.6.0 Response no longer contains formatted date field. They're added
+	 * @since 5.5.2 Response no longer contains formatted date field. They're added
 	 *              in `wp.communityEvents.populateDynamicEventFields()` now.
 	 *
 	 * @param string $location_search Optional. City name to help determine the location.
@@ -345,7 +345,7 @@ class WP_Community_Events {
 	 * Gets cached events.
 	 *
 	 * @since 4.8.0
-	 * @since 5.6.0 Response no longer contains formatted date field. They're added
+	 * @since 5.5.2 Response no longer contains formatted date field. They're added
 	 *              in `wp.communityEvents.populateDynamicEventFields()` now.
 	 *
 	 * @return array|false An array containing `location` and `events` items
@@ -377,7 +377,7 @@ class WP_Community_Events {
 	protected function format_event_data_time( $response_body ) {
 		_deprecated_function(
 			__METHOD__,
-			'5.6.0',
+			'5.5.2',
 			'This is no longer used by Core, and only kept for backwards-compatibility.'
 		);
 
@@ -451,7 +451,7 @@ class WP_Community_Events {
 	 *
 	 * @since 4.8.0
 	 * @since 4.9.7 Stick a WordCamp to the final list.
-	 * @since 5.6.0 Accepts and returns only the events, rather than an entire HTTP response.
+	 * @since 5.5.2 Accepts and returns only the events, rather than an entire HTTP response.
 	 *
 	 * @param array $events The events that will be prepared.
 	 * @return array The response body with events trimmed.

wp-admin/js/dashboard.js

@@ -623,7 +623,7 @@ jQuery( function( $ ) {
 		 * These can't be stored in the database, because they're dependent on
 		 * the user's current time zone, locale, etc.
 		 *
-		 * @since 5.6.0
+		 * @since 5.5.2
 		 *
 		 * @param {Array}  rawEvents  The events that should have dynamic fields added to them.
 		 * @param {string} timeFormat A time format acceptable by `wp.date.dateI18n()`.
@@ -658,7 +658,7 @@ jQuery( function( $ ) {
 		/**
 		 * Returns the user's local/browser time zone, in a form suitable for `wp.date.i18n()`.
 		 *
-		 * @since 5.6.0
+		 * @since 5.5.2
 		 *
 		 * @param startTimestamp
 		 *
@@ -693,7 +693,7 @@ jQuery( function( $ ) {
 		 *
 		 * See https://stackoverflow.com/questions/21102435/why-does-javascript-date-gettimezoneoffset-consider-0500-as-a-positive-off.
 		 *
-		 * @since 5.6.0
+		 * @since 5.5.2
 		 *
 		 * @param {number} startTimestamp
 		 *
@@ -706,7 +706,7 @@ jQuery( function( $ ) {
 		/**
 		 * Get a short time zone name, like `PST`.
 		 *
-		 * @since 5.6.0
+		 * @since 5.5.2
 		 *
 		 * @param {number} startTimestamp
 		 *
@@ -748,7 +748,7 @@ jQuery( function( $ ) {
 		/**
 		 * Format a start/end date in the user's local time zone and locale.
 		 *
-		 * @since 5.6.0
+		 * @since 5.5.2
 		 *
 		 * @param {int}    startDate   The Unix timestamp in milliseconds when the the event starts.
 		 * @param {int}    endDate     The Unix timestamp in milliseconds when the the event ends.

wp-includes/version.php

@@ -13,7 +13,7 @@
  *
  * @global string $wp_version
  */
-$wp_version = '5.6-alpha-49151';
+$wp_version = '5.6-alpha-49152';
 
 /**
  * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.