🤖 Update from upstream repository mesosphere/mesos-dns

.gitignore

@@ -4,3 +4,4 @@ mesos-dns
 *.gz
 VERSION
 cov.json
+*.swp

CHANGELOG

@@ -1,3 +1,19 @@
+2016-09-14: v0.6.0
+  Added some benchmarks for RecordGenerator.insertRR
+  Make minor fixes to enumeration API, where it would return null, as
+    as opposed to an empty list
+  Add the AXFR (record listing) HTTP API endpoint
+  Make HTTP listener address configurable
+  General improvements to the HTTP client
+    -Pool HTTP connections, preventing connection leakage
+    -Set the User Agent
+  Switch the project to Go Vendor as opposed to Godeps
+  Add HTTPS Client support to Mesos-DNS (for state.json)
+  Add Mesos authentication support
+  Fix tasks from more than 63 dashes and a non - character from
+    crashing Mesos-DNS
+  Don't treat truncated records as an error.
+
 2016-03-04: v0.5.2
   Add EnforceRFC952 to sample config
   Improve performance of record generation

CONTRIBUTING.md

@@ -1,5 +1,7 @@
 # Contributing
+
 ## Issues
+
 When filing an issue, make sure to answer these five questions:
 
 1. What version of the project are you using?
@@ -9,14 +11,17 @@ When filing an issue, make sure to answer these five questions:
 5. What did you see instead?
 
 ## Code
+
 ### Proposals
+
 Non trivial changes should be first discussed with the project maintainers by
 opening a Github issue with the "Proposal: " title prefix, clearly explaining
 rationale, context and implementation ideas.
 
 This separate step is encouraged but not required.
 
 ### Implementation
+
 Work should happen in an open pull request having a WIP prefix in its
 title which gives visibility to the development process and provides
 continuous integration feedback.
@@ -28,6 +33,7 @@ bring your contribution to the attention of project maintainers who will review
 your PR in a timely manner.
 
 Before review, keep in mind that:
+
 - Git commit messages should conform to [community standards](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 - Git commits should represent meaningful milestones or units of work.
 - Changed or added code must be well tested. Different kinds of code
@@ -36,4 +42,4 @@ Before review, keep in mind that:
 - Changes to vendored files must be grouped into a single commit.
 
 Once comments and revisions on the implementation wind down, the reviewers will
-add the LGTM label which marks the PR as merge-able.
+add the LGTM label which marks the PR as mergeable.