https://bugzilla.wikimedia.org/show_bug.cgi?id=33287
--- Comment #8 from Chad H. <innocentkil...@gmail.com> 2012-04-16 14:52:00 UTC --- (In reply to comment #6) > git has the ability to fill in keywords when checking out files. Have a look > at > "Keyword Expansion" on http://progit.org/book/ch7-2.html . Just because the functionality exists doesn't mean we should use it. There's lots of bad ideas out there ;-) (In reply to comment #7) > Solutions that require local configuration changes will not work as nobody > will > use them. This. (In reply to comment #5) > (In reply to comment #2) > > It would be nice to have some kind of versioning on our public API so people > > can detect incompatibilities when they exist. > > Although the previous svn:keywords did not provide that information, that was > just a simple "last rev modified" number. Right now this bug is just to remove > them. We could open a feature enhancement ticket for that other, although I > personally never found that needed and release notes seem to be more useful > for > breaking changes. If we create an API module to programmatically be able to > export the version of an Api module, the it could be useful to an Api client > to > see if it considers itself compatible, that'd be a nice feature. I'm in favor of simple integer increments. When a module changes in an incompatible way, bump v1 -> v2 (which doesn't happen *often*). But you're right, let's spin that off to another bug and just remove the existing keywords while we bikeshed over that. -- 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 Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
