You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by Steve Loughran <st...@hortonworks.com> on 2014/05/20 14:22:11 UTC

JIRA talking to slider dev

Everyone should have noticed now that JIRA is sending issue creation events
to the list.

it is of mixed benefit for all that this happened just before I copied over
a pool of pre-apache internal JIRAs.

Now they're out, volunteers welcome. I'm going to start the new sprint
today, so drag into the "slider-may-2" sprint what you want to work on for
the next fortnight, keep out stuff you wont


https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=41&view=planning

FWIW I'm going to do three main things


   1. registry -provider publishing with tests
   2. start to push upstream YARN enhancements
   3. all of next week in berlin, half of this week writing a twill app and
   slides: https://issues.apache.org/jira/browse/SLIDER-28 . I'll send the
   slides out for review soon. These aren't slider specific -about YARN dev in
   general. TL;DR: have someone else write the AM and stay at the Knuth layer,
   not the Lamport layer

in the background, more of the ASF migration homework

-steve

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: JIRA talking to slider dev

Posted by Billie Rinaldi <bi...@gmail.com>.
On Tue, May 20, 2014 at 5:22 AM, Steve Loughran <st...@hortonworks.com>wrote:

> Everyone should have noticed now that JIRA is sending issue creation events
> to the list.
>

Sumit accomplished this by sending an email to "dev-allow-subscribe-jira=
apache.org@slider.incubator.apache.org".  Presumably Steve and Jon also
have moderation abilities, just no one is seeing moderation emails for the
dev list because it's set to automatically reject everything from
non-subscribers.  When we want to subscribe other services so that we can
see notifications from them (such as jenkins), they can be subscribed to
the dev-allow list as above.  (For new moderators: an -allow list contains
emails that can send to a mailing list, but do not receive mail from the
list.)


>
> it is of mixed benefit for all that this happened just before I copied over
> a pool of pre-apache internal JIRAs.
>
> Now they're out, volunteers welcome. I'm going to start the new sprint
> today, so drag into the "slider-may-2" sprint what you want to work on for
> the next fortnight, keep out stuff you wont
>
>
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=41&view=planning
>
> FWIW I'm going to do three main things
>
>
>    1. registry -provider publishing with tests
>    2. start to push upstream YARN enhancements
>    3. all of next week in berlin, half of this week writing a twill app and
>    slides: https://issues.apache.org/jira/browse/SLIDER-28 . I'll send the
>    slides out for review soon. These aren't slider specific -about YARN
> dev in
>    general. TL;DR: have someone else write the AM and stay at the Knuth
> layer,
>    not the Lamport layer
>
> in the background, more of the ASF migration homework
>
> -steve
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>