Re: Looking for shepherd

[Judith Malnick]

Thanks Ben!

On Mon, Feb 12, 2018 at 2:17 PM, Benjamin Mahler  wrote:

> In case others also look at this thinking this still needs a shepherd, this
> has been committed.
>
> On Mon, Feb 12, 2018 at 6:39 AM, Tomek Janiszewski 
> wrote:
>
> > I need someone to review and merge this change
> > https://reviews.apache.org/r/65569/
> > It should fix ARM tests.
> >
>



-- 
Judith Malnick
Community Manager
310-709-1517

Re: Looking for shepherd

[Benjamin Mahler]

In case others also look at this thinking this still needs a shepherd, this
has been committed.

On Mon, Feb 12, 2018 at 6:39 AM, Tomek Janiszewski 
wrote:

> I need someone to review and merge this change
> https://reviews.apache.org/r/65569/
> It should fix ARM tests.
>

Looking for shepherd

[Tomek Janiszewski]

I need someone to review and merge this change
https://reviews.apache.org/r/65569/
It should fix ARM tests.

Re: MESOS-7233: Looking for shepherd

[Tomek Janiszewski]

OK, I discovered it myself, this test uses absolute paths.

@Benjamin You were right it's not backward compatible. I'll work on this.

mesos 1.3.0 framework failed with mesos 1.3.48291 master and mesos 1.3.0
agent




pt., 17 mar 2017 o 13:44 użytkownik Tomek Janiszewski <jani...@gmail.com>
napisał:

@Benjamin thanks for taking a look at this. I tried to run
mesos/test-upgrade.py but it failed on starting the framework? Below are
the logs? What am I doing wrong?

./support/test-upgrade.py --prev build --next build-varint
Running upgrade test from mesos 1.3.0 to mesos 1.3.0
+--+++---+
| Test case|   Framework| Master | Agent |
+--+++---+
|#1|  mesos 1.3.0 | mesos 1.3.0 | mesos 1.3.0 |
|#2|  mesos 1.3.0 | mesos 1.3.0 | mesos 1.3.0 |
|#3|  mesos 1.3.0 | mesos 1.3.0 | mesos 1.3.0 |
|#4|  mesos 1.3.0 | mesos 1.3.0 | mesos 1.3.0 |
+--+++---+

NOTE: live denotes that master process keeps running from previous case.


Test case 1 (Run of previous setup)
# Starting mesos 1.3.0 master #
Run ['build/bin/mesos-master.sh', '--ip=127.0.0.1',
'--work_dir=/tmp/tmpGs3TLW', '--authenticate',
'--credentials=/tmp/tmpQUicSA', '--roles=test'], output: /tmp/tmpSVfW1x
# Starting mesos 1.3.0 agent #
Run ['build/bin/mesos-slave.sh', '--master=127.0.0.1:5050',
'--credential=/tmp/tmpQUicSA', '--work_dir=/tmp/tmpCgaNrV',
'--resources=disk:2048;mem:2048;cpus:2'], output: /tmp/tmpgil1QV
# Starting mesos 1.3.0 framework #
Waiting for mesos 1.3.0 framework to complete (10 sec max)...
Run ['build/src/test-framework', '--master=127.0.0.1:5050'], output:
/tmp/tmp_sTAa1
mesos 1.3.0 framework failed


pt., 17 mar 2017 o 00:44 użytkownik Benjamin Mahler <bmah...@apache.org>
napisał:

Thanks Tomek, I'm not very familiar with the code but I dug in and couldn't
figure out how this is a backwards compatible change to make. Left a
comment on the review.

On Sat, Mar 11, 2017 at 2:24 AM, Tomek Janiszewski <jani...@gmail.com>
wrote:

> Hi
>
> I'm looking for shepherd for MESOS-7233 — Use varint comparator in replica
> log.
>
> JIRA: https://issues.apache.org/jira/browse/MESOS-7233
> Review: https://reviews.apache.org/r/48291/
>
> Thanks
> Tomek
>

Re: MESOS-7233: Looking for shepherd

[Benjamin Mahler]

Thanks Tomek, I'm not very familiar with the code but I dug in and couldn't
figure out how this is a backwards compatible change to make. Left a
comment on the review.

On Sat, Mar 11, 2017 at 2:24 AM, Tomek Janiszewski <jani...@gmail.com>
wrote:

> Hi
>
> I'm looking for shepherd for MESOS-7233 — Use varint comparator in replica
> log.
>
> JIRA: https://issues.apache.org/jira/browse/MESOS-7233
> Review: https://reviews.apache.org/r/48291/
>
> Thanks
> Tomek
>

MESOS-7233: Looking for shepherd

[Tomek Janiszewski]

Hi

I'm looking for shepherd for MESOS-7233 — Use varint comparator in replica
log.

JIRA: https://issues.apache.org/jira/browse/MESOS-7233
Review: https://reviews.apache.org/r/48291/

Thanks
Tomek

Re: Looking for shepherd for MESOS-4638

[Benjamin Mahler]

For posterity, and for those keeping track of shepherd requests, Yan
shepherded. Thanks Yan!

On Thursday, August 11, 2016, Zhitao Li  wrote:

> Our modules requires conditional compile because we need to make sure we
> can cross version boundary during upgrade cycles, so I'm interested in
> getting this fixed.
>
> Can some committer help to shepherd?
>
> (Joris, from git blame it seems you added these macros :)
>
> Thanks.
>
> --
> Cheers,
>
> Zhitao Li
>

Looking for shepherd for MESOS-4638

[Zhitao Li]

Our modules requires conditional compile because we need to make sure we
can cross version boundary during upgrade cycles, so I'm interested in
getting this fixed.

Can some committer help to shepherd?

(Joris, from git blame it seems you added these macros :)

Thanks.

-- 
Cheers,

Zhitao Li

Re: Looking for Shepherd for MESOS-2201

[Benjamin Mahler]

+alexr

It would be helpful if the shepherd replies to the list when they get
involved. Hard to tell from the mailing list that this was picked up.

On Tue, May 10, 2016 at 12:46 AM, Tomek Janiszewski 
wrote:

> Hi
>
> Can anyone help shepherd MESOS-2201 – Fixed replica log restore tests.
> This issue is first step to upgrade leveldb.
>
> https://issues.apache.org/jira/browse/MESOS-2201
> https://reviews.apache.org/r/47161/
>
> Thanks
> Tomek
>

Re: Looking for shepherd HealthCheck flaky test cases

[Benjamin Mahler]

Thanks for looking into these, I gave reviews on:
https://reviews.apache.org/r/47089/
https://reviews.apache.org/r/46307/

I couldn't tell why this change was being made, can you describe why in the
review description?
https://reviews.apache.org/r/47088/

Just as an aside, the health check test code is in need of readability
improvements IMHO.

On Sat, May 7, 2016 at 2:37 AM, haosdent  wrote:

> Hi, All. We have two Health Check flaky test cases for a long time.
>
> [HealthCheckTest.HealthStatusChange is flaky on jenkins.](
> https://issues.apache.org/jira/browse/MESOS-1653)
> [HealthCheckTest.GracePeriod is flaky.](
> https://issues.apache.org/jira/browse/MESOS-1802)
>
> I’m writing to inquire if anyone could review and shepherd the patches of
> them. Any review and comments on patches would be highly appreciated. Thank
> you in advance.
>
> --
> Best Regards,
> Haosdent Huang
>

Looking for Shepherd for MESOS-2201

[Tomek Janiszewski]

Hi

Can anyone help shepherd MESOS-2201 – Fixed replica log restore tests.
This issue is first step to upgrade leveldb.

https://issues.apache.org/jira/browse/MESOS-2201
https://reviews.apache.org/r/47161/

Thanks
Tomek

Looking for shepherd HealthCheck flaky test cases

[haosdent]

Hi, All. We have two Health Check flaky test cases for a long time.

[HealthCheckTest.HealthStatusChange is flaky on jenkins.](
https://issues.apache.org/jira/browse/MESOS-1653)
[HealthCheckTest.GracePeriod is flaky.](
https://issues.apache.org/jira/browse/MESOS-1802)

I’m writing to inquire if anyone could review and shepherd the patches of
them. Any review and comments on patches would be highly appreciated. Thank
you in advance.

-- 
Best Regards,
Haosdent Huang

Re: Looking for Shepherd for MESOS-5263

[haosdent]

ping @ben and @vinodkone, would you like to review this patch again?

On Wed, Apr 27, 2016 at 7:22 PM, haosdent  wrote:

> Already left my comments on it, thank you for your patch!
>
> On Wed, Apr 27, 2016 at 5:52 PM, Tomek Janiszewski 
> wrote:
>
>> Hi
>>
>> I prepared cleanup https://reviews.apache.org/r/46730/
>> @Haosdent can you check it?
>>
>> Best
>> Tomek
>>
>> śr., 27.04.2016 o 04:03 użytkownik haosdent  napisał:
>>
>> > Hi, @bmahler, thank you so much for review it! As the email I sent
>> > to @idownes and @chenzhiwei, we could drop that safely by adding
>> >
>> > ```
>> > #include 
>> > ```
>> >
>> > from @RobinDong's patch.
>> >
>> > Because this header file comes from kernel headers and it include
>> machine
>> > specific syscall numbers no matter which CPU architecture used.
>> >
>> > On the other hand, we can not use
>> >
>> > ```
>> > #include 
>> > #include 
>> > ```
>> >
>> > as the source of the syscall numbers because these header files come
>> from
>> > glibc.
>> >
>> > ```
>> > $ rpm -qf /usr/include/sys/syscall.h
>> > glibc-headers-2.12-1.149.el6_6.5.x86_64
>> > $ rpm -qf /usr/include/unistd.h
>> > glibc-headers-2.12-1.149.el6_6.5.x86_64
>> > ```
>> >
>> > If use them, would fall into the problem @idownes mentioned in
>> > `linux/ns.hpp` (Old glibc library and new kernel)
>> >
>> > ```
>> > #ifdef SYS_setns
>> >   int ret = ::syscall(SYS_setns, fd.get(), nstype.get());
>> > #elif __x86_64__
>> >   // A workaround for those hosts that have an old glibc (older than
>> >   // 2.14) but have a new kernel. The magic number '308' here is the
>> >   // syscall number for 'setns' on x86_64 architecture.
>> >   int ret = ::syscall(308, fd.get(), nstype.get());
>> > #else
>> > #error "setns is not available"
>> > #endif
>> > ```
>> >
>> > I verify `#include ` works on CentOS 6.5, CentOS 7.2
>> Ubuntu
>> > 14.04 with X86 and Debian jessie with ARM. In code level, I verify it
>> works
>> > on all architectures I know [
>> > http://lxr.free-electrons.com/ident?v=3.8;i=__NR_pivot_root] .
>> >
>> > @BingLi would like to port Mesos works on System Z, and he blocked by
>> > `__NR_pivot_root ` (https://issues.apache.org/jira/browse/MESOS-5242)
>> as
>> > well. As he commented in ticket, `#include ` could solve
>> > the problem as well.
>> >
>> >
>> > Appendix[The verify program]:
>> >
>> > ```
>> > #include 
>> > #include 
>> >
>> > int main(int argc, char const *argv[])
>> > {
>> >   std::cout << __NR_pivot_root << std::endl;
>> >   return 0;
>> > }
>> > ```
>> >
>> >
>> > On Wed, Apr 27, 2016 at 3:24 AM, Benjamin Mahler 
>> > wrote:
>> >
>> > > Looks like Vinod shipped MESOS-5121. I just shipped MESOS-5263
>> following
>> > > the same approach.
>> > >
>> > > Haosdent mentioned some cleanups are possible here so please keep us
>> > > posted if the cleanups are available!
>> > >
>> > > On Sun, Apr 24, 2016 at 1:34 PM, Tomek Janiszewski > >
>> > > wrote:
>> > >
>> > >> Hi,
>> > >>
>> > >> Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263
>> ?
>> > >> It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and
>> > >> could
>> > >> be resolved in the same manner or it could be done in a way that'll
>> > >> support
>> > >> other platforms as well.
>> > >>
>> > >> Thanks
>> > >> Tomek
>> > >>
>> > >
>> > >
>> >
>> >
>> > --
>> > Best Regards,
>> > Haosdent Huang
>> >
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>



-- 
Best Regards,
Haosdent Huang

Re: Looking for Shepherd for MESOS-5263

[haosdent]

Already left my comments on it, thank you for your patch!

On Wed, Apr 27, 2016 at 5:52 PM, Tomek Janiszewski 
wrote:

> Hi
>
> I prepared cleanup https://reviews.apache.org/r/46730/
> @Haosdent can you check it?
>
> Best
> Tomek
>
> śr., 27.04.2016 o 04:03 użytkownik haosdent  napisał:
>
> > Hi, @bmahler, thank you so much for review it! As the email I sent
> > to @idownes and @chenzhiwei, we could drop that safely by adding
> >
> > ```
> > #include 
> > ```
> >
> > from @RobinDong's patch.
> >
> > Because this header file comes from kernel headers and it include machine
> > specific syscall numbers no matter which CPU architecture used.
> >
> > On the other hand, we can not use
> >
> > ```
> > #include 
> > #include 
> > ```
> >
> > as the source of the syscall numbers because these header files come from
> > glibc.
> >
> > ```
> > $ rpm -qf /usr/include/sys/syscall.h
> > glibc-headers-2.12-1.149.el6_6.5.x86_64
> > $ rpm -qf /usr/include/unistd.h
> > glibc-headers-2.12-1.149.el6_6.5.x86_64
> > ```
> >
> > If use them, would fall into the problem @idownes mentioned in
> > `linux/ns.hpp` (Old glibc library and new kernel)
> >
> > ```
> > #ifdef SYS_setns
> >   int ret = ::syscall(SYS_setns, fd.get(), nstype.get());
> > #elif __x86_64__
> >   // A workaround for those hosts that have an old glibc (older than
> >   // 2.14) but have a new kernel. The magic number '308' here is the
> >   // syscall number for 'setns' on x86_64 architecture.
> >   int ret = ::syscall(308, fd.get(), nstype.get());
> > #else
> > #error "setns is not available"
> > #endif
> > ```
> >
> > I verify `#include ` works on CentOS 6.5, CentOS 7.2
> Ubuntu
> > 14.04 with X86 and Debian jessie with ARM. In code level, I verify it
> works
> > on all architectures I know [
> > http://lxr.free-electrons.com/ident?v=3.8;i=__NR_pivot_root] .
> >
> > @BingLi would like to port Mesos works on System Z, and he blocked by
> > `__NR_pivot_root ` (https://issues.apache.org/jira/browse/MESOS-5242) as
> > well. As he commented in ticket, `#include ` could solve
> > the problem as well.
> >
> >
> > Appendix[The verify program]:
> >
> > ```
> > #include 
> > #include 
> >
> > int main(int argc, char const *argv[])
> > {
> >   std::cout << __NR_pivot_root << std::endl;
> >   return 0;
> > }
> > ```
> >
> >
> > On Wed, Apr 27, 2016 at 3:24 AM, Benjamin Mahler 
> > wrote:
> >
> > > Looks like Vinod shipped MESOS-5121. I just shipped MESOS-5263
> following
> > > the same approach.
> > >
> > > Haosdent mentioned some cleanups are possible here so please keep us
> > > posted if the cleanups are available!
> > >
> > > On Sun, Apr 24, 2016 at 1:34 PM, Tomek Janiszewski 
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263?
> > >> It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and
> > >> could
> > >> be resolved in the same manner or it could be done in a way that'll
> > >> support
> > >> other platforms as well.
> > >>
> > >> Thanks
> > >> Tomek
> > >>
> > >
> > >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
> >
>



-- 
Best Regards,
Haosdent Huang

Re: Looking for Shepherd for MESOS-5263

[Tomek Janiszewski]

Hi

I prepared cleanup https://reviews.apache.org/r/46730/
@Haosdent can you check it?

Best
Tomek

śr., 27.04.2016 o 04:03 użytkownik haosdent  napisał:

> Hi, @bmahler, thank you so much for review it! As the email I sent
> to @idownes and @chenzhiwei, we could drop that safely by adding
>
> ```
> #include 
> ```
>
> from @RobinDong's patch.
>
> Because this header file comes from kernel headers and it include machine
> specific syscall numbers no matter which CPU architecture used.
>
> On the other hand, we can not use
>
> ```
> #include 
> #include 
> ```
>
> as the source of the syscall numbers because these header files come from
> glibc.
>
> ```
> $ rpm -qf /usr/include/sys/syscall.h
> glibc-headers-2.12-1.149.el6_6.5.x86_64
> $ rpm -qf /usr/include/unistd.h
> glibc-headers-2.12-1.149.el6_6.5.x86_64
> ```
>
> If use them, would fall into the problem @idownes mentioned in
> `linux/ns.hpp` (Old glibc library and new kernel)
>
> ```
> #ifdef SYS_setns
>   int ret = ::syscall(SYS_setns, fd.get(), nstype.get());
> #elif __x86_64__
>   // A workaround for those hosts that have an old glibc (older than
>   // 2.14) but have a new kernel. The magic number '308' here is the
>   // syscall number for 'setns' on x86_64 architecture.
>   int ret = ::syscall(308, fd.get(), nstype.get());
> #else
> #error "setns is not available"
> #endif
> ```
>
> I verify `#include ` works on CentOS 6.5, CentOS 7.2 Ubuntu
> 14.04 with X86 and Debian jessie with ARM. In code level, I verify it works
> on all architectures I know [
> http://lxr.free-electrons.com/ident?v=3.8;i=__NR_pivot_root] .
>
> @BingLi would like to port Mesos works on System Z, and he blocked by
> `__NR_pivot_root ` (https://issues.apache.org/jira/browse/MESOS-5242) as
> well. As he commented in ticket, `#include ` could solve
> the problem as well.
>
>
> Appendix[The verify program]:
>
> ```
> #include 
> #include 
>
> int main(int argc, char const *argv[])
> {
>   std::cout << __NR_pivot_root << std::endl;
>   return 0;
> }
> ```
>
>
> On Wed, Apr 27, 2016 at 3:24 AM, Benjamin Mahler 
> wrote:
>
> > Looks like Vinod shipped MESOS-5121. I just shipped MESOS-5263 following
> > the same approach.
> >
> > Haosdent mentioned some cleanups are possible here so please keep us
> > posted if the cleanups are available!
> >
> > On Sun, Apr 24, 2016 at 1:34 PM, Tomek Janiszewski 
> > wrote:
> >
> >> Hi,
> >>
> >> Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263?
> >> It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and
> >> could
> >> be resolved in the same manner or it could be done in a way that'll
> >> support
> >> other platforms as well.
> >>
> >> Thanks
> >> Tomek
> >>
> >
> >
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Looking for Shepherd for MESOS-5263

[haosdent]

Hi, @bmahler, thank you so much for review it! As the email I sent
to @idownes and @chenzhiwei, we could drop that safely by adding

```
#include 
```

from @RobinDong's patch.

Because this header file comes from kernel headers and it include machine
specific syscall numbers no matter which CPU architecture used.

On the other hand, we can not use

```
#include 
#include 
```

as the source of the syscall numbers because these header files come from
glibc.

```
$ rpm -qf /usr/include/sys/syscall.h
glibc-headers-2.12-1.149.el6_6.5.x86_64
$ rpm -qf /usr/include/unistd.h
glibc-headers-2.12-1.149.el6_6.5.x86_64
```

If use them, would fall into the problem @idownes mentioned in
`linux/ns.hpp` (Old glibc library and new kernel)

```
#ifdef SYS_setns
  int ret = ::syscall(SYS_setns, fd.get(), nstype.get());
#elif __x86_64__
  // A workaround for those hosts that have an old glibc (older than
  // 2.14) but have a new kernel. The magic number '308' here is the
  // syscall number for 'setns' on x86_64 architecture.
  int ret = ::syscall(308, fd.get(), nstype.get());
#else
#error "setns is not available"
#endif
```

I verify `#include ` works on CentOS 6.5, CentOS 7.2 Ubuntu
14.04 with X86 and Debian jessie with ARM. In code level, I verify it works
on all architectures I know [
http://lxr.free-electrons.com/ident?v=3.8;i=__NR_pivot_root] .

@BingLi would like to port Mesos works on System Z, and he blocked by
`__NR_pivot_root ` (https://issues.apache.org/jira/browse/MESOS-5242) as
well. As he commented in ticket, `#include ` could solve
the problem as well.


Appendix[The verify program]:

```
#include 
#include 

int main(int argc, char const *argv[])
{
  std::cout << __NR_pivot_root << std::endl;
  return 0;
}
```


On Wed, Apr 27, 2016 at 3:24 AM, Benjamin Mahler  wrote:

> Looks like Vinod shipped MESOS-5121. I just shipped MESOS-5263 following
> the same approach.
>
> Haosdent mentioned some cleanups are possible here so please keep us
> posted if the cleanups are available!
>
> On Sun, Apr 24, 2016 at 1:34 PM, Tomek Janiszewski 
> wrote:
>
>> Hi,
>>
>> Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263?
>> It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and
>> could
>> be resolved in the same manner or it could be done in a way that'll
>> support
>> other platforms as well.
>>
>> Thanks
>> Tomek
>>
>
>


-- 
Best Regards,
Haosdent Huang

Re: Looking for Shepherd for MESOS-5263

[Benjamin Mahler]

Looks like Vinod shipped MESOS-5121. I just shipped MESOS-5263 following
the same approach.

Haosdent mentioned some cleanups are possible here so please keep us posted
if the cleanups are available!

On Sun, Apr 24, 2016 at 1:34 PM, Tomek Janiszewski 
wrote:

> Hi,
>
> Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263?
> It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and could
> be resolved in the same manner or it could be done in a way that'll support
> other platforms as well.
>
> Thanks
> Tomek
>

Looking for Shepherd for MESOS-5263

[Tomek Janiszewski]

Hi,

Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263?
It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and could
be resolved in the same manner or it could be done in a way that'll support
other platforms as well.

Thanks
Tomek

Looking for Shepherd for Mesos-3402

[Timothy Anderegg]

Hi folks -

https://issues.apache.org/jira/browse/MESOS-3402

This change adds support for framework authentication to the mesos-execute
command line utility, to make it easier to conduct integration testing.
It's a fairly small change code-wise, please let me know if you could help
review/shepherd, thanks!

Tim

Re: Looking for Shepherd for MESOS-1104

[tommy xiao]

Hi team,

Need a committer to give a Shepherd for MESOS-1104,  anyone can help review
it( https://reviews.apache.org/r/45500/). the patch is updated as  "ship
it" status.

2016-04-01 13:49 GMT+08:00 tommy xiao :

> the patch is here: https://reviews.apache.org/r/45500/
>
> 2016-04-01 13:25 GMT+08:00 tommy xiao :
>
>> Hi team,
>>
>> https://issues.apache.org/jira/browse/MESOS-1104
>>
>> i have follow haosdent's suggest, remove mesos::internal:: should be
>> enough. need a shepherd to let thing done. thanks
>>
>>
>>
>> --
>> Deshi Xiao
>> Twitter: xds2000
>> E-mail: xiaods(AT)gmail.com
>>
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[Kevin Klues]

@Alexr: That makes sense. I think we should enforce the check for
unicode in the docs though. Ascii in the code, unicode in the docs. I
can review the python.

On Sun, Apr 3, 2016 at 2:42 AM, Alex Rukletsov <a...@mesosphere.com> wrote:
> @Vinod: I can take it, but would like someone, more experienced in python
> than myself, to review it.
>
> @Kevin: I think we should not apply the same rules for code and docs. Since
> docs are meant for people, I believe special characters, umlauts, symbols
> make them easier to read and digest. I'd suggest pushing UTF-8 for docs,
> it's 21st century! Alternatively, we can use numeric character references,
> if folks think unicode in docs is a bad idea.
>
> On Sat, Apr 2, 2016 at 8:48 PM, Kevin Klues <klue...@gmail.com> wrote:
>
>> @vinod, @alexr.  Neil and I had also suggested not excluding the doc
>> directories (which Yong's current patch still does).  What are your
>> thoughts on this?
>>
>> On Fri, Apr 1, 2016 at 6:47 PM, Yong Tang <yong.tang.git...@outlook.com>
>> wrote:
>> > Hi Vinod,
>> >
>> > Thanks for the help. I updated the mesos-style.py and added the
>> non-ascii check there.
>> >
>> > Please let me know if there is anything else that needs to do to move
>> forward this issue.
>> >
>> >
>> > Thanks
>> > Yong
>> >
>> >> From: vinodk...@apache.org
>> >> Date: Fri, 1 Apr 2016 15:47:29 -0700
>> >> Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for
>> non-ascii characters)
>> >> To: dev@mesos.apache.org
>> >>
>> >> @AleR do you want to be a shepherd for this, since you originally filed
>> >> this ticket?
>> >>
>> >> @Yong: Just took a quick look at the review. It's unfortunate that we
>> need
>> >> a whole new script for checking non-ascii characters. Can we update
>> >> mesos-style.py to catch this?
>> >>
>> >> On Fri, Apr 1, 2016 at 7:36 AM, Yong Tang <yong.tang.git...@outlook.com
>> >
>> >> wrote:
>> >>
>> >> > Ping again to find a shepherd for MESOS-4033. A review request has
>> been
>> >> > created with good discussions from many reviewers:
>> >> >
>> >> > https://reviews.apache.org/r/45033/
>> >> >
>> >> > It would be really good if a shepherd could provide some guidance so
>> that
>> >> > this ticket could move forward.
>> >> >
>> >> > Thanks
>> >> > Yong
>> >> >
>> >> > > Date: Sat, 26 Mar 2016 08:13:28 +0800
>> >> > > Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for
>> >> > non-ascii characters)
>> >> > > From: xia...@gmail.com
>> >> > > To: dev@mesos.apache.org
>> >> > >
>> >> > > +1
>> >> > >
>> >> > > 2016-03-25 23:26 GMT+08:00 Yong Tang <yong.tang.git...@outlook.com
>> >:
>> >> > >
>> >> > > > Hi
>> >> > > >
>> >> > > > Just bump the email to look for shepherd for MESOS-4033.
>> >> > > >
>> >> > > > This issue (commit hook for non ascii characters) has already been
>> >> > fairly
>> >> > > > discussed on the review board. Thanks Deshi, Neil, and haosdent
>> for the
>> >> > > > great inputs.
>> >> > > >
>> >> > > > It really would be nice if there is anyone that could shepherd so
>> that
>> >> > the
>> >> > > > issue could move forward.
>> >> > > >
>> >> > > > Thanks
>> >> > > > Yong
>> >> > > >
>> >> > > >
>> >> > > > > From: yong.tang.git...@outlook.com
>> >> > > > > To: dev@mesos.apache.org
>> >> > > > > Subject: Looking for Shepherd for MESOS-4033 (commit hook for
>> >> > non-ascii
>> >> > > > characters)
>> >> > > > > Date: Tue, 22 Mar 2016 08:31:40 -0700
>> >> > > > >
>> >> > > > > Hi All
>> >> > > > >
>> >> > > > > Can anyone help shepherd MESOS-4033 - Add a commit hook for
>> non-ascii
>> >> > > > characters?
>> >> > > > >
>> >> > > > > https://issues.apache.org/jira/browse/MESOS-4033
>> >> > > > >
>> >> > > > > This issue is about adding a commit hook to check for non-ascii
>> >> > > > characters. The issue has been accepted sometime ago.
>> >> > > > >
>> >> > > > > Thanks a lot for the help
>> >> > > > > Yong
>> >> > > > >
>> >> > > >
>> >> > > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Deshi Xiao
>> >> > > Twitter: xds2000
>> >> > > E-mail: xiaods(AT)gmail.com
>> >> >
>> >> >
>> >
>>
>>
>>
>> --
>> ~Kevin
>>



-- 
~Kevin

Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[Alex Rukletsov]

@Vinod: I can take it, but would like someone, more experienced in python
than myself, to review it.

@Kevin: I think we should not apply the same rules for code and docs. Since
docs are meant for people, I believe special characters, umlauts, symbols
make them easier to read and digest. I'd suggest pushing UTF-8 for docs,
it's 21st century! Alternatively, we can use numeric character references,
if folks think unicode in docs is a bad idea.

On Sat, Apr 2, 2016 at 8:48 PM, Kevin Klues <klue...@gmail.com> wrote:

> @vinod, @alexr.  Neil and I had also suggested not excluding the doc
> directories (which Yong's current patch still does).  What are your
> thoughts on this?
>
> On Fri, Apr 1, 2016 at 6:47 PM, Yong Tang <yong.tang.git...@outlook.com>
> wrote:
> > Hi Vinod,
> >
> > Thanks for the help. I updated the mesos-style.py and added the
> non-ascii check there.
> >
> > Please let me know if there is anything else that needs to do to move
> forward this issue.
> >
> >
> > Thanks
> > Yong
> >
> >> From: vinodk...@apache.org
> >> Date: Fri, 1 Apr 2016 15:47:29 -0700
> >> Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for
> non-ascii characters)
> >> To: dev@mesos.apache.org
> >>
> >> @AleR do you want to be a shepherd for this, since you originally filed
> >> this ticket?
> >>
> >> @Yong: Just took a quick look at the review. It's unfortunate that we
> need
> >> a whole new script for checking non-ascii characters. Can we update
> >> mesos-style.py to catch this?
> >>
> >> On Fri, Apr 1, 2016 at 7:36 AM, Yong Tang <yong.tang.git...@outlook.com
> >
> >> wrote:
> >>
> >> > Ping again to find a shepherd for MESOS-4033. A review request has
> been
> >> > created with good discussions from many reviewers:
> >> >
> >> > https://reviews.apache.org/r/45033/
> >> >
> >> > It would be really good if a shepherd could provide some guidance so
> that
> >> > this ticket could move forward.
> >> >
> >> > Thanks
> >> > Yong
> >> >
> >> > > Date: Sat, 26 Mar 2016 08:13:28 +0800
> >> > > Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for
> >> > non-ascii characters)
> >> > > From: xia...@gmail.com
> >> > > To: dev@mesos.apache.org
> >> > >
> >> > > +1
> >> > >
> >> > > 2016-03-25 23:26 GMT+08:00 Yong Tang <yong.tang.git...@outlook.com
> >:
> >> > >
> >> > > > Hi
> >> > > >
> >> > > > Just bump the email to look for shepherd for MESOS-4033.
> >> > > >
> >> > > > This issue (commit hook for non ascii characters) has already been
> >> > fairly
> >> > > > discussed on the review board. Thanks Deshi, Neil, and haosdent
> for the
> >> > > > great inputs.
> >> > > >
> >> > > > It really would be nice if there is anyone that could shepherd so
> that
> >> > the
> >> > > > issue could move forward.
> >> > > >
> >> > > > Thanks
> >> > > > Yong
> >> > > >
> >> > > >
> >> > > > > From: yong.tang.git...@outlook.com
> >> > > > > To: dev@mesos.apache.org
> >> > > > > Subject: Looking for Shepherd for MESOS-4033 (commit hook for
> >> > non-ascii
> >> > > > characters)
> >> > > > > Date: Tue, 22 Mar 2016 08:31:40 -0700
> >> > > > >
> >> > > > > Hi All
> >> > > > >
> >> > > > > Can anyone help shepherd MESOS-4033 - Add a commit hook for
> non-ascii
> >> > > > characters?
> >> > > > >
> >> > > > > https://issues.apache.org/jira/browse/MESOS-4033
> >> > > > >
> >> > > > > This issue is about adding a commit hook to check for non-ascii
> >> > > > characters. The issue has been accepted sometime ago.
> >> > > > >
> >> > > > > Thanks a lot for the help
> >> > > > > Yong
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Deshi Xiao
> >> > > Twitter: xds2000
> >> > > E-mail: xiaods(AT)gmail.com
> >> >
> >> >
> >
>
>
>
> --
> ~Kevin
>

Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[Kevin Klues]

@vinod, @alexr.  Neil and I had also suggested not excluding the doc
directories (which Yong's current patch still does).  What are your
thoughts on this?

On Fri, Apr 1, 2016 at 6:47 PM, Yong Tang <yong.tang.git...@outlook.com> wrote:
> Hi Vinod,
>
> Thanks for the help. I updated the mesos-style.py and added the non-ascii 
> check there.
>
> Please let me know if there is anything else that needs to do to move forward 
> this issue.
>
>
> Thanks
> Yong
>
>> From: vinodk...@apache.org
>> Date: Fri, 1 Apr 2016 15:47:29 -0700
>> Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii 
>> characters)
>> To: dev@mesos.apache.org
>>
>> @AleR do you want to be a shepherd for this, since you originally filed
>> this ticket?
>>
>> @Yong: Just took a quick look at the review. It's unfortunate that we need
>> a whole new script for checking non-ascii characters. Can we update
>> mesos-style.py to catch this?
>>
>> On Fri, Apr 1, 2016 at 7:36 AM, Yong Tang <yong.tang.git...@outlook.com>
>> wrote:
>>
>> > Ping again to find a shepherd for MESOS-4033. A review request has been
>> > created with good discussions from many reviewers:
>> >
>> > https://reviews.apache.org/r/45033/
>> >
>> > It would be really good if a shepherd could provide some guidance so that
>> > this ticket could move forward.
>> >
>> > Thanks
>> > Yong
>> >
>> > > Date: Sat, 26 Mar 2016 08:13:28 +0800
>> > > Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for
>> > non-ascii characters)
>> > > From: xia...@gmail.com
>> > > To: dev@mesos.apache.org
>> > >
>> > > +1
>> > >
>> > > 2016-03-25 23:26 GMT+08:00 Yong Tang <yong.tang.git...@outlook.com>:
>> > >
>> > > > Hi
>> > > >
>> > > > Just bump the email to look for shepherd for MESOS-4033.
>> > > >
>> > > > This issue (commit hook for non ascii characters) has already been
>> > fairly
>> > > > discussed on the review board. Thanks Deshi, Neil, and haosdent for the
>> > > > great inputs.
>> > > >
>> > > > It really would be nice if there is anyone that could shepherd so that
>> > the
>> > > > issue could move forward.
>> > > >
>> > > > Thanks
>> > > > Yong
>> > > >
>> > > >
>> > > > > From: yong.tang.git...@outlook.com
>> > > > > To: dev@mesos.apache.org
>> > > > > Subject: Looking for Shepherd for MESOS-4033 (commit hook for
>> > non-ascii
>> > > > characters)
>> > > > > Date: Tue, 22 Mar 2016 08:31:40 -0700
>> > > > >
>> > > > > Hi All
>> > > > >
>> > > > > Can anyone help shepherd MESOS-4033 - Add a commit hook for non-ascii
>> > > > characters?
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/MESOS-4033
>> > > > >
>> > > > > This issue is about adding a commit hook to check for non-ascii
>> > > > characters. The issue has been accepted sometime ago.
>> > > > >
>> > > > > Thanks a lot for the help
>> > > > > Yong
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Deshi Xiao
>> > > Twitter: xds2000
>> > > E-mail: xiaods(AT)gmail.com
>> >
>> >
>



-- 
~Kevin

RE: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[Yong Tang]

Hi Vinod,

Thanks for the help. I updated the mesos-style.py and added the non-ascii check 
there.

Please let me know if there is anything else that needs to do to move forward 
this issue.


Thanks
Yong

> From: vinodk...@apache.org
> Date: Fri, 1 Apr 2016 15:47:29 -0700
> Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii 
> characters)
> To: dev@mesos.apache.org
> 
> @AleR do you want to be a shepherd for this, since you originally filed
> this ticket?
> 
> @Yong: Just took a quick look at the review. It's unfortunate that we need
> a whole new script for checking non-ascii characters. Can we update
> mesos-style.py to catch this?
> 
> On Fri, Apr 1, 2016 at 7:36 AM, Yong Tang <yong.tang.git...@outlook.com>
> wrote:
> 
> > Ping again to find a shepherd for MESOS-4033. A review request has been
> > created with good discussions from many reviewers:
> >
> > https://reviews.apache.org/r/45033/
> >
> > It would be really good if a shepherd could provide some guidance so that
> > this ticket could move forward.
> >
> > Thanks
> > Yong
> >
> > > Date: Sat, 26 Mar 2016 08:13:28 +0800
> > > Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for
> > non-ascii characters)
> > > From: xia...@gmail.com
> > > To: dev@mesos.apache.org
> > >
> > > +1
> > >
> > > 2016-03-25 23:26 GMT+08:00 Yong Tang <yong.tang.git...@outlook.com>:
> > >
> > > > Hi
> > > >
> > > > Just bump the email to look for shepherd for MESOS-4033.
> > > >
> > > > This issue (commit hook for non ascii characters) has already been
> > fairly
> > > > discussed on the review board. Thanks Deshi, Neil, and haosdent for the
> > > > great inputs.
> > > >
> > > > It really would be nice if there is anyone that could shepherd so that
> > the
> > > > issue could move forward.
> > > >
> > > > Thanks
> > > > Yong
> > > >
> > > >
> > > > > From: yong.tang.git...@outlook.com
> > > > > To: dev@mesos.apache.org
> > > > > Subject: Looking for Shepherd for MESOS-4033 (commit hook for
> > non-ascii
> > > > characters)
> > > > > Date: Tue, 22 Mar 2016 08:31:40 -0700
> > > > >
> > > > > Hi All
> > > > >
> > > > > Can anyone help shepherd MESOS-4033 - Add a commit hook for non-ascii
> > > > characters?
> > > > >
> > > > > https://issues.apache.org/jira/browse/MESOS-4033
> > > > >
> > > > > This issue is about adding a commit hook to check for non-ascii
> > > > characters. The issue has been accepted sometime ago.
> > > > >
> > > > > Thanks a lot for the help
> > > > > Yong
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Deshi Xiao
> > > Twitter: xds2000
> > > E-mail: xiaods(AT)gmail.com
> >
> >
  

RE: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[Yong Tang]

Ping again to find a shepherd for MESOS-4033. A review request has been created 
with good discussions from many reviewers:

https://reviews.apache.org/r/45033/

It would be really good if a shepherd could provide some guidance so that this 
ticket could move forward.

Thanks
Yong

> Date: Sat, 26 Mar 2016 08:13:28 +0800
> Subject: Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii 
> characters)
> From: xia...@gmail.com
> To: dev@mesos.apache.org
> 
> +1
> 
> 2016-03-25 23:26 GMT+08:00 Yong Tang <yong.tang.git...@outlook.com>:
> 
> > Hi
> >
> > Just bump the email to look for shepherd for MESOS-4033.
> >
> > This issue (commit hook for non ascii characters) has already been fairly
> > discussed on the review board. Thanks Deshi, Neil, and haosdent for the
> > great inputs.
> >
> > It really would be nice if there is anyone that could shepherd so that the
> > issue could move forward.
> >
> > Thanks
> > Yong
> >
> >
> > > From: yong.tang.git...@outlook.com
> > > To: dev@mesos.apache.org
> > > Subject: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii
> > characters)
> > > Date: Tue, 22 Mar 2016 08:31:40 -0700
> > >
> > > Hi All
> > >
> > > Can anyone help shepherd MESOS-4033 - Add a commit hook for non-ascii
> > characters?
> > >
> > > https://issues.apache.org/jira/browse/MESOS-4033
> > >
> > > This issue is about adding a commit hook to check for non-ascii
> > characters. The issue has been accepted sometime ago.
> > >
> > > Thanks a lot for the help
> > > Yong
> > >
> >
> >
> 
> 
> 
> -- 
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
  

Re: Looking for Shepherd for MESOS-1104

[tommy xiao]

the patch is here: https://reviews.apache.org/r/45500/

2016-04-01 13:25 GMT+08:00 tommy xiao :

> Hi team,
>
> https://issues.apache.org/jira/browse/MESOS-1104
>
> i have follow haosdent's suggest, remove mesos::internal:: should be
> enough. need a shepherd to let thing done. thanks
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Looking for Shepherd for MESOS-1104

[tommy xiao]

Hi team,

https://issues.apache.org/jira/browse/MESOS-1104

i have follow haosdent's suggest, remove mesos::internal:: should be
enough. need a shepherd to let thing done. thanks



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Looking for Shepherd for MESOS-3059

[tommy xiao]

Continue update the status from i review:

i review the Design Docs on MESOS-1739, i found the resources is not easily
to reconfiguration without kill task. so i suggest the slave config update
only focus on attributes.

2016-03-25 17:28 GMT+08:00 tommy xiao :

>
> Hello,
>
> Can anyone please shepherd the following JIRA:
>
> https://issues.apache.org/jira/browse/MESOS-3059
>
> This issue add http endpoint to dynamically change the slave attributes.
> we want to push the design docs and patches so on.
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[tommy xiao]

+1

2016-03-25 23:26 GMT+08:00 Yong Tang <yong.tang.git...@outlook.com>:

> Hi
>
> Just bump the email to look for shepherd for MESOS-4033.
>
> This issue (commit hook for non ascii characters) has already been fairly
> discussed on the review board. Thanks Deshi, Neil, and haosdent for the
> great inputs.
>
> It really would be nice if there is anyone that could shepherd so that the
> issue could move forward.
>
> Thanks
> Yong
>
>
> > From: yong.tang.git...@outlook.com
> > To: dev@mesos.apache.org
> > Subject: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii
> characters)
> > Date: Tue, 22 Mar 2016 08:31:40 -0700
> >
> > Hi All
> >
> > Can anyone help shepherd MESOS-4033 - Add a commit hook for non-ascii
> characters?
> >
> > https://issues.apache.org/jira/browse/MESOS-4033
> >
> > This issue is about adding a commit hook to check for non-ascii
> characters. The issue has been accepted sometime ago.
> >
> > Thanks a lot for the help
> > Yong
> >
>
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

RE: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

[Yong Tang]

Hi

Just bump the email to look for shepherd for MESOS-4033. 

This issue (commit hook for non ascii characters) has already been fairly 
discussed on the review board. Thanks Deshi, Neil, and haosdent for the great 
inputs.

It really would be nice if there is anyone that could shepherd so that the 
issue could move forward.

Thanks
Yong


> From: yong.tang.git...@outlook.com
> To: dev@mesos.apache.org
> Subject: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii 
> characters)
> Date: Tue, 22 Mar 2016 08:31:40 -0700
> 
> Hi All
> 
> Can anyone help shepherd MESOS-4033 - Add a commit hook for non-ascii 
> characters?
> 
> https://issues.apache.org/jira/browse/MESOS-4033
> 
> This issue is about adding a commit hook to check for non-ascii characters. 
> The issue has been accepted sometime ago.
> 
> Thanks a lot for the help
> Yong
> 
  

Looking for Shepherd for MESOS-3059

[tommy xiao]

Hello,

Can anyone please shepherd the following JIRA:

https://issues.apache.org/jira/browse/MESOS-3059

This issue add http endpoint to dynamically change the slave attributes. we
want to push the design docs and patches so on.


-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Looking for shepherd for MESOS-4760

[tommy xiao]

+1

2016-03-24 8:32 GMT+08:00 Zhitao Li :

> We are interested in seriously using fetcher for more use cases, but would
> hate to fly completely blind.
>
> Looking for someone to shepherd for MESOS-4760: Expose metrics and gauges
> for fetcher cache usage and hit rate.
>
> Thanks!
>
> --
> Cheers,
>
> Zhitao Li
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Looking for shepherd for MESOS-4760

[Zhitao Li]

We are interested in seriously using fetcher for more use cases, but would
hate to fly completely blind.

Looking for someone to shepherd for MESOS-4760: Expose metrics and gauges
for fetcher cache usage and hit rate.

Thanks!

-- 
Cheers,

Zhitao Li

Re: Looking for Shepherd for MESOS-5002

[Jiří Šimša]

Thanks Neil. I added you to the Review request.

Best,

--
Jiří Šimša

On Tue, Mar 22, 2016 at 9:30 AM, Neil Conway  wrote:

> Sure, I'd be happy to review the change.
>
> Neil
>
>
> On Tue, Mar 22, 2016 at 9:01 AM, Jie Yu  wrote:
> > + Neil
> >
> > Neil is driving the documentation improvement in Mesos. Neil, do you have
> > time for that? I can help commit the patch if you give a shipit.
> >
> > - Jie
> >
> > On Tue, Mar 22, 2016 at 8:45 AM, Jiří Šimša 
> wrote:
> >
> >> Hello,
> >>
> >> Can anyone please shepherd the following JIRA:
> >>
> >> https://issues.apache.org/jira/browse/MESOS-5002
> >>
> >> This issue reflects the recent renaming of Tachyon to Alluxio in Mesos'
> >> documentation. Thanks.
> >>
> >> Best,
> >>
> >> --
> >> Jiří Šimša
> >>
>

Re: Looking for Shepherd for MESOS-5002

[Neil Conway]

Sure, I'd be happy to review the change.

Neil


On Tue, Mar 22, 2016 at 9:01 AM, Jie Yu  wrote:
> + Neil
>
> Neil is driving the documentation improvement in Mesos. Neil, do you have
> time for that? I can help commit the patch if you give a shipit.
>
> - Jie
>
> On Tue, Mar 22, 2016 at 8:45 AM, Jiří Šimša  wrote:
>
>> Hello,
>>
>> Can anyone please shepherd the following JIRA:
>>
>> https://issues.apache.org/jira/browse/MESOS-5002
>>
>> This issue reflects the recent renaming of Tachyon to Alluxio in Mesos'
>> documentation. Thanks.
>>
>> Best,
>>
>> --
>> Jiří Šimša
>>

Re: Looking for shepherd (MESOS-4355 - Docker Volume Isolator)

[Jie Yu]

Guangya, I'd be happy to shepherd this work if no other committers
volunteer for this work.

- Jie

On Thu, Mar 17, 2016 at 6:05 AM, Guangya Liu  wrote:

> Hi,
>
> I was now working on the FS for MESOS-4355 with some EMC guys, can anyone
> help shepherd for this? There are some issues need to discuss with the
> shepherd.
>
> Thanks,
>
> Guangya
>

Looking for shepherd (MESOS-4355 - Docker Volume Isolator)

[Guangya Liu]

Hi,

I was now working on the FS for MESOS-4355 with some EMC guys, can anyone
help shepherd for this? There are some issues need to discuss with the
shepherd.

Thanks,

Guangya

RE: Looking for shepherd (MESOS-4807)

[Yong Tang]

Thanks Benjamin and Joris for the help!

Thanks
Yong

> Subject: Re: Looking for shepherd (MESOS-4807)
> From: benjamin.bann...@mesosphere.io
> Date: Tue, 15 Mar 2016 21:29:17 +0100
> To: dev@mesos.apache.org
> 
> Hi Yong,
> 
> > I am looking for shepherd to help me on MESOS-4807. 
> > 
> > https://issues.apache.org/jira/browse/MESOS-4807
> > 
> > This issue is similar to MESOS-4806 as both of them tries to fixes issues 
> > that could parallelize the tests in mesos. Would appreciate if anyone could 
> > shepherd to help me on this issue (MESOS-4807).
> 
> Thanks for taking on fixing this issue. Joris stepped up to shepherd your 
> patch, and it looks like he already committed it.
> 
> 
> Cheers,
> 
> Benjamin
  

Re: Looking for shepherd (MESOS-4807)

[Benjamin Bannier]

Hi Yong,

> I am looking for shepherd to help me on MESOS-4807. 
> 
> https://issues.apache.org/jira/browse/MESOS-4807
> 
> This issue is similar to MESOS-4806 as both of them tries to fixes issues 
> that could parallelize the tests in mesos. Would appreciate if anyone could 
> shepherd to help me on this issue (MESOS-4807).

Thanks for taking on fixing this issue. Joris stepped up to shepherd your 
patch, and it looks like he already committed it.


Cheers,

Benjamin

Looking for shepherd (MESOS-4807)

[Yong Tang]

Hi All

I am looking for shepherd to help me on MESOS-4807. 

https://issues.apache.org/jira/browse/MESOS-4807

This issue is similar to MESOS-4806 as both of them tries to fixes issues that 
could parallelize the tests in mesos. Would appreciate if anyone could shepherd 
to help me on this issue (MESOS-4807).
Thanks a lotYong  

Looking for shepherd of MESOS-4807

[Yong Tang]

Hi All,Can anyone shepherd 
MESOS-4807?https://issues.apache.org/jira/browse/MESOS-4807This is a minor 
issue though the fix of this issue will allow mesos tests to be executed in 
parallel in the future.Thanks a lot for the help!Yong   

Re: Looking for shepherd for MESOS-4705

[Benjamin Mahler]

Thanks for looking into this bug, I left some comments.

On Sun, Mar 6, 2016 at 11:28 PM, Du, Fan  wrote:

> Hi
>
> Could I have a shepherd for MESOS-4705<
> https://issues.apache.org/jira/browse/MESOS-4705> ?
> A trivial bug fix with RR https://reviews.apache.org/r/44379/
>
> Thanks a lot.
>
>
>

Looking for shepherd for MESOS-4705

[Du, Fan]

Hi

Could I have a shepherd for 
MESOS-4705 ?
A trivial bug fix with RR https://reviews.apache.org/r/44379/

Thanks a lot.

Re: Looking for shepherd of three trivial tickets

[Shuai Lin]

Hi Alex, Could you please shepherd these tickets? Thanks!

On Mon, Feb 29, 2016 at 10:17 AM, Shuai Lin  wrote:

> Hi,
>
> Can anyone shepherd these trivial tickets? All of them are about speeding
> up tests by advancing the clock.
>
> https://issues.apache.org/jira/browse/MESOS-3775 (RR
> https://reviews.apache.org/r/43329/)
> https://issues.apache.org/jira/browse/MESOS-4160 (RR
> https://reviews.apache.org/r/43524/)
> https://issues.apache.org/jira/browse/MESOS-4175 (RR
> https://reviews.apache.org/r/43321/)
>
> Regards,
> Shuai
>
>

Looking for shepherd of three trivial tickets

[Shuai Lin]

Hi,

Can anyone shepherd these trivial tickets? All of them are about speeding
up tests by advancing the clock.

https://issues.apache.org/jira/browse/MESOS-3775 (RR
https://reviews.apache.org/r/43329/)
https://issues.apache.org/jira/browse/MESOS-4160 (RR
https://reviews.apache.org/r/43524/)
https://issues.apache.org/jira/browse/MESOS-4175 (RR
https://reviews.apache.org/r/43321/)

Regards,
Shuai

Looking for shepherd to solve MESOS-4135

[Srinivas R Brahmaroutu]

I am learning Mesos and looking to contribute. I thought this would be a
good bug to work on.
https://issues.apache.org/jira/browse/MESOS-4135