https://bugzilla.wikimedia.org/show_bug.cgi?id=30955
--- Comment #13 from Olivier Finlay Beaton <[email protected]> 2011-09-18 04:00:37 UTC --- Hi Daniel, none of that is new I'm sure to people in the community. But it really bares repeating. In terms of control panel we are making slow progress with: http://www.mediawiki.org/wiki/Extension:Maintenance http://www.mediawiki.org/wiki/Extension:Admin_Links http://www.mediawiki.org/wiki/Configure and the missing part of course is Special:Version. All of these leave a lot to be desired, and while some may disagree, I believe wordpress is the right direction. We don't need to core-ify any of these until they are mature however and it's a clear win all around. I'm glad you brought this up Daniel, because I have an extension sitting here in my editor called 'ExtensionUpdate'. If I had commit rights it would be checked in right now, although it's not ready for testing yet (give me a few more days). I fully plan to tackle the problem of trying to provide a 'there is a new version of this extension out'. Eventually it will tackle 'let me download that' to 'let me unpack and install that'. Maybe even oneday it will do so for the core. But before I can start checking if there is a new version, I need version numbers to be more prominent. Hence my request here. If oneday an extension core'ified and becomes the new Special:Version page great. We don't need to revolutionize it right now, people can make extensions and fight it out. But the default core needs to encourage people to put in version number as much as possible, and making it more prominent in Special:Version is a minimal change that I believe would go a long way (why is that box empty, ack!). A loner extension won't get that kind of push. Like I mentioned, putting the revision automatically on checkout into a 'revision' field in $wgExtensionCredits would also be great, and publishing it on the extension pages. But like others have mentioned this won't for git, so to be safe should we really rely on a comit revision system? Maybe just stick with version numbers for now and authors can decide when it warrants to be pushed out to everyone. You can bet that new API calls is next on my list, but at least with version numbers we make administrator's lives easier everywhere, they can do the comparison by hand for now. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
