Last modified: 2014-11-18 18:07:19 UTC
Implement full support for enhanced changes format in client recent changes and watchlist. This requires a bit of refactoring and cleanup of spaghetti code in core, and then simplify / provide a more fine-grained way for extensions to hook into the core code that generates the recent changes lists in the special pages.
*** Bug 45927 has been marked as a duplicate of this bug. ***
Copying my comment from duplicate bug: I see that they've been intentionally hidden in I567a697f, but it's a non-solution and a major issue, especially since we're now trying to make that the default per bug 35785.
I think I was told fixing this bug was only a matter of days? I understand that there are other even higher priorities but High/1.21 should be correct I hope.
Is anything happening about this?
Sorry folks for not replying earlier: It is on our todo list but it does require quite a bit of work so I have to ask you for some more patience unfortunately.
*** Bug 50510 has been marked as a duplicate of this bug. ***
*** Bug 48865 has been marked as a duplicate of this bug. ***
(Up)
Sergey: If you have a specific question or a technical comment to make, please go ahead. Just writing "(Up)" isn't very helpful or clear. :)
Andre, the specific of question is so obvious for me, so i wrote it in short form "up". I believe it's okay to do it _once a year_. In full form it looks like "how is the progress of this item and is there anything we can help with?"
