Remove versionadded / versionchanged notes for 6.2

However, leave behind notes that mark settings/features that are deprecated but not yet removed, as this would be removing information that isn't in the main body of the text (and moving it out of a versionchanged note would make it harder to find when we come to remove it properly in 7.0).

docs/advanced_topics/customisation/custom_user_models.md

@@ -95,10 +95,6 @@ be redefined.
 
 ## Creating a custom `UserViewSet`
 
-```{versionadded} 6.2
-The ability to customize the `UserViewSet` was added.
-```
-
 To make use of the custom forms, create a `UserViewSet` subclass.
 
 ```python
@@ -158,8 +154,4 @@ class UserViewSet(WagtailUserViewSet):
     edit_template_name = "myapp/users/edit.html"
 ```
 
-```{versionchanged} 6.2
-The [`WAGTAIL_USER_EDIT_FORM`, `WAGTAIL_USER_CREATION_FORM`, and `WAGTAIL_USER_CUSTOM_FIELDS` settings](user_form_settings) have been deprecated in favor of customizing the form classes via `UserViewSet.get_form_class()`.
-```
-
 The group forms and views can be customized in a similar way – see [](customizing_group_views).

docs/extending/adding_reports.md

@@ -56,11 +56,6 @@ The listing table should be implemented in a separate template specified by ``re
 Unless you want to customize the overall view, you will rarely need to change this template.
 To customize the listing, change the ``results_template_name`` instead.
 
-.. versionchanged:: 6.2
-   The default ``template_name`` attribute for ``PageReportView`` was changed from ``"wagtailadmin/reports/base_page_report.html"`` to ``"wagtailadmin/reports/base_report.html"``.
-
-   Additionally, customization of the ``template_name`` should generally be replaced with a ``results_template_name`` customization, unless you intend to completely override the view template and not just the listing table.
-
 .. attribute:: results_template_name
 
 (string)
@@ -73,9 +68,6 @@ which provides a default table layout based on the explorer views,
 displaying action buttons, as well as the title, time of the last update, status, and specific type of any pages.
 In this example, we'll change this to a new template in a later section.
 
-.. versionadded:: 6.2
-   The ``results_template_name`` attribute was added to support updating the listing via AJAX upon filtering and to allow the use of the ``wagtail.admin.ui.tables`` framework.
-
 .. attribute:: page_title
 
 (string)
@@ -83,9 +75,6 @@ In this example, we'll change this to a new template in a later section.
 The name of your report, which will be displayed in the header. For our example, we'll set it to
 ``"Pages with unpublished changes"``.
 
-.. versionchanged:: 6.2
-   The ``title`` attribute was renamed to ``page_title``.
-
 .. attribute:: header_icon
 
 (string)
@@ -105,9 +94,6 @@ The name of the URL pattern registered for the report view.
 
 The name of the URL pattern registered for the results view (the report view with ``.as_view(results_only=True)``).
 
-.. versionadded:: 6.2
-   The ``index_results_url_name`` attribute was added to support updating the listing via AJAX upon filtering.
-
 ```
 
 ## Spreadsheet exports
@@ -161,10 +147,6 @@ preprocessing, set the preprocessing_function to ``None``.
 
 For this example \"pages with unpublished changes\" report, we'll add an extra column to the listing template, showing the last publication date for each page. To do this, we'll extend two templates: `wagtailadmin/reports/base_page_report_results.html`, and `wagtailadmin/reports/listing/_list_page_report.html`.
 
-```{versionchanged} 6.2
-Extending `wagtailadmin/reports/base_page_report.html` was changed in favor of extending `wagtailadmin/reports/base_page_report_results.html`. The `listing` and `no_results` blocks were renamed to `results` and `no_results_message`, respectively.
-```
-
 ```html+django
 {# <project>/templates/reports/unpublished_changes_report_results.html #}
 

docs/reference/hooks.md

@@ -429,10 +429,6 @@ def user_listing_external_profile(user, request_user):
         )
 ```
 
-```{versionchanged} 6.2
-The hook function was updated to accept a `request_user` argument instead of `context`.
-```
-
 (filter_form_submissions_for_user)=
 
 ### `filter_form_submissions_for_user`