On Fri, Jun 8, 2012 at 7:36 AM, Petr Bena <benap...@gmail.com> wrote: > I don't think that Risker is wrong, it is true, that ipv6 was enabled > on production almost with no warning and since it wasn't available on > any test site before, neither on wmflabs it was almost impossible for > developers to fix all issues in tools related to this. For example one > of tools that broke was huggle, people are complaining now at us > (huggle devs) that it doesn't work, and my reply is: We knew that, we > know that, but no one gave us a chance to prepare. I have no working > ipv6 wiki I could test it on, neither there is any on wmflabs. So when > it was enabled on production we couldn't be prepared for this. Huggle > is not the only tool which broke, there are many others and devs never > had a chance to adapt to ipv6 without any test wiki to try it on. >
Not true--I tested (and fixed) several IPv6 bugs years ago. Labs may not have been setup for IPv6, but as long as your operating system supports IPv6 there's no reason you can't test it locally. Without getting too far OT, I'd like to mention that labs does not have feature parity with the production sites (yet). This is the way it's been for years, and until we get more things available to labs, we should test our code the way we've always done it--locally. I don't think it's reasonable to hold up projects *just because* they haven't been through labs yet. -Chad _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
