I think this is better to explain from English native speakers. :) >From my understanding, cut sometimes is about having the commit id(point) to begin the release process. publish is more closing to release done. But from translating perspective, such as in the Chinese perspective, there is no much difference, even they are even truly having the above difference(maybe not).
Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun <zhangyong...@apache.org> 于2021年5月17日周一 下午11:10写道： > Hi, > > In the 'Creating an Apache Release' section of the graduation guide [1], I > am a little confused by the statements of 'cut a release', 'publish a > release' and 'create a release'. What's the difference between them? > I really know what this section means generally, but when I tried to > translate I met difficult. > I thought these three statements are equal previous, but I'm not sure now. > > > Podlings do not need to actually *publish *a release to demonstrate that > they understand how to accomplish such a feat. However, creating a release > that is approved by the incubator project management committee is usually > the simplest way to do this. > > What does the highlight *publish* imply? Anyway, I get 'create a release' > is better. > > > If you are going to cut a release (which is highly recommended), then > please read the Incubator Release Management Guide for hints, tips and > guidelines for cutting a release that will get approved by the IPMC without > problems. > > Why recommend 'cut a release' this time instead of 'create a release'? > > I am trying to translate this guide to local language, it's very appreciate > if anyone could help. > > > [1] http://incubator.apache.org/guides/graduation.html#creating_an_apache > _release > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere >
