Re: Apache Infra tickets for MXNet
LGTM One suggestion - add a section how to handle security or other sensitive and time critical issues. I assume that an email should be sent to PPMC to private list to raise such issue and PPMC will take appropriate action. Steffen On Sat, Dec 1, 2018 at 1:40 PM Marco de Abreu wrote: > - Resending since I sent it to the wrong list - > > Thank you Steffen and Michael! > > I have created a new page at > > https://cwiki.apache.org/confluence/display/MXNET/Contacting+Apache+Infrastructure > . > I'd appreciate a review. > > Best regards, > Marco > > On Sat, Dec 1, 2018 at 8:54 PM Michael Wall wrote: > > > LGTM, thanks again for taking care of this for the project > > > > Mike > > > > On Sat, Dec 1, 2018 at 1:10 PM Marco de Abreu < > > marco.g.ab...@googlemail.com> wrote: > > > >> Thank you Steffen and Michael! > >> > >> I have created a new page at > >> > https://cwiki.apache.org/confluence/display/MXNET/Contacting+Apache+Infrastructure > . > >> I'd appreciate a review. > >> > >> Best regards, > >> Marco > >> > >> On Sat, Dec 1, 2018 at 4:23 PM Michael Wall wrote: > >> > >>> Thanks for working through that with infra Marco. I think the process > >>> you outlined is good and being able to submit tickets without mentor > >>> approval is good for the project. > >>> > >>> Whoever puts the process on the wiki please reply with a link. > >>> > >>> Mike > >>> > >>> On Thu, Nov 29, 2018 at 11:45 PM Steffen Rochel < > steffenroc...@gmail.com> > >>> wrote: > >>> > Thanks Marco. Cwiki seems a good place to document the policy. > Steffen > > On Thu, Nov 29, 2018 at 8:06 PM Marco de Abreu > wrote: > > > Hello everyone, > > > > I have just had a nice conversation with Greg Stein, VP of Apache > Infra, > > about the topic of creating tickets against Apache Infra. > > > > In the past, we had the restriction that only IPMC members (speak, > mentors) > > were allowed to file tickets against Apache Infra. This was due past > issues > > where tickets have been created without previous discussions on dev@ > and > > from people who were not PPMC members, thus creating too much churn. > > > > During the last year, the MXNet community has shown that we are able > to > > adhere to the Apache ways. Thus the restrictions are being lifted > and > the > > following policy get set in place: > > > > - Only PPMC members are allowed to create tickets (if you can see > > priv...@mxnet.apache.org, you're good to go) > > - Committers are not allowed to create tickets (if you have write > access to > > GitHub but can't see priv...@mxnet.apache.org, you're not a PPMC > member > > but > > a committer) > > - Contributors are not allowed to create tickets (if you're neither > a > PPMC > > member, nor a committer, then you're a contributor) > > - There always has to be a dev@ thread before a ticket can be > created. > > That > > thread has to be linked in that said ticket. > > - Always search for a solution yourself (self-service) before > engaging with > > Apache Infra. > > > > I'm not sure about a good place to document these guidelines. If > somebody > > has a good idea where we should write them down, please feel free to > drop > > me a link and I'll paste them in there. > > > > Thanks everybody for the great collaboration around Apache Infra > tickets! > > This was a prime example of a community working together. > > > > Best regards, > > Marco > > > > >>> >
Re: Apache Infra tickets for MXNet
- Resending since I sent it to the wrong list - Thank you Steffen and Michael! I have created a new page at https://cwiki.apache.org/confluence/display/MXNET/Contacting+Apache+Infrastructure. I'd appreciate a review. Best regards, Marco On Sat, Dec 1, 2018 at 8:54 PM Michael Wall wrote: > LGTM, thanks again for taking care of this for the project > > Mike > > On Sat, Dec 1, 2018 at 1:10 PM Marco de Abreu < > marco.g.ab...@googlemail.com> wrote: > >> Thank you Steffen and Michael! >> >> I have created a new page at >> https://cwiki.apache.org/confluence/display/MXNET/Contacting+Apache+Infrastructure. >> I'd appreciate a review. >> >> Best regards, >> Marco >> >> On Sat, Dec 1, 2018 at 4:23 PM Michael Wall wrote: >> >>> Thanks for working through that with infra Marco. I think the process >>> you outlined is good and being able to submit tickets without mentor >>> approval is good for the project. >>> >>> Whoever puts the process on the wiki please reply with a link. >>> >>> Mike >>> >>> On Thu, Nov 29, 2018 at 11:45 PM Steffen Rochel >>> wrote: >>> Thanks Marco. Cwiki seems a good place to document the policy. Steffen On Thu, Nov 29, 2018 at 8:06 PM Marco de Abreu wrote: > Hello everyone, > > I have just had a nice conversation with Greg Stein, VP of Apache Infra, > about the topic of creating tickets against Apache Infra. > > In the past, we had the restriction that only IPMC members (speak, mentors) > were allowed to file tickets against Apache Infra. This was due past issues > where tickets have been created without previous discussions on dev@ and > from people who were not PPMC members, thus creating too much churn. > > During the last year, the MXNet community has shown that we are able to > adhere to the Apache ways. Thus the restrictions are being lifted and the > following policy get set in place: > > - Only PPMC members are allowed to create tickets (if you can see > priv...@mxnet.apache.org, you're good to go) > - Committers are not allowed to create tickets (if you have write access to > GitHub but can't see priv...@mxnet.apache.org, you're not a PPMC member > but > a committer) > - Contributors are not allowed to create tickets (if you're neither a PPMC > member, nor a committer, then you're a contributor) > - There always has to be a dev@ thread before a ticket can be created. > That > thread has to be linked in that said ticket. > - Always search for a solution yourself (self-service) before engaging with > Apache Infra. > > I'm not sure about a good place to document these guidelines. If somebody > has a good idea where we should write them down, please feel free to drop > me a link and I'll paste them in there. > > Thanks everybody for the great collaboration around Apache Infra tickets! > This was a prime example of a community working together. > > Best regards, > Marco > >>>
Re: CI impaired
Hello everyone, the move has just been completed and the old big pipeline as well as the according job have been disabled. From now on, you will see the details status messages below your PRs. Some people wanted to make modifications to the Jenkinsfiles recently. In that case, your PR will show a merge conflict. The new Jenkinsfiles are available at [1]. Yesterday, I have indexed all PRs with our CI system to make sure that each one gets properly validated and our merge processes don't get impaired. Everything looks good so far, but due to the flakyness of our tests, it's quite unlikely that every single tests has passed. If your particular PR shows a failure for a certain test, please follow the same procedure as usual and retrigger it by pushing another commit. From now on, you can also trigger partial runs of the CI. For this, just hit up a committer and they will be happy to trigger that specific job on your behalf. If somebody in the community is interested, we would also be happy to collaborate on a bot that allows to control CI runs like retriggering certain jobs, requesting additional non-PR jobs to run - e.g. when you made changes to nightly, etc. Thanks everybody for being patient and so collaborative during this transisition time. I'm looking forward to everybodys contributions. Best regards, Marco [1]: https://github.com/apache/incubator-mxnet/tree/master/ci/jenkins On Sat, Dec 1, 2018 at 4:27 AM Marco de Abreu wrote: > Thanks Naveen and Gavin! > > #1 has been completed and every job has finished its processing. > > #2 is the ticket with infra: > https://issues.apache.org/jira/browse/INFRA-17346 > > I'm now waiting for their response. > > -Marco > > On Fri, Nov 30, 2018 at 8:25 PM Naveen Swamy wrote: > >> Hi Marco/Gavin, >> >> Thanks for the clarification. I was not aware that it has been tested on a >> separate test environment(this is what I was suggesting and make the >> changes in a more controlled manner), last time the change was made, many >> PRs were left dangling and developers had to go trigger and I triggered >> them at least 5 times before it succeeded today. >> >> Appreciate all the hard work to make CI better. >> >> -Naveen >> >> On Fri, Nov 30, 2018 at 8:50 AM Gavin M. Bell >> wrote: >> >> > Hey Folks, >> > >> > Marco has been running this change in dev, with flying colors, for some >> > time. This is not an experiment but a roll out that was announced. We >> also >> > decided to make this change post the release cut so limit the blast >> radius >> > from any critical obligations to the community. Marco is accountable >> for >> > this work and will address any issues that may occur as he has been put >> > on-call. We have, to our best ability, mitigated as much risk as >> possible >> > and now it is time to pull the trigger. The community will enjoy a bit >> > more visibility and clarity into the test process which will be >> > advantageous, as well as allowing us to extend our infrastructure in a >> way >> > that affords us more flexibility. >> > >> > No pending PRs will be impacted. >> > >> > Thank you for your support as we evolve this system to better serve the >> > community. >> > >> > -Gavin >> > >> > On Fri, Nov 30, 2018 at 5:23 PM Marco de Abreu >> > wrote: >> > >> > > Hello Naveen, this is not an experiment. Everything has been tested in >> > our >> > > test system and is considered working 100%. This is not a test but >> > actually >> > > the move into production - the merge into master happened a week ago. >> We >> > > now just have to put all PRs into the catalogue, which means that all >> PRs >> > > have to be analyzed with the new pipelines - the only thing that will >> be >> > > noticeable is that the CI is under higher load. >> > > >> > > The pending PRs will not be impacted. The existing pipeline is still >> > > running in parallel and everything will behave as before. >> > > >> > > -Marco >> > > >> > > On Fri, Nov 30, 2018 at 4:41 PM Naveen Swamy >> wrote: >> > > >> > > > Marco, run your experiments on a branch - set up, test it well and >> then >> > > > bring it to the master. >> > > > >> > > > > On Nov 30, 2018, at 6:53 AM, Marco de Abreu < >> > > > marco.g.ab...@googlemail.com.INVALID> wrote: >> > > > > >> > > > > Hello, >> > > > > >> > > > > I'm now moving forward with #1. I will try to get to #3 as soon as >> > > > possible >> > > > > to reduce parallel jobs in our CI. You might notice some >> unfinished >> > > > jobs. I >> > > > > will let you know as soon as this process has been completed. >> Until >> > > then, >> > > > > please bare with me since we have hundreds of jobs to run in >> order to >> > > > > validate all PRs. >> > > > > >> > > > > Best regards, >> > > > > Marco >> > > > > >> > > > > On Fri, Nov 30, 2018 at 1:36 AM Marco de Abreu < >> > > > marco.g.ab...@googlemail.com> >> > > > > wrote: >> > > > > >> > > > >> Hello, >> > > > >> >> > > > >> since the release branch has now been cut, I would like to move >> > > forward >> > >
Re: Apache Infra tickets for MXNet
Thanks for working through that with infra Marco. I think the process you outlined is good and being able to submit tickets without mentor approval is good for the project. Whoever puts the process on the wiki please reply with a link. Mike On Thu, Nov 29, 2018 at 11:45 PM Steffen Rochel wrote: > Thanks Marco. Cwiki seems a good place to document the policy. > Steffen > > On Thu, Nov 29, 2018 at 8:06 PM Marco de Abreu > wrote: > > > Hello everyone, > > > > I have just had a nice conversation with Greg Stein, VP of Apache Infra, > > about the topic of creating tickets against Apache Infra. > > > > In the past, we had the restriction that only IPMC members (speak, > mentors) > > were allowed to file tickets against Apache Infra. This was due past > issues > > where tickets have been created without previous discussions on dev@ and > > from people who were not PPMC members, thus creating too much churn. > > > > During the last year, the MXNet community has shown that we are able to > > adhere to the Apache ways. Thus the restrictions are being lifted and the > > following policy get set in place: > > > > - Only PPMC members are allowed to create tickets (if you can see > > priv...@mxnet.apache.org, you're good to go) > > - Committers are not allowed to create tickets (if you have write access > to > > GitHub but can't see priv...@mxnet.apache.org, you're not a PPMC member > > but > > a committer) > > - Contributors are not allowed to create tickets (if you're neither a > PPMC > > member, nor a committer, then you're a contributor) > > - There always has to be a dev@ thread before a ticket can be created. > > That > > thread has to be linked in that said ticket. > > - Always search for a solution yourself (self-service) before engaging > with > > Apache Infra. > > > > I'm not sure about a good place to document these guidelines. If somebody > > has a good idea where we should write them down, please feel free to drop > > me a link and I'll paste them in there. > > > > Thanks everybody for the great collaboration around Apache Infra tickets! > > This was a prime example of a community working together. > > > > Best regards, > > Marco > > >
