+1 This would be really helpful
> On 17 Dec 2015, at 21:38, Greg Mann wrote:
>
> reparation for the 0.26.0 release. Since I started contributing
> to the project, my Source of Truth for "how to prepare a given platform to
> compile and run Mesos" has been the Getting Started
+1. (Really exited about this prospect!)
This kind of documentation is not necessarily for “testing” only. How can we
expect certain features to run in production if they don’t pass the unit tests
on a given platform? So I am in favor of the “let’s expand our existing install
instructions”
indeed useful.
2016-01-06 18:16 GMT+08:00 Bernd Mathiske :
> +1. (Really exited about this prospect!)
>
> This kind of documentation is not necessarily for “testing” only. How can
> we expect certain features to run in production if they don’t pass the unit
> tests on a
+1
The current version of get-started.md lacks introduction into . Today I
tried to run a docker container test case
"ROOT_DOCKER_DestroyWhileFetching", but by default it's disabled unless I
use "sudo make check". I'm not aware of that until I dig into the test
environment/filters code.
This
+1 to the general idea of including this information in the documentation.
I'd probably lean towards including this information in the current
"Getting Started" page, but in a separate section ("Running The Test
Suite"?).
Neil
On Thu, Dec 17, 2015 at 12:38 PM, Greg Mann
Hey folks!
Something occurred to me recently which is related to the extensive testing
we did in preparation for the 0.26.0 release. Since I started contributing
to the project, my Source of Truth for "how to prepare a given platform to
compile and run Mesos" has been the Getting Started page of