As discussed during the API working group, we would like to ensure that
upcoming API changes are surfaced more broadly than just in Review Board.
The hope is that if we surface them on the dev@ list, it will raise
awareness and give a chance for more folks to give feedback on things like
naming,
Github user chhsia0 closed the pull request at:
https://github.com/apache/mesos/pull/272
---
GitHub user chhsia0 opened a pull request:
https://github.com/apache/mesos/pull/272
Added Chun-Hung Hsiao to the list of committers.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chhsia0/mesos committer
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/271
---
Github user sbz commented on the issue:
https://github.com/apache/mesos/pull/271
@carlonelong No, we are a Software company using [Apache
Mesos](/apache/mesos) and [Singularity](/HubSpot/Singularity) in production.
Checkout our website!
---
Github user carlonelong commented on the issue:
https://github.com/apache/mesos/pull/271
Are you the Nitro making snowboards?
---
GitHub user sbz opened a pull request:
https://github.com/apache/mesos/pull/271
Add Nitro into powered-by-mesos.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Nitro/mesos sbrabez/update-adopters
Alternatively you can review
