https://bugzilla.wikimedia.org/show_bug.cgi?id=30955
--- Comment #14 from Olivier Finlay Beaton <[email protected]> 2011-09-18 05:18:09 UTC --- 23:45 < bawolff> I was thinking another approach to that version bug, would be for ExtensionDistributor to annotate extensions downloaded from it with revision number some way (like via a hidden file) that MW could read and understand This is really interesting. A hidden file with revision information sounds great. Knowing if it was 'trunk' or what 'branch' would be great too. This way we don't need to rely on extension authors to add an auto-gen var to one of their files, since we can add the hidden file automatically to any extension branch before we check it out and have it auto-populate. Something like Special:Update can then read out the info, and use API calls to determine if the extensions need updating. When we move to GIT we simply change from revisions to hashes and use the API to know if my hash is older than the one MW has. This also alleviates the need for extension authors to update their versions and de-values the version numbers quiete a lot. As an admin and extension author I still like versions, but this would go a long way to making them seem 'old-school'. (what version of chrome do I have? I don't really care). -- 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
