Update CHANGELOG.txt for the release (compile list of high level changes)

What is the qualification for something to be included?

First line has the tpl.php conversions. We could add that all theme functions have been converted, as well. Also, the addition of Classy and Stable.

There are some new modules missing, like the menu link change and the caching ones?

* Added PHPUnit for proper unit testing, see https://phpunit.de/manual/4.8/en/index.html so you can run tests via your IDE
* Added BrowserTestBase as an alternative to simpletest for browser testing (Javascript included in the future)
* Added KernelTestBase to provide a fast API testing of integration of different components

Added responsive images

Added a bit more around the symfony components.

+++ b/core/CHANGELOG.txt
-- Added Twig as the default template engine and converted all .tpl.php templates
+    * Added the Stable theme to be used as base theme.

I think we should note that this is the default base theme. "used as the default base theme." maybe.

As for other frontend changes, here are some in no particular order (just numbered for discussion purposes). Not sure the level of detail we want, feel free to reject some of these as too granular:

1. Removed the template process layer
2. New, completely overhauled asset library system for CSS and JavaScript
3. New CSS architecture and standards
4. Theme suggestions API moved out of preprocess into its own hooks
5. Consistent use of render arrays rather than the theme() function
6. New Attribute object that can be manipulated from within templates
7. show() and hide() in templates removed in favor of a |without Twig filter
8. Removed most support for versions of Internet Explorer lower than 9

Edited to make one addition.

Missed an important one:

All page variables (title, tabs, etc.) converted to blocks

* Modernizr has been added that allows us to make styling changes based on browser support.

Added some frontend changes.

Nope. I wasn't sure if they really needed to be included, due to the granularity, or how to describe them properly so I left them out. Low hanging fruit I suppose.

I'm not suggesting including all the things, but we might look at these places to get inspired/reminded of things to put in the change log

general things from the front page of https://api.drupal.org/api/drupal/8
closed fixed major and critical feature requests https://www.drupal.org/project/issues/search/drupal?project_issue_follow...

modules removed https://www.drupal.org/node/2116417
modules added https://www.drupal.org/node/2164623

I think change records are a new thing since 8.x started.
The changelog.txt file should mention https://www.drupal.org/list-changes/drupal
and maybe describe a bit of what the difference is there vs the changelog.txt file.

- Removed backwards-compatibility with 'magic_quotes_gpc'/'magic_quotes_runtime'
PHP configuration settings. Both are required to be disabled.

Needs to be removed as we require PHP 5.4.0 and that version nuked these two

yeah.

also, I think we can remove
"Drupal 8 can no longer be installed on hosts with the 'magic_quotes_gpc', 'magic_quotes_runtime', or 'safe_mode' PHP ini settings turned on; these settings are deprecated in PHP 5.3 and have no effect anymore in PHP 5.4 and higher."
from
https://www.drupal.org/requirements/php#8
since d8 requires a min php version of 5.5.9 anyway ( https://www.drupal.org/requirements )

I have tested all PHP 7 RC releases so far. I haven't found any problems on D8 yet.

• Added support for saving and deleting entities through the controller. - Instead "Full CRUD API for entities." something about complete with a field API and a more fleshed out query API.
• The revision paragraph is way too long
• Replaced the core routing system with one built on the Symfony2 framework. - That is incorrect, maybe supplemented or simply use the word "ruined". It was not replaced fully anyways: the only thing keeps it even remotely performant is the same database architecture underneath. Symfony2 could not perform its way out of a wet paper bag.
• The configuration section says nothing about import and export which is the most important part
• ClassLoader - PSR-0-compatible autoload routines. - maybe we added this but do we use it? I thought we use the Composer autoloader. The typehint on the classloader in DrupalKernel corroborates such belief.
• Support added for making HTTP requests through a proxy server. - Nuke this, it was added in 2012, it talks about drupal_http_request which was replaced by Guzzle. Do mention adding Guzzle, however.
• Mention typed data.
• Mention config entities and block placement entities most especially. Same block, multiple times, how many people turned to panels for this.
• Even if it's experimental, migrate mentions a blip.

Some ux changes worth calling out:

Shiny new installer
Redesigned content creation form
Updated and extended Seven admin theme
Responsive admin toolbar

Drupal does not load automatically any (vendor) library (eg. jQuery) for better performance.

I'd highlight the fact that we support Composer. It's usually a big deal to external developers.

Once #2608174: Update composer-merge-plugin to latest version lands, we will be able to use Composer not just to download libraries, but also Drupal modules, with no additional tools (other than adding the Drupal Packagist repository). That's a very big workflow improvement/change.

+- Dramatically improved the frontend

It's not dramatic. Are you American? :-)

Should "Phone number" be called "Telephone number"?

Added some stuff I'm proud of contributing to that we'd not covered.

typo

Suggestions:

1. HTML Attributes are now self printed objects
2. Auto-escaping template variables
3. Branding variables, menus and system messages are now blocks

And yes @MustangGB it should be because that is the name of the module, good idea.

• Improved punctuation/consistency.
• Added a few clarifications
• Expanded the "CKEditor added" line into an "improved authoring experience" section with some more high-level bullets, including in-place editing.

EDIT: includes #26.

• Added a few clarifications/improvements.
• Added a "Performance" section.

Crosspost with Wim...

A sandbox for just that could be actually useful.

Expanded the views section a bit.

Its certainly on needs review ...

Found some nits and things. Great to see all this in one place :)

As for collaboration maybe something like an etherpad or google doc? ¯\_(ツ)_/¯

1. +++ b/core/CHANGELOG.txt
   -- Added Twig as the default template engine and converted all .tpl.php templates
   +- Dramatically improved the front end
   

   Nit: This should end in a period or colon or some kind of punctuation.

2. +++ b/core/CHANGELOG.txt
   -- Replaced the core routing system with one built on the Symfony2 framework.
   +- Refactored routing system based Symfony2 components.
   

   based = based on?

3. +++ b/core/CHANGELOG.txt
   -- Replaced the core routing system with one built on the Symfony2 framework.
   +- Reworked Menu links / Local actions and tasks based upon the new routing
   

   Why are Menu and Local capitalized here?

4. +++ b/core/CHANGELOG.txt
   -- Included the HTML5 Shiv library to support HTML5 elements in IE 8 and below.
   +    * Supports configuration schema, dependencies and validation to maintain
   

   Add an oxford comma here before the "and" - "schema, dependencies, and validation"

5. +++ b/core/CHANGELOG.txt
   -- Included the HTML5 Shiv library to support HTML5 elements in IE 8 and below.
   +      but also blockquotes, code snippets, videos…
   

   I would suggest removing "but also" and replacing it with a comma but maybe that's just me.

6. +++ b/core/CHANGELOG.txt
   @@ -28,10 +74,14 @@ Drupal 8.0, xxxx-xx-xx (development version)
   +    * Serialization - Allows to serialize complex nested objects into JSON/XML
   ...
   +    * Validator - Allows to ensure that an object is in a valid state based upon
   

   In both cases I think these would read better if "Allows to" was removed.

7. +++ b/core/CHANGELOG.txt
   -- Support added for making HTTP requests through a proxy server.
   +- Added routing component from Symfony CMF.
   

   Is there duplication here? Routing based on Symfony2 components is mentioned above… just checking.

8. +++ b/core/CHANGELOG.txt
   -- Added Date field type to core.
   +  * REST api support built in.
   

   s/api/API/

9. +++ b/core/CHANGELOG.txt
   -- Added Date field type to core.
   +  * Rewritting caching integration for better performance.
   

   s/Rewritting/Rewrote/

   Typo in the first place, but present tense doesn't seem to make much sense here to me.

10. +++ b/core/CHANGELOG.txt
    -- Added Date field type to core.
    +- Custom blocks are now fieldable, revisionable and translatable entities.
    

    Should have a comma before "and" again, see https://www.drupal.org/drupalorg/style-guide/content.

11. +++ b/core/CHANGELOG.txt
    -- Added Date field type to core.
    +- An accessible modal API based on improvements made in collaboration with
    +  jQuery UI team and the Views UI.
    

    "the jQuery UI team" I think, and then maybe just "the Views team"? If it's not the Views team I think this sentence could use some rethinking because it sounds like "the Views UI" is a group of people which would be odd :).

12. +++ b/core/CHANGELOG.txt
    -- Added Date field type to core.
    +  for soliticing feedback from users.
    

    s/soliticing/soliciting/

13. +++ b/core/CHANGELOG.txt
    -- Added Date field type to core.
    +      testing (Javascript support to be included in the future)
    

    s/Javascript/JavaScript/

I'm OK with multiple commits from here, let's address #39 first though then get what we have in?

Then we can keep going for #41 onwards?

Multiple commits does sound better. Here's everything from #39 but #39.7, left as is because I'm not sure if it's duplication or not.

I do agree with @joelpittet in #32 that the Attribute thing is worth mentioning, and probably autoescape too. We already have the blocks stuff covered:

* All page template variables converted to blocks.

Oh I missed this, stray bullet point got introduced somewhere.

Committed/pushed #45.

Back to 'active' for more updates.

Feel free to include #29.

+1 for the approach to improve things over time!

Nice consolidation @Gábor Hojtsy. Likely big enough for an commit iteration, though I'll give it more than 15 min;)

added security section based on chat in #drupal-security and using https://dev.acquia.com/blog/drupal-8/10-ways-drupal-8-will-be-more-secur... for some inspiration

Is it worth mentioning that a lot of declarative information (libraries, permissions, routes etc.) has been moved from PHP to YAML?

Statistics module view counting works with the page cache and reverse proxies now.

1.  Drupal 8.0.x, xxxx-xx-xx (development version)
    ----------------------
   

   Can we add two extra "-" here so it's even with the line above? :) (We actually just fixed that throughout CHANGELOG.txt not too long ago.)

2.  Drupal 8.0.x, xxxx-xx-xx (development version)
    ----------------------
   +
   +The following is a list of the most important changes made to Drupal in 8.0.0.
   +For a detailed list of changes with background information, see
   +https://www.drupal.org/list-changes/drupal
   

   This is out of place here. If it belongs in CHANGELOG.txt, it should be in an intro section at the top of the file or something like that (not in the Drupal 8.0.0 section). It seems like a good idea though.

3. +    * Removed the Overlay module from core but kept the functionality with a
   +      simple but dynamic "Back to site" link.
   

   This is confusing... I think maybe it's trying to say: 'Removed the Overlay module from core and replaced it with a simple, dynamic "Back to site" link.'

4. +    * Redesigned icons to look good on high resolution (retina) displays too.
   

   Remove "too".

5. +    * Completed the field API and improved the Entity Query API.
   

   I am not sure what it means to "complete the field API" but it sounds inaccurate by definition :) Maybe just "Improved the field API and entity query API"? (Or make them separate bullet points.)

6. +    * Added configuration schema, dependencies, and validation to maintain
          data-integrity between deployments and updates.
   

   Not added in this patch, but "data-integrity" => "data integrity".

7. +- Made media management (a little) easier:
   

   That looks pretty odd. Why not just "Improved media management"?

8. +    * Made it possible to use drag-and-drop for instant uploads, when using file
   +      fields. Even multiple files at once.
   

   The last sentence especially (which isn't even a sentence) seems out of place here. Maybe the whole thing could just be "Made it possible to instantly upload files via drag-and-drop"?

9. +      * Added language fallback possibility in interface translation (no UI in
   +        core though to configure it).
   

   I found that sentence confusing. Not sure the best way to reword it, but maybe "Added a language fallback capability to the interface translation API"?

10. +    * Added the notion of comment types (for reviews, greetings, and so on),
    +      which may take different fields on their own.
    

    Something's wrong here... at least replace the last part with "each of which can be configured with a different set of fields", I think.

11. +    * Converted various core listings: /node, several blocks blocks,
    +      /admin/content/node and /admin/people to views.
    

    Something's wrong with that sentence... How about "Converted various core listings to views, including /node, /admin/content/node, /admin/people, and several blocks"?

12. +    * Added ability to place all blocks multiple times.
    

    Should be "Added the ability to place all blocks multiple times on the same page"?

13. +- Introduced an accessible modal API based on improvements made in collaboration
    +  with the jQuery UI team and the Views team.
    

    Views is part of Drupal, so "and the Views team" doesn't make any sense here. Just leave that part off.

14. +- Moved the automated cron execution functionality to its own module, so it can
    +  be turned off on sites that don't need it.
    

    It was always possible to turn off...

    "Moved the automated cron execution functionality to its own module" is enough to say here by itself, I think.

15. +    * Managing fields for each entity type is now a separate (secure)
    +      permission.
    

    "Secure" is really ambiguous here. I would just leave that word out.

16. +    * PDO MySQL limited to executing single statements to limit SQLi vectors.
    

    This should not be here since it wasn't introduced in Drupal 8 (see http://cgit.drupalcode.org/drupal/tree/CHANGELOG.txt?h=7.40#n53). However given #2489672: Limit all DB drivers to executing single statements by checking for delimiter this could instead maybe say something about adding similar protection for non-MySQL drivers?

    Also, "SQLi" => "SQL injection".

17. +    * Twig autoescape to provide output-filtering and prevent XSS vectors.
    

    Let's be careful with this one. We don't autoescape everything, and what we do isn't limited to Twig. I would say something like "Added an autoescape API to prevent cross-site scripting in many of the places where Drupal outputs HTML"...

18. +    * Core JavaScript API Compatible with CSP.
    

    Too much capitalization; not enough words :) How about something like "Made the core JavaScript API compatible with Content Security Policy (CSP)"?

19. +- Security improvements:
    ....
    +    * User content entry and filtering improved, and more tightly integrated
    +      with WYSIWYG editors.
    

    Not sure what this refers to security-wise... probably needs to be more specific if it's going to stay in this section.

20.  Drupal 8.0.x, xxxx-xx-xx (development version)
    ...
    +  months in 8.1, 8.2, etc.
     
     Drupal 7.0, 2011-01-05
    

    Hm, I guess it's time to revive #1762708: Update CHANGELOG.txt to contain up-to-date entries from previous versions of Drupal also.

+++ b/core/CHANGELOG.txt
-- Made media management (a little) easier:
-    * Made it possible to use drag-and-drop for instant uploads, when using file
-      fields. Even multiple files at once.
+    * Made file uploads immediate when selecting files in file fields.

Thanks, this is more accurate. But it's still worth calling out the support for uploading multiple files simultaneously!

I'll review this now. (maybe we can get another intermediate commit)

1. 2. Not sure adding it above 8.0.0 would be useful, it is not really an over-arching improvement, you cannot learn much about Drupal 7 or 6 changes with change notices, they were mostly used for Drupal 8.

   There are some for Drupal 7; however my bigger point is that it applies to future releases also (e.g. 8.0.1 and beyond). There is nothing about change notices that is specific to the 8.0.0 release so it looks pretty out of place to me there.

2. 4. But they don't look bad on other displays :) They look good ALSO on retina displays.

   Honestly I don't think anyone would be confused by that - it's not like we'd want to make them worse elsewhere :) I guess it's OK as is, but I did find the "too" to be confusing.

3. 12. No, its not about the same page. You can place a block to a sidebar on one page or set of pages while the same block may be in the footer on another set of pages page.

   Hm, right. So how about "Added the ability to place the same block in multiple locations" or something like that?

4. +    * Made file uploads immediate when selecting files in file fields.
   

   This isn't as good as the previous one, in my opinion. It is still worth mentioning drag-and-drop even though it's not the only way. How about something like "Made it possible to instantly upload files, including via drag-and-drop"?

5. -- Removed the Statistics module's accesslog functionality and reports from core.
   +- Improved the statistics module:
   +    * Made view counting work with the page cache and reverse proxies.
   +    * Removed the accesslog functionality and reports.
   

   "statistics" => "Statistics", but also... isn't that new (first) bullet point referring to #1209532: Count node views via AJAX in the statistics module which is already in Drupal 7? I think the only difference is that it's on by default in Drupal 8 (but not Drupal 7). Not sure that difference is really worth mentioning.

We're in the final home stretch of preparing 8.0.0, and we won't be committing the majority of "rc target" issues any more, but still leaving the tag on them to triage them for patch-release or minor-release post 8.0.0 release. Meanwhile, switching to "8.0.0 target" for issues we'd still love to get in before 8.0.0.

1. +++ b/core/CHANGELOG.txt
   -- Improved entity system.
   +    * Added support for widgets, formatters and translation to base entity
   
   -- Configuration:
   +    * Made uploading, aligning and captioning of images possible in the editor.
   

   oxford comma here also.

2. +++ b/core/CHANGELOG.txt
   -- Configuration:
   +    * Allowed module authors to provide configuration in a standard file format.
   

   standard file format.

   "standard"

   maybe simple instead or just take out the adjective.

3. +++ b/core/CHANGELOG.txt
   -- Configuration:
   +    * Implemented functionality to get, set, add and remove configuration.
   

   comma after add (before and)

4. +++ b/core/CHANGELOG.txt
   -- Configuration:
   +    * Added Text Editor module to help map other editors to text formats.
   

   adding "the" so: "Added the Text Editor module"

5. +++ b/core/CHANGELOG.txt
   -- Configuration:
   +    * Added ability to configure when unused files get deleted with the option
   +      to keep them. Useful for media libraries.
   

   fix english a bit so is a sentence.

6. +++ b/core/CHANGELOG.txt
   -- Removed the Statistics module's accesslog functionality and reports from core.
   +- Improved the statistics module:
   

   keeping the capital on the module name.

7. +++ b/core/CHANGELOG.txt
   -- When using MySQL, the MyISAM engine is no longer supported.
   +      and instantly, including reverse proxies and CDNs.
   

   including on
   including for
   ?

8. +++ b/core/CHANGELOG.txt
   -- When using MySQL, the MyISAM engine is no longer supported.
   +      also enabled it by default.
   

   I think we can remove also.

I'll make those changes now.

I looked at the whole patch, and the changes mostly look accurate and the wording is good.

someone please check my interdiff.

I dont think it is ok to have a changelog and not have a pointer to where people can actually find all of the changes: the change records.
How are people supposed to discover our change records?

But we can discuss that later, I'm ok with a commit without it.

based on feedback from @dawehner in irc (standard YAML redundant), so taking out the standard and being specific about which standard. :)

-
-The following is a list of the most important changes made to Drupal in 8.0.0.
-For a detailed list of changes with background information, see
-https://www.drupal.org/list-changes/drupal
-

How about instead of that "intro", just add a single bullet point at the bottom?

- Numerous other important changes and additions. See https://www.drupal.org/list-changes/drupal for a detailed list.

The problem is still that that link isn't (and never will be) specific to 8.0.0 but at least that would get it into the list, in a way that's consistent with the "catch-all" bullets points at the bottom of existing CHANGELOG.txt entries.

In fact we could add those catch-all bullet points too (certainly they are true), so maybe:

...
- Numerous other important changes and additions. See https://www.drupal.org/list-changes/drupal for a detailed list.
- Numerous bug fixes.
- Numerous API documentation improvements.
- Additional automated test coverage.

* All entity types, not just nodes, now have support for revisions.

Wishful thinking, sadly. Only applies to content entity types.

I'll make those change now.

(maybe when after some change record improvements we can have a link that applies a filter by version that is useful. right now... it's not so much)

addressed #74 and #75

here is the meta I was thinking of: #2292469: [meta] Improve change records
and this child might be the one that would result in an argument to the url for change records where a version can be given: #2289073: Make it easier to find change records that are relevant for major version upgrades

+++ b/core/CHANGELOG.txt
@@ -52,7 +52,8 @@ Drupal 8.0.x, xxxx-xx-xx (development version)
+    * All content entity types (terms, comments, etc.), not just nodes, have
+      support for revisions.

we could add custom blocks to the list before the etc.

we could add custom blocks to the list before the etc.

yeah cause only nodes and custom blocks are turned on by default

1. +++ b/core/CHANGELOG.txt
   @@ -10,7 +11,7 @@ Drupal 8.0.x, xxxx-xx-xx (development version)
        * Included the HTML5 Shiv library to support HTML5 elements in IE 8 and
   
   @@ -29,41 +31,70 @@ Drupal 8.0.x, xxxx-xx-xx (development version)
        * Removed most support for Internet Explorer 8 and below.
   

   These two look weird in combination.

2. +++ b/core/CHANGELOG.txt
   -- Improved entity system.
   +- Improved the entity system:
   

   I may be biased but shouldn't we mention that the entity schema is now fully managed by the system? ;)

Thanks @larowlan and @plach
I'm going to make a new patch now.

Added the custom blocks.

I checked "Included the HTML5 Shiv library" was an old entry (the line was moved around in this issue in an earlier commit). I think it makes most sense to remove it given we are removing IE 8 support.

got help from @alexpott and @catch for the wording of the entity schema line. thanks!

let's get this a review!

Thanks, this looks ready to go to me, but I have not enough knowledge about all the D8 changes to RTBC it.

You know, we can iterate for ages, let's get the improvements in!

1. +++ b/core/CHANGELOG.txt
   -- Improved entity system.
   +    * Added search to the module listing and made the page easier to read.
   

   I was about to mention that we could add that you can also search on the testing page, but this is not strictly a site administrator experience ;)

2. +++ b/core/CHANGELOG.txt
   -- Reworked menu links, local actions, and local tasks based upon the new routing
   +- Made declarative information (libraries, permissions, routes etc.) use YAML
   +  files for definitions instead of PHP.
   

   Maybe also mention menu links?

testbot just retested all the patches when the change went to rtbc... [edit: those interested might want to see #2598438: Improve logic and/or UI around retesting patches in RTBC issues and patches can be hidden as a workaround]

the fail on #83 can't be failing cause of changes to changelog.
https://www.drupal.org/pift-ci-job/84616
head: https://www.drupal.org/pift-ci-job/84336 was earlier
and there haven't been any commits since then.
so I'm gonna reset this to rtbc.

Thanks @tim.plunkett for hiding the old patches so they are not retested and for removing allll the test fail messages on the old patches that are not relevant :)

This looks great. Thanks for everyone's contribution to this! Ticking everyone's credit box but mine.

I pushed #83 to 8.0.x. But before marking this Fixed, here's a patch to set the exact version and date. Just uploading it as a reminder for @catch to do this prior to tagging.

He'll probably want to look at https://www.drupal.org/node/721106 for that :)

Committed/pushed to 8.0.x, thanks!