I’ve documented the detailed steps below on the process of migrating MXNet
-> Apache for open feedback and discussion.
Essentially Amazon will be providing the GPU build slaves to be hooked into
Apache’s Jenkins build Master. We’ll first make sure that Apache can build
a fork of MXNet, before offi
Hi Sebastian. Thank you for spotting this. We will be looking into this and
send an update later today.
Ly
On Thu, Jun 15, 2017 at 12:41 AM, Sebastian Schelter wrote:
> Hi,
>
> I think I found an typo in the documentation under
> http://mxnet.io/architecture/note_engine.html, in the pseudo code
Hi, I'm helping with the code migration of MXNet to Apache and need to set
up jobs on Jenkins. It seems I would need to be a committer (detailed
below) which I'm currently not. What would the group suggest for me in this
case?
https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-Howdo
I've posted an issue here: https://github.com/dmlc/mxnet/issues/6721
As soon as I get access to the original graphic I can make the change.
On Thu, Jun 15, 2017 at 9:09 AM, Ly Nguyen wrote:
> Hi Sebastian. Thank you for spotting this. We will be looking into this
> and send an u
voter.
>
> Hen
>
>
> On Sat, Jun 17, 2017 at 8:59 AM, Naveen Swamy wrote:
>
> > Ly,
> > Continuous Integration is an integral part of MXNet's development
> process,
> > you have been making great contributions in setting up Jenkins and the
> > relate
Jun 7, 2017 at 12:53 PM, Ly Nguyen wrote:
> I’ve documented the detailed steps below on the process of migrating MXNet
> -> Apache for open feedback and discussion.
>
> Essentially Amazon will be providing the GPU build slaves to be hooked
> into Apache’s Jenkins build Master. We
ve not got my email, I am wondering who are all on the
> > private@ list or is it not setup?
> >
> > Thanks, Naveen
> >
> > On Tue, Jun 20, 2017 at 10:33 AM, Ly Nguyen wrote:
> >
> > > I've confirmed with a few folks in the Apache Infra team that I inde
ite
https://issues.apache.org/jira/browse/INFRA-14479
4. Filed a ticket to reconfigure donated linux slaves
https://issues.apache.org/jira/browse/INFRA-14478
On Tue, Jun 27, 2017 at 1:10 PM, Ly Nguyen wrote:
> We are aiming to complete migration of MXNet to Apache by July 10. This
> involves transfer
ows pip package?
> >
> > Thanks, Naveen
> >
> >
> >
> > On Sat, Jul 1, 2017 at 12:14 AM, shiwen hu
> wrote:
> >
> > > what problem with windows ci?
> > >
> > > 2017-07-01 9:06 GMT+08:00 Ly Nguyen :
> > >
> > > >
>
> > Have a great weekend everyone!
> >
> > On Fri, Jul 7, 2017 at 6:07 PM, Dominic Divakaruni
> > wrote:
> > > great stuff!! glad to see this getting close!
> > >
> > > On Fri, Jul 7, 2017 at 3:47 PM, Ly Nguyen wrote:
> > >>
>
>From Mu:
Please preserve the following hooks after transferring:
-http://mxnet.io:8080/github-webhook/ (docs deployment)
-https://ci.appveyor.com/api/github/webhook
all other hooks can be removed
On Mon, Jul 10, 2017 at 12:00 PM, Ly Nguyen wrote:
> @Suneel I don't think so. We
checks/
On Mon, Jul 10, 2017 at 12:36 PM, Ly Nguyen wrote:
> From Mu:
> Please preserve the following hooks after transferring:
> -http://mxnet.io:8080/github-webhook/ (docs deployment)
> -https://ci.appveyor.com/api/github/webhook
> all other hooks can be removed
>
> On Mon,
Hi @KK, any updates from legal on whether excluding the R pkg is a solution
for our next release?
On Mon, Jul 10, 2017 at 10:49 AM, Qiang Kou wrote:
> Thank you for the info.
>
> As I understand, if we skip the R pkg when releasing the a new version of
> MXNet, everything is OK. This is can be d
Best,
>
> KK
>
> On Tue, Jul 11, 2017 at 10:50 AM, Ly Nguyen wrote:
>
> > Hi @KK, any updates from legal on whether excluding the R pkg is a
> solution
> > for our next release?
> >
> > On Mon, Jul 10, 2017 at 10:49 AM, Qiang Kou wrote:
> >
> &g
@mentors, we would like to hold a RC vote and release on Monday July 17th.
- Are there any blockers (i.e., licenses)?
- Can you validate the proposal below?
*PROPOSAL FOR JULY RELASE (version?):*
*Start voting THIS week. Release on Monday July 17th.*
1. Create signing keys
1. SKI
As mentioned in the migration FAQ, if you currently have any kind of write
access to MXNet repo, once migration happens, YOU WILL LOSE IT unless you
do the following.
If you haven't already, please link your Apache accounts (you need to
already be a committer) to Gitbox here: https://gitbox.apache
s from having
> > those SHAs in as many inboxes as possible, after all.
> >
> > Thanks,
> >
> > Markus
> >
> > On Tue, Jul 11, 2017 at 4:07 PM, Ly Nguyen wrote:
> > > @mentors, we would like to hold a RC vote and release on Monday July
> > 17th.
> &
> On 27.06.2017 23:02, Ly Nguyen wrote:
>
>> Now that I'm a committer and have an account (thanks all!) I still need
>> the
>> following to move migration forward:
>>
>> 1) Grant me access to Jenkins:
>> https://cwiki.apache.org/confluence/display/INFR
Hi Henri, checking in about this. Can Naveen and Mu gain access?
On Fri, Jul 14, 2017 at 3:11 PM, Ly Nguyen wrote:
> Hi, can we also add Naveen Swamy and Mu Li to the jobsadmin group so they
> have access to configure Jenkins?
>
> On Tue, Jun 27, 2017 at 2:19 PM, Sebastian w
Hi folks,
We've migrated our code base to Apache/incubator-mxnet:
https://github.com/apache/incubator-mxnet
Please help us test whether:
- your existing forks can continue to pull
- clone/fork from the old URL http://github.com/dmlc/mxnet as well as
the new URL
- make a pull request
Is there a preference for the email handle?
On Fri, Jul 28, 2017 at 1:44 PM, Yuan Tang wrote:
> This is quite annoying. Could anyone please change this?
>
> On Fri, Jul 28, 2017 at 4:25 PM Dom Divakaruni <
> dominic.divakar...@gmail.com>
> wrote:
>
> > Can we please do this?
> >
> > @Lnx2
> >
>
JIRA ticket: https://issues.apache.org/jira/browse/INFRA-14732
On Fri, Jul 28, 2017 at 2:10 PM, Naveen Swamy wrote:
> Can we move such emails to comm...@mxnet.incubator.apache.org or similar ?
>
> Whoever interested can subscribe on that.
>
> Thanks, Naveen
>
> On Fri, Jul 28, 2017 at 1:44 PM, Y
A more detailed release process for release managers as the target audience
has been documented here:
https://cwiki.apache.org/confluence/display/MXNET/Release+Process
There are some details such as example commands that are still TODOs and
will be added as we go through the first official release
We are starting the process to prepare for MXNET v0.11.0 release. We
have drafted release notes
https://cwiki.apache.org/confluence/display/MXNET/v0.11.0+Release+Notes
to cover the tasks under this release.
A release candidate will be cut on Monday, August 7th, and voting will
commence from then u
Hi Isabelle,
As Mu mentioned we are in the process of transferring our website to
http://mxnet.incubator.apache.org so nothing there is official. Thank you
for the note about the disclaimer about be an incubator though.
Is this the writing that we need to add?:
"Apache MXNet (incubating) is an e
Hi, a pending item for our release is adding license headers to all source
files. We first need to stabilize the CI before we can merge the license
headers, which is a very big change. To avoid introducing any breaking
changes, we need to halt merges of new features. Until we have stability
and upd
/foundation/marks/pmcs#introduction
>
> Cheers,
> Chris
>
>
> On 8/4/17, 11:20 AM, "Ly Nguyen" wrote:
>
> Hi Isabelle,
>
> As Mu mentioned we are in the process of transferring our website to
> http://mxnet.incubator.apache.org so nothing
This is the vote to release Apache MXNet (incubating) version 0.11.0.
Voting will start now (Saturday, August 12, 2017 9:26 AM UTC) and
close Tuesday, August 15, 2017 9:26 AM UTC.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/v0.11.0+Release+Notes
Link to release candid
As mentioned by Sheng this is an ongoing issue and a JIRA ticket has been
filed to Apache Infra team, will follow up tomorrow if status hasn't been
updated. https://issues.apache.org/jira/browse/INFRA-14840
On Sun, Aug 13, 2017 at 9:21 AM, Nan Zhu wrote:
> no, I mean the CI system in our github
I turned off PR builds to prioritize testing our v0.11.0 branch for cutting
RC1. The following PR builds that were in progress, and any new PR's or
updated PR's, will be affected and will pick back up once we cut the
release and re-enable PR builds tonight:
7433
7442
7458
2
7498
On Mon, Aug 14, 2017 at 3:32 PM, Ly Nguyen wrote:
> I turned off PR builds to prioritize testing our v0.11.0 branch for
> cutting RC1. The following PR builds that were in progress, and any new
> PR's or updated PR's, will be affected and will pick back up once we cut
&
I agree with comments on not breaking momentum by rebranding the name. It's
also my first time hearing about the pronunciation being "mixnet" and not
"m-x-net" so that clarification, along with the motivation behind the name,
feature parity, would strengthen the brand more.
To that point, Sean Com
32 matches
Mail list logo
