Here's what I did for the past few releases: 1. For 3.1.1 - check out the rc version tag locally in git and tag it with the release version. (i.e. duplicate 1.5.1.rc0 and name it 1.5.1) - edit the last release candidate pre-release on github. update the title and tag to reflect the new release, and uncheck this is a pre-release checkbox. - update the release artifact in the release with the artifacts from 3.1.2. - delete the old rc tag locally and on github.
2. For 3.1.2 - Since folder name needs to be changed inside the archive, the signature and hash need to be produced again. I usually just untar the old file, rename the folder name to remove mentions of "rc", and follow step 1.10 to tar, sign, and digest. - SVN repo also needs to be updated with the correct folder name and path, and the updated artifacts. The end result should be that the old rc artifacts are removed from the dev repo, and the release artifacts are uploaded to the dist repo. 3. Aaron has been helping with 3.2. -sz On 2019/09/28 20:47:37, Lin Yuan <apefor...@gmail.com> wrote: > Ping @Sheng and @Lai who released 1.5.0 for help. > > Could you please update the Release Process doc after you find the right > answers to these questions? > > Thanks, > > Lin > > On Sat, Sep 28, 2019 at 7:49 AM Tao Lv <ta...@apache.org> wrote: > > > Hi dev, > > > > I'm glad to say that the rc0 of 1.5.1 patch release has passed the vote on > > general@. Please find the voting thread at: > > > > https://lists.apache.org/thread.html/282f7911768dab61ddf8f70adcce34ef0afb285046093b3ff0bafb7e@%3Cgeneral.incubator.apache.org%3E > > > > > > Now I'm proceeding the release process and have several questions there. > > Hope someone can help to answer: > > > > 1. Change the 1.5.1.rc0 tag to formal 1.5.1. Seems the step 3.1.1 on the > > cwiki page [1] doesn't work. It says: > > > > "Go to the GitHub repo’s “releases” tab > > > > Click “Draft a new release” > > > > Provide the release tag in the form of “<major>.<minor>.<patch>” > > Select the commit by clicking Target: master > the passing release > > candidate tag" > > > > But I cannot find "the passing release candidate tag" in the drop list. > > There're branches and recent commits. Once I create a new tag, how about > > the old tag of 1.5.1.rc0? > > > > 2. Step 3.1.2 is also confusing to me. Not sure what should be done at step > > 3 and what need to be uploaded at step 4. > > > > 3. As we have a new website now, I guess there are some changes for the > > step 3.2. Can anyone help to clarify this? > > > > Thanks, > > -tao > > > > [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process > > >
