Thanks Alex!
Also I would like to re-state the importance of everyone subscribing to the
builds@ list and helping triage the build failure emails. In particular, if
you find a ticket, reply with it so that others don't have to look into it.
If there's no ticket, capturing the logs of the bad run
+kapil
Kapil was this missed during the 1.4.0 release? It seems to be in the
release guide:
http://mesos.apache.org/documentation/latest/release-guide/#updating-external-tooling
On Sun, Oct 22, 2017 at 1:38 AM, Erb, Stephan
wrote:
> Hi,
>
> the
Github user andschwa commented on the issue:
https://github.com/apache/mesos/pull/242
I thought I caught all of these... I `grep`ed for them anyway. Hm, thanks
@Tri0L!
---
Github user jpeach commented on the issue:
https://github.com/apache/mesos/pull/242
thanks @Tri0L
---
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/242
---
GitHub user Tri0L opened a pull request:
https://github.com/apache/mesos/pull/242
Link to getting started
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Tri0L/mesos patch-1
Alternatively you can review and apply these changes