Re: Julia Package Release Process
I put the note. I'm fine with leaving the issue tracker at that. On 1/8/19 1:28 AM, Chiyuan Zhang wrote: I just checked that I have ability to disable the issue tracker on dmlc/MXNet.jl. Iblis: let me know if you would like me to disable the issue (after you transferred active ones to mxnet main repo). Disabling issues makes the whole 'issues' tab disappear. I think we can also adopt clojure repo's approach, instead of closing the issues completely, put a note there to point to the main repo. Best, Chiyuan On Mon, Jan 7, 2019 at 9:13 AM Iblis Lin wrote: Yes, I have them on main repo. But for MXNet.jl, I'm repo collaborator. Anyway, I'm browsing the issues and migrating some of them. On 1/8/19 12:46 AM, Chris Olivier wrote: Do you not have write permissions on mxnet repo? On Mon, Jan 7, 2019 at 6:13 AM iblis wrote: just found that I don't have the permission to transfer issues of dmlc/MXNet.jl. Could anyone help me on this? On 1/7/19 12:16 PM, iblis wrote: okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via https://help.github.com/articles/transferring-an-issue-to-another-repository/ ) On 1/7/19 12:17 AM, Chris Olivier wrote: +1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
Re: Julia Package Release Process
I just checked that I have ability to disable the issue tracker on dmlc/MXNet.jl. Iblis: let me know if you would like me to disable the issue (after you transferred active ones to mxnet main repo). Disabling issues makes the whole 'issues' tab disappear. I think we can also adopt clojure repo's approach, instead of closing the issues completely, put a note there to point to the main repo. Best, Chiyuan On Mon, Jan 7, 2019 at 9:13 AM Iblis Lin wrote: > Yes, I have them on main repo. > But for MXNet.jl, I'm repo collaborator. > Anyway, I'm browsing the issues and migrating some of them. > > On 1/8/19 12:46 AM, Chris Olivier wrote: > > Do you not have write permissions on mxnet repo? > > > > On Mon, Jan 7, 2019 at 6:13 AM iblis wrote: > > > >> just found that I don't have the permission to transfer issues of > >> dmlc/MXNet.jl. > >> Could anyone help me on this? > >> > >> On 1/7/19 12:16 PM, iblis wrote: > >>> okay. > >>> Before disabling the issue tracker, I'm going to transfer the issue > >>> from MXNet.jl to main repo. > >>> (via > >> > https://help.github.com/articles/transferring-an-issue-to-another-repository/ > >> ) > >>> > >>> On 1/7/19 12:17 AM, Chris Olivier wrote: > +1 for disabling issue tracker and putting a note on original repo (if > >> it > isn’t already there) that work/issue tracking has moved to mxnet > (using > julia label in github or Jira). m > > > On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: > > > Before PR #10149 got merged (Oct 5, 2018) into main repo, > > julia code is developed and maintained in the separate repo -- > > dmlc/MXNet.jl. > > > > After that PR, there are no further development happened in > >> dmlc/MXNet.jl. > > We work with the main repo now. > > But the original MXNet.jl repo is still there, it just isn't deleted > or > > archived yet. > > I receive some issue ticks from this repo occasionally, > > maybe we should just disable the issue tracker of it. > > > >> Does it work with other frameworks other than mxnet? > > hmm, I'm not sure what you mean. > > > > On 1/6/19 1:18 PM, Chris Olivier wrote: > >> Curious: Why is the julia code maintained in a separate repo? I was > > under > >> the impression that it was donated/permanently merged into the mxnet > > source > >> tree. Does it work with other frameworks other than mxnet? > >> > >> On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin > >> wrote: > >> > >>> If there is trademark issue, how about this option: > >>> 3) transferring the MXNet.jl repo ownership from DMLC to > Apache. > >>> > >>> On 1/6/19 6:45 AM, Justin Mclean wrote: > Hi, > > > 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > > It's under DMLC. I have the committer bit of this > repo. > > I'm not 100% sure that would be allowed from a branding/trademark > >>> perspective, any distribution owned by a 3rd party can't be called > > "Apache > >>> MXNet". > > > 2) A new repo under ASF's organization? > > That seems preferable I think. > > Thanks, > Justin > > >>> > >>> -- > >>> Iblis Lin > >>> 林峻頤 > >>> > >> > > > > -- > > Iblis Lin > > 林峻頤 > > > > >>> > >> > >> -- > >> Iblis Lin > >> 林峻頤 > >> > > > > -- > Iblis Lin > 林峻頤 >
Re: Julia Package Release Process
Yes, I have them on main repo. But for MXNet.jl, I'm repo collaborator. Anyway, I'm browsing the issues and migrating some of them. On 1/8/19 12:46 AM, Chris Olivier wrote: Do you not have write permissions on mxnet repo? On Mon, Jan 7, 2019 at 6:13 AM iblis wrote: just found that I don't have the permission to transfer issues of dmlc/MXNet.jl. Could anyone help me on this? On 1/7/19 12:16 PM, iblis wrote: okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via https://help.github.com/articles/transferring-an-issue-to-another-repository/ ) On 1/7/19 12:17 AM, Chris Olivier wrote: +1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
Re: Julia Package Release Process
Do you not have write permissions on mxnet repo? On Mon, Jan 7, 2019 at 6:13 AM iblis wrote: > just found that I don't have the permission to transfer issues of > dmlc/MXNet.jl. > Could anyone help me on this? > > On 1/7/19 12:16 PM, iblis wrote: > > okay. > > Before disabling the issue tracker, I'm going to transfer the issue > > from MXNet.jl to main repo. > > (via > https://help.github.com/articles/transferring-an-issue-to-another-repository/ > ) > > > > On 1/7/19 12:17 AM, Chris Olivier wrote: > >> +1 for disabling issue tracker and putting a note on original repo (if > it > >> isn’t already there) that work/issue tracking has moved to mxnet (using > >> julia label in github or Jira). m > >> > >> > >> On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: > >> > >>> Before PR #10149 got merged (Oct 5, 2018) into main repo, > >>> julia code is developed and maintained in the separate repo -- > >>> dmlc/MXNet.jl. > >>> > >>> After that PR, there are no further development happened in > dmlc/MXNet.jl. > >>> We work with the main repo now. > >>> But the original MXNet.jl repo is still there, it just isn't deleted or > >>> archived yet. > >>> I receive some issue ticks from this repo occasionally, > >>> maybe we should just disable the issue tracker of it. > >>> > Does it work with other frameworks other than mxnet? > >>> hmm, I'm not sure what you mean. > >>> > >>> On 1/6/19 1:18 PM, Chris Olivier wrote: > Curious: Why is the julia code maintained in a separate repo? I was > >>> under > the impression that it was donated/permanently merged into the mxnet > >>> source > tree. Does it work with other frameworks other than mxnet? > > On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin > wrote: > > > If there is trademark issue, how about this option: > > 3) transferring the MXNet.jl repo ownership from DMLC to Apache. > > > > On 1/6/19 6:45 AM, Justin Mclean wrote: > >> Hi, > >> > >>> 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > >>>It's under DMLC. I have the committer bit of this repo. > >> > >> I'm not 100% sure that would be allowed from a branding/trademark > > perspective, any distribution owned by a 3rd party can't be called > >>> "Apache > > MXNet". > >> > >>> 2) A new repo under ASF's organization? > >> > >> That seems preferable I think. > >> > >> Thanks, > >> Justin > >> > > > > -- > > Iblis Lin > > 林峻頤 > > > > >>> > >>> -- > >>> Iblis Lin > >>> 林峻頤 > >>> > >> > > > > -- > Iblis Lin > 林峻頤 >
Re: Julia Package Release Process
I think you need admin permissions on both repos to do that which might be problematic. Since it looks like there is just one recent open issue, can you replicate it on the main MXNet repo and have a link to the original issue? FWIW - When the Clojure package joined the main repo. I just put instructions on the main page to open issues against the main repo instead https://github.com/gigasquid/clojure-mxnet - Carin On Mon, Jan 7, 2019 at 9:13 AM iblis wrote: > just found that I don't have the permission to transfer issues of > dmlc/MXNet.jl. > Could anyone help me on this? > > On 1/7/19 12:16 PM, iblis wrote: > > okay. > > Before disabling the issue tracker, I'm going to transfer the issue > > from MXNet.jl to main repo. > > (via > https://help.github.com/articles/transferring-an-issue-to-another-repository/ > ) > > > > On 1/7/19 12:17 AM, Chris Olivier wrote: > >> +1 for disabling issue tracker and putting a note on original repo (if > it > >> isn’t already there) that work/issue tracking has moved to mxnet (using > >> julia label in github or Jira). m > >> > >> > >> On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: > >> > >>> Before PR #10149 got merged (Oct 5, 2018) into main repo, > >>> julia code is developed and maintained in the separate repo -- > >>> dmlc/MXNet.jl. > >>> > >>> After that PR, there are no further development happened in > dmlc/MXNet.jl. > >>> We work with the main repo now. > >>> But the original MXNet.jl repo is still there, it just isn't deleted or > >>> archived yet. > >>> I receive some issue ticks from this repo occasionally, > >>> maybe we should just disable the issue tracker of it. > >>> > Does it work with other frameworks other than mxnet? > >>> hmm, I'm not sure what you mean. > >>> > >>> On 1/6/19 1:18 PM, Chris Olivier wrote: > Curious: Why is the julia code maintained in a separate repo? I was > >>> under > the impression that it was donated/permanently merged into the mxnet > >>> source > tree. Does it work with other frameworks other than mxnet? > > On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin > wrote: > > > If there is trademark issue, how about this option: > > 3) transferring the MXNet.jl repo ownership from DMLC to Apache. > > > > On 1/6/19 6:45 AM, Justin Mclean wrote: > >> Hi, > >> > >>> 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > >>>It's under DMLC. I have the committer bit of this repo. > >> > >> I'm not 100% sure that would be allowed from a branding/trademark > > perspective, any distribution owned by a 3rd party can't be called > >>> "Apache > > MXNet". > >> > >>> 2) A new repo under ASF's organization? > >> > >> That seems preferable I think. > >> > >> Thanks, > >> Justin > >> > > > > -- > > Iblis Lin > > 林峻頤 > > > > >>> > >>> -- > >>> Iblis Lin > >>> 林峻頤 > >>> > >> > > > > -- > Iblis Lin > 林峻頤 >
Re: Julia Package Release Process
just found that I don't have the permission to transfer issues of dmlc/MXNet.jl. Could anyone help me on this? On 1/7/19 12:16 PM, iblis wrote: okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via https://help.github.com/articles/transferring-an-issue-to-another-repository/) On 1/7/19 12:17 AM, Chris Olivier wrote: +1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
Re: Julia Package Release Process
okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via https://help.github.com/articles/transferring-an-issue-to-another-repository/) On 1/7/19 12:17 AM, Chris Olivier wrote: +1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
Re: Julia Package Release Process
+1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: > Before PR #10149 got merged (Oct 5, 2018) into main repo, > julia code is developed and maintained in the separate repo -- > dmlc/MXNet.jl. > > After that PR, there are no further development happened in dmlc/MXNet.jl. > We work with the main repo now. > But the original MXNet.jl repo is still there, it just isn't deleted or > archived yet. > I receive some issue ticks from this repo occasionally, > maybe we should just disable the issue tracker of it. > > > Does it work with other frameworks other than mxnet? > hmm, I'm not sure what you mean. > > On 1/6/19 1:18 PM, Chris Olivier wrote: > > Curious: Why is the julia code maintained in a separate repo? I was > under > > the impression that it was donated/permanently merged into the mxnet > source > > tree. Does it work with other frameworks other than mxnet? > > > > On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: > > > >> If there is trademark issue, how about this option: > >> 3) transferring the MXNet.jl repo ownership from DMLC to Apache. > >> > >> On 1/6/19 6:45 AM, Justin Mclean wrote: > >>> Hi, > >>> > 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > It's under DMLC. I have the committer bit of this repo. > >>> > >>> I'm not 100% sure that would be allowed from a branding/trademark > >> perspective, any distribution owned by a 3rd party can't be called > "Apache > >> MXNet". > >>> > 2) A new repo under ASF's organization? > >>> > >>> That seems preferable I think. > >>> > >>> Thanks, > >>> Justin > >>> > >> > >> -- > >> Iblis Lin > >> 林峻頤 > >> > > > > -- > Iblis Lin > 林峻頤 >
Re: Julia Package Release Process
Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
Re: Julia Package Release Process
Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: > If there is trademark issue, how about this option: >3) transferring the MXNet.jl repo ownership from DMLC to Apache. > > On 1/6/19 6:45 AM, Justin Mclean wrote: > > Hi, > > > >> 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > >> It's under DMLC. I have the committer bit of this repo. > > > > I'm not 100% sure that would be allowed from a branding/trademark > perspective, any distribution owned by a 3rd party can't be called "Apache > MXNet". > > > >> 2) A new repo under ASF's organization? > > > > That seems preferable I think. > > > > Thanks, > > Justin > > > > -- > Iblis Lin > 林峻頤 >
Re: Julia Package Release Process
If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤
Re: Julia Package Release Process
On 1/6/19 5:48 AM, Carin Meier wrote: Do you know of any other Julia Apache projects? Maybe we could look and see how they are doing it. well, seems no. -- Iblis Lin
Re: Julia Package Release Process
Hi, > 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". > 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin
Re: Julia Package Release Process
Hi, > I know there are some conditions under which Apache can distribute releases > downstream. Short version it's fine to distribute packages that consist of voted on ASF releases, but you are not allowed to create and distribute packages that contain un-released code. See also [1] Thanks, Justin 1. https://issues.apache.org/jira/browse/LEGAL-427
Re: Julia Package Release Process
Iblis, Thank you for your work in developing a release process for the Julia package. Thanks especially for explaining it in way that is approachable for others not familiar with the Julia dependency management system. I know there are some conditions under which Apache can distribute releases downstream. >From this conversation https://issues.apache.org/jira/browse/LEGAL-270 It seems that "it is appropriate to distribute official releases through downstream channels". Another github repo seems like it could be a downstream channel for ease with Julia deps. I don't know whether the DMLC repo would be a problem with the naming or as long as it specified it was a distribution of the Apache (incubating) MXNet project it would be ok. Do you know of any other Julia Apache projects? Maybe we could look and see how they are doing it. Best, Carin On Sat, Jan 5, 2019 at 11:00 AM iblis wrote: > Hello MXNet community, > > After the Julia package has been imported into the main repo, > the next unresolved issue is establishing the releasing process for Julia. > > The PR #12845, which is for upgrading Julia package to work with Julia > v0.7+, > is ready for review at this moment. > I want to release the Julia part along with the next mxnet major release > (v1.5, I think). > > We imported the Julia package to make it part of the CI validation chain. > And merging code into main repo makes Julia release process different from > normal. > > At first, let me describe a usual release process for a Julia package. > I will try to explain it with corresponding ideas in Python. > > 1.Package manager in Julia: > There are a module from stdlib named `Pkg` served as the package > manager in Julia, > like Python's `pip`. > > 2. The package registry and package source: > The package manager will download the desired packages from a default > registry. > In Python, pip will conduct two actions before installing packags: > (1) Search the metadata (like pkg name, version, ...etc) > from the CheeseShop (a.k.a PyPI) for users. > (2) Fetch them from the CheeseShop if matched. > > In Julia, there is a default registry to hold the packages metadata, > hosted on GitHub: >https://github.com/JuliaLang/METADATA.jl > > And where to fetch the package? The aren't a center for download > packages. > It's unlike Python's idea, we don't upload package to a center server > in case of Julia. > > The package manager will fetch stuffs from the URL listed in the > metadata. > It should be a valid git URL for git-clone. > e.g. For the package `Distributions`: > > https://github.com/JuliaLang/METADATA.jl/blob/metadata-v2/Distributions/url > Most of the packages use GitHub for hosting code. > > 3. A valid package directory structure > > In the process of package installation, > Python's pip will run `./setup.py` from unpacked package dir. > This is kind of protocol between package developer and package > manager. > > In Julia, the package manager run `./deps/build.jl` from the > git-cloned dir. > > Here comes an issue of mxnet's main repo. > The Julia package is collected under the subdir `./julia/`, so the > setup script > in our case is `./julia/deps/build.jl`. > This breaks the protocol. > > Also, in runtime, there is another protocol for phase of module > loading. > The entry point of a module must be `./src/PackageName.jl`. > In our repo, it's `./julia/src/MXNet.jl`. > So, the directory structure of mxnet main repo is invalid for Julia > package manager. > Putting the url of main repo as package metadata will not work. > > The proposed solution: > >To provide a valid dir structure, it need a standalone git repo. >We can just treat this standalone repo as the place to "upload" package > code, >just like uploading Python package to PyPI in every release. > >I want to discuss about the home of this standalone repo. > 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > It's under DMLC. I have the committer bit of this repo. > 2) A new repo under ASF's organization? > 3) Anything else? > >I will vote for option (1). > > >The actual process in detail: > 1) Split the julia dir out via git-subtree > ``` > cd /path/to/mxnet/ > git subtree split -P julia -b MXNet_jl > ``` > > 2) Push the branch `MXNet_jl` to the standalone git repo mentioned in > previous section. > > 3) Push a new tag for MXNet.jl. The version number is same as the > mxnet main repo. > > 4) Make a release page via GitHub release button. > > 5) Then, updating metadata to Julia package registry will be > automated by the bot. > https://github.com/attobot/attobot > > 6) Relax! > > -- > Iblis Lin >
Julia Package Release Process
Hello MXNet community, After the Julia package has been imported into the main repo, the next unresolved issue is establishing the releasing process for Julia. The PR #12845, which is for upgrading Julia package to work with Julia v0.7+, is ready for review at this moment. I want to release the Julia part along with the next mxnet major release (v1.5, I think). We imported the Julia package to make it part of the CI validation chain. And merging code into main repo makes Julia release process different from normal. At first, let me describe a usual release process for a Julia package. I will try to explain it with corresponding ideas in Python. 1.Package manager in Julia: There are a module from stdlib named `Pkg` served as the package manager in Julia, like Python's `pip`. 2. The package registry and package source: The package manager will download the desired packages from a default registry. In Python, pip will conduct two actions before installing packags: (1) Search the metadata (like pkg name, version, ...etc) from the CheeseShop (a.k.a PyPI) for users. (2) Fetch them from the CheeseShop if matched. In Julia, there is a default registry to hold the packages metadata, hosted on GitHub: https://github.com/JuliaLang/METADATA.jl And where to fetch the package? The aren't a center for download packages. It's unlike Python's idea, we don't upload package to a center server in case of Julia. The package manager will fetch stuffs from the URL listed in the metadata. It should be a valid git URL for git-clone. e.g. For the package `Distributions`: https://github.com/JuliaLang/METADATA.jl/blob/metadata-v2/Distributions/url Most of the packages use GitHub for hosting code. 3. A valid package directory structure In the process of package installation, Python's pip will run `./setup.py` from unpacked package dir. This is kind of protocol between package developer and package manager. In Julia, the package manager run `./deps/build.jl` from the git-cloned dir. Here comes an issue of mxnet's main repo. The Julia package is collected under the subdir `./julia/`, so the setup script in our case is `./julia/deps/build.jl`. This breaks the protocol. Also, in runtime, there is another protocol for phase of module loading. The entry point of a module must be `./src/PackageName.jl`. In our repo, it's `./julia/src/MXNet.jl`. So, the directory structure of mxnet main repo is invalid for Julia package manager. Putting the url of main repo as package metadata will not work. The proposed solution: To provide a valid dir structure, it need a standalone git repo. We can just treat this standalone repo as the place to "upload" package code, just like uploading Python package to PyPI in every release. I want to discuss about the home of this standalone repo. 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. 2) A new repo under ASF's organization? 3) Anything else? I will vote for option (1). The actual process in detail: 1) Split the julia dir out via git-subtree ``` cd /path/to/mxnet/ git subtree split -P julia -b MXNet_jl ``` 2) Push the branch `MXNet_jl` to the standalone git repo mentioned in previous section. 3) Push a new tag for MXNet.jl. The version number is same as the mxnet main repo. 4) Make a release page via GitHub release button. 5) Then, updating metadata to Julia package registry will be automated by the bot. https://github.com/attobot/attobot 6) Relax! -- Iblis Lin
