I agree with kalid's sentiments here. I think updating the changelog for stable should be a manual process, but the change log for trunk could easily be an automated process before we push out the release.
- Isolate checkins to /trunk
- Generate change log from svn commits
Having to update the changelog for all commits is going to be prone to errors.
@Guerric
Great work. I've used it in the developer site for the first time today and it's really a huge improvement!
Obviously not for this release, but might dekiscript syntax highlighting be implemented at some point?rberinger contributed syntax definition files for Crimson Editor: http://developer.mindtouch.com/DekiScript/Tutorials/DekiScript_Syntax_Highlighting
Also, some sort of autosave would be a real bonus - I currently use a text editor with autosave, and copy / paste to CKEditor periodically when coding / doing anything taking more than 2 minutes, but users can't be told to do that in my experience!
@Guerric - Take in mind the Active Directory Groups, I mean if you add a user to a group ( on AD not Mindtouch Interface) if you don't log out / log in you wan't get this user / group from AD information. The same if you delete / disable a User on the Active Directory ( a employer fired up ), this user will enter on Mindtouch forever :(
Guerric - for your advanced search function (http://wiki.developer.mindtouch.com/index.php?title=MindTouch_Deki/Extensions/Advanced_Search&highlight=advanced+search) - I would really likely to be able to use it while getting the results in the standard deki format, but I see you have said this is only for "advanced users" I tried to just a) copy the on a new wiki page, and then b) update the advanced page as you indicated. However, I get an error on the wiki page where I want the results to appear and gather the code you have provided is only half complete...any chance we could have this in baby language?
If you look on that page, you'll notice that the entire extension source code is listed under the "Source Code" heading. Simply take the entire contents of the "results" function and paste it into the wiki page in SOURCE mode.
Guerric - thanks so much for answering. I tried what you said, but when I paste the whole code in "Source" mode, nothing happens when I get out of source mode (nothing on screen) and then when I return to Source mode, what I pasted is gone. I realise this is basic stuff, but it would help me so much to get this up and running.
Concerning your resolution of bug #8572, can you provide an exemple of the correct way to use this feature? I created a new class that inherit from beechbetaTemplate but where do I set the $wgBeechTemplate variable?