We have moved to Github. Please open tickets there.

#3668 closed Defect (fixed)

CHANGES.txt has been neglected for 1.8

Reported by: brettp Owned by:
Priority: low Milestone: Elgg 1.8.0
Component: Core Version: 1.8 Beta
Severity: trivial Keywords:
Cc: brett@… Difficulty: moderate

Description

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.

Change History (2)

comment:1 Changed 21 months ago by brettp

It will be an eagle's eye view of the changes.

comment:2 Changed 21 months ago by brettp

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.