Problem/Motivation

Other issues have established standards for configuration files and filenames.
Can find by searching for issues and change records.
But should be all in one place.

Proposed resolution

Document already decided things in a coding standard page.
https://www.drupal.org/node/2315769

Remaining tasks

find the related issues and change records and link to them here and/or when updating the doc page in the revision log.

Related issues and change records and other things to aggregate

User interface changes

No.

API changes

No.

Comments

YesCT’s picture

YesCT’s picture

Issue summary: View changes

linking to the new standard page in the summary

YesCT’s picture

Issue summary: View changes
YesCT’s picture

should probably sort the related issues into a set that is obselete and the still valid ones.

jhodgdon’s picture

I'm really not sure how much we need to document on that page.

I mean, people should really not be writing out config files in their editor, should they, at least for the final config they check into their git repo or put in a patch? That should be written out by Drupal.

There is already docs about the config file syntax in the Config API pages that I linked to in that page header.

The standards for name lengths and file names I put in there are also important.

But I think we can probably get rid of the rest, or maybe replace it with something like:

To write initial configuration for your module, entity, etc., here's a link to the docs page on the YAML structure, and you also need to make a schema file, so here's a link for that. But when you make your config file to go into the install directory of your module, you should export it using the Config Export screen.

Thoughts? [not suggesting this wording obviously!]

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.