On Mon, May 17, 2021 at 11:10 AM Zhang Yonglun <zhangyong...@apache.org> wrote:
> 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. > I think from a translation POV you should treat all of these statements the same. We may even find that it makes sense to simplify the guide to cut down on englsih specific idioms that may not translate well. They all essentially mean that the graduating podling: - Knows the licensing requirements of what code is going into your *source release* - Knows where to stage the source release - Knows how to conduct votes on the releases - Knows how to archive old releases > > > 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 >
