Last updated February 20, 2012. Created by tstoeckler on May 10, 2011.
Edited by JohnAlbin, webchick, jhodgdon, salvis. Log in to edit this page.
For Drupal 8 and beyond, we are (hooray!) not creating a page similar to the other pages in this section.
Find out about changes in Drupal Core
If you came here because you want to find out about changes in Drupal Core, visit:
http://drupal.org/list-changes/drupal
- To see changes just for Drupal 8, see http://drupal.org/list-changes/drupal?to_branch=8.x
- To see changes just for Drupal 7, see http://drupal.org/list-changes/drupal?to_branch=7.x
Change updates needed for Coder module, Examples and Documentation
If you came here because you are a maintainer of Coder module, Examples, or Documentation, and want to see which changes need to be reflected in Coder, Examples, or Documentation, visit:
http://drupal.org/list-change-updates/drupal
Create a Change Record
If you came here because you wanted to add to this page, instead create a Change Record node at: http://drupal.org/node/add/changenotice and it will automatically be listed on the pages above.
Comments
Is it just me?
Is it just me?
But I don't find this useful/usable at all. There are no code samples like in the previous 1-page style, and you can't ctrl-f for phrases related to the code you're upgrading. All it lists are dates and titles of the changes, which have very little meaning to me. You have to actually click each title to get enough detail to understand the title, so you have to wade through each page of the index and then open each link up on the page to read it. No more skimming to find relevant information.
This seems more suitable for managing the core project, rather than making it easy for contrib maintainers.
I agree, I loved the master
I agree, I loved the master page we had for Drupal 6 to 7. It made updating the code so much easier, especially since it was all on one page.
-Leighton
------------------------------------------------
Leighton Whiting - http://blog.leightonwhiting.com
WildKatana Design - http://www.wildkatana.com
I loved the master page we
+1
Entering the changes as
Entering the changes as separate records is a big improvement IMO. It wouldn't be too hard for someone to make a View which lists all change record bodies at once.
I'd be glad to create a view
I agree that individual change records makes much more sense, but we desperately need a way to view this. I'd be glad to create such a view but don't have access to do that.
The RSS feed is handy -- it basically creates such a view -- but it is is hard-wired to always show the last XX items, ignoring filters and pager pages. It might be useful to have the rss feed respond to the filters, show the same number of items as the view (it does not now), and use offsets based on the page # of the result. With that you could create a feed of any subset of the changes for your own purposes.
It's not just you, the change
It's not just you, the change appears to be to make it easier for core maintainers at the expense of ease-of-use for the rest of us.
Web Design, GNU/Linux and Drupal.