CHANGES.txt has been neglected for 1.8
|Reported by:||brettp||Owned by:|
Thoughts on how to go about updating this file? It could end up being a huge task. I'm thinking the following will help to keep it concise and useful:
- Only flyby info on the large changes ("New menu system" vs "added ElggMenuItem, ElggMenuBuilder, elgg_view_menu(), ...")
- Mention deprecated functions only (instead of deprecated and new functions)
- Don't try to address deprecated views.
- Abstract out as many changes as possible with generic messages (Multiple bugfixes to Blog plugin). This might be annoying to end users interested in those bugs, though.