I think we can continue to use the same path for storage. The version numbers are self-evident to help tell these wheels apart from other nightly builds.
Thanks, Sheng On 2021/02/17 20:16:24, Zhu Zhaoqi <[email protected]> wrote: > Hi Wei, > > Thanks for creating this thread. I think a quick way to automate docker > image/linux pypi wheel generation is to reuse our existing cd pipelines. > The release manager can just trigger a cd task pointing to the release tag > and download the image/wheels. (docker images are not being uploaded now > but we can re-enable this) One thing that I would like to discuss is where > to upload the files -- currently we use https://dist.mxnet.io/python/ for > the nightly wheels. Maybe we can create a new directory under > https://dist.mxnet.io/ for the mxnet release docker images and pypi wheels? > > Thanks > Zhaoqi > > Sheng Zha <[email protected]> 于2021年2月17日周三 上午11:33写道： > > > Hi Wei, > > > > Thank you for bringing this up. It's definitely helpful and > > appreciated to keep the release run-book up-to-date. If you are unsure > > of any part or have specific issues you'd like to discuss, feel free > > to bring to the list. > > > > Thanks, > > Sheng > > > > On Wed, Feb 17, 2021 at 2:25 PM Wei Chu <[email protected]> wrote: > > > > > > Hi dev community, > > > The MXNet release runbook is used as the instruction for each new > > version release: > > > https://cwiki.apache.org/confluence/display/MXNET/Release+Process > > > The runbook has not been updated for a while and contains broken > > links/outdated contents. There’s also effort being made to improve and > > automate the process since then, which is not included in the runbook. I > > propose we update the release runbook to make the release process smoother > > and easier. Does anyone have any input or suggestions? > > > > > > Best, > > > Wei > > > > > >
