On Fri, Apr 3, 2015 at 3:47 PM, Niklas Nielsen nik...@mesosphere.io wrote:
Based on input from Vinod and Adam; I will reduce the scope on the point
release to focus on MESOS-1795 and MESOS-2583.
Can I help test these in any way?
--
/adam
On Mon, Nov 9, 2015 at 4:29 AM, Bernd Mathiske wrote:
> +1 on converting lots of TODOs into JIRAs with links to them in the TODOs.
>
Totally agree with pulling TODOs out to something more visible / trackable
/ scheduleable.
> Questions with opinions:
> - Do we need to
This is great! I am not one of the devs, but the more transparency and ease
of use there is in our tools, the easier it is to focus on the actual work,
and not the process. I really like Martin Fowler's quote from
http://martinfowler.com/articles/newMethodology.html:
"Agile methods are
Great!
On Fri, Nov 6, 2015 at 9:00 AM, tommy xiao wrote:
> +1
>
> 2015-11-06 17:59 GMT+08:00 Guangya Liu :
>
> > Just FYI, the OpenStack Kolla Team [1] is forming a small team trying to
> > investigate if Mesos could be used as an orchestration engine in
Not sure, but could this turn into a newb doc or something pointing to
references on internet for dev env setup and such?
On Thu, Dec 3, 2015 at 1:43 PM, Alex Rukletsov wrote:
> Hi Abhishek and welcome to the community!
>
> There are a lot of options to set up Mesos
On Tue, Nov 24, 2015 at 3:15 PM, Marco Massenzio <ma...@mesosphere.io>
wrote:
> On Tue, Nov 24, 2015 at 10:45 AM, Adam Avilla <a...@avil.la> wrote:
>
> > Is there any way to support HUP reloading of config with this design
> > paradigm?
>
>
> Can you please
> > > > > >
> > > > > > $ source config.sh
> > > > > > $ ./bin/mesos-master.sh
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Nov 23, 2015 at 10:19 AM, Jo
+1 I think it would be helpful.
This may be orthogonal / feature creep, but would it be possible to have
the config file be able to be safely reloaded with a HUP or appropriate
signal?
On Mon, Nov 23, 2015 at 5:32 AM, Guangya Liu wrote:
> +1000, introducing a new