Add all the references to the Change record: [#2831499]
For more information about the original change see: https://www.drupal.org/project/drupal/issues/2248983

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ws6shawn created an issue. See original summary.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Janec’s picture

Hi, I'm @ drupalcon Vienna and about to try to help with this issue.

Janec’s picture

Status: Active » Needs review
Issue tags: +Vienna2017

Hi, there is only one deprecated private function. Since it is private nobody can use it outside of the class it self. The method is used only once on line 295. Is it worth documenting the necessary changes for this single usage?

tedbow’s picture

Status: Needs review » Active

@Janec thanks starting to this.

We don't want to create a separate issue for each file but for every change which may affect multiple files.. This @deprecated tag was added in #2248983: Define the revision metadata base fields in the entity annotation in order for the storage to create them only in the revision table which has 2 change record https://www.drupal.org/node/2831499 https://www.drupal.org/node/2870643

If there not already an issue for this we want to make sure that all @deprecated tags from that issue have @see tag pointing https://www.drupal.org/node/2831499

So we would also need to change the title of this issue to reflect the change record concept not an individual file.

There are 2 commits that mention #2248983: Define the revision metadata base fields in the entity annotation in order for the storage to create them only in the revision table : http://cgit.drupalcode.org/drupal/log/?qt=grep&q=2248983

Setting back to Active because there is not a patch yet.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Nikro’s picture

Title: Add Change record to @deprecated for View » Add Change record for Revision Metadata Base Fields change to Annotation
Issue summary: View changes
Status: Active » Needs review
Issue tags: +SprintWeekend2018
FileSize
1.12 KB

Hi,

We're working on this issue together with @mecmartini during the SprintWeekend2018.

We've analyzed the original changes in: https://www.drupal.org/project/drupal/issues/2248983 and noticed that we need to add 2 references to the change of record: [#2831499].

Patched attached below, also adjusted the title and description of the issue.

sk33lz’s picture

The #7 patch applies cleanly to 8.6.x.

borisson_’s picture

Status: Needs review » Reviewed & tested by the community

Looks solid.

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Crediting @time2buzzthetower for creating the issue, @tedbow for issue management and @mecmartini as according to #7 they worked on this too.

alexpott’s picture

+++ b/core/modules/views/views.post_update.php
@@ -206,6 +206,9 @@ function views_post_update_grouped_filters() {
+ * @todo Remove in Drupal 9.0.x.

This is not really required. All post updates will be cleared out during the preparation for Drupal 9 - like hook_update_N()'s. Fixed on commit.

Committed and pushed 951b4334fb to 8.6.x and 2be4ef6160 to 8.5.x. Thanks!

As docs change backported to 8.5.x.

  • alexpott committed 951b433 on 8.6.x
    Issue #2873860 by Nikro, time2buzzthetower, mecmartini, tedbow: Add...

  • alexpott committed 2be4ef6 on 8.5.x
    Issue #2873860 by Nikro, time2buzzthetower, mecmartini, tedbow: Add...
Anonymous’s picture

8000!!! You really are a legendary person, @alexpott!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.