You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Zhang Yonglun <zh...@apache.org> on 2021/05/17 15:10:06 UTC
How to understand cut a release
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
Re: How to understand cut a release
Posted by "John D. Ament" <jo...@gmail.com>.
On Mon, May 17, 2021 at 11:10 AM Zhang Yonglun <zh...@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
>
Re: How to understand cut a release
Posted by Zhang Yonglun <zh...@apache.org>.
Thanks for John and Sheng pointed out these statements can be treated
equally. If so, I can do a paraphrase instead of a direct translation.
--
Zhang Yonglun
Apache ShenYu (Incubating)
Apache ShardingSphere
Sheng Wu <wu...@gmail.com> 于2021年5月17日周一 下午11:20写道：
> 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 <zh...@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
> >
>
Re: How to understand cut a release
Posted by Sheng Wu <wu...@gmail.com>.
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 <zh...@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
>
Re: How to understand cut a release
Posted by Dave Fisher <wa...@comcast.net>.
Sent from my iPhone
> On May 19, 2021, at 7:45 PM, Zhang Yonglun <zh...@apache.org> wrote:
>
> Hi Craig,
>
> Thanks for your reply.
>
> Actually, I followed this guide [1] and created a pull request [2] to the
> incubator repo [3] yesterday. Could you help to review?
>
> Besides, are there any relevant steps should be done together in the ASF
> Website [4] you mentioned?
Make a pull request and it will be reviewed. The site is newly migrated.
All the best,
Dave
>
>
>
> [1] http://incubator.apache.org/guides/website.html
> [2] https://github.com/apache/incubator/pull/93/files
> [3] https://github.com/apache/incubator
> [4] https://github.com/apache/www-site/
>
> --
>
> Zhang Yonglun
> Apache ShenYu (Incubating)
> Apache ShardingSphere
>
>
> Craig Russell <ap...@gmail.com> 于2021年5月20日周四 上午4:51写道：
>
>> Hi Yonglun,
>>
>>> On May 18, 2021, at 8:27 PM, Zhang Yonglun <zh...@apache.org>
>> wrote:
>>>
>>> Hi Craig,
>>>
>>> Got it. Thank you for the detailed explanation.
>>>
>>> I'd like to update the doc to reflect the two phase to making releases.
>>
>> That would be great. You can submit a patch here:
>> https://github.com/apache/www-site/
>>
>> It is not quite live yet but that's where the content will be shortly.
>>
>> Best,
>> Craig
>>>
>>> --
>>>
>>> Zhang Yonglun
>>> Apache ShenYu (Incubating)
>>> Apache ShardingSphere
>>>
>>>
>>> Craig Russell <ap...@gmail.com> 于2021年5月19日周三 上午8:17写道：
>>>
>>>> Hi,
>>>>
>>>> I'd say that there are two distinct parts to making releases, and would
>>>> recommend that we update the docs to reflect:
>>>>
>>>> 1. "Preparing a release" is something that is done by a release manager.
>>>> Some documentation refers to this as "cutting" a release. Preparing a
>>>> release means following the project-specific instructions for creating
>> the
>>>> release artifacts and putting them in a repository that is a staging
>> area
>>>> for voting and subsequent publishing the release.
>>>>
>>>> 2. "Publishing a release" is done after the podling and then the IPMC
>>>> approve the release that has been prepared, using a formal [VOTE]
>> process.
>>>> If the vote fails, the release manager can prepare an improved release.
>>>> Publishing means that the release artifacts are moved to the official
>>>> distribution area where they are picked up by the mirror system.
>>>>
>>>> So, cutting a release == creating a release == preparing a release
>>>> but these != publishing a release.
>>>>
>>>> Craig
>>>>
>>>>> On May 17, 2021, at 8:10 AM, Zhang Yonglun <zh...@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.
>>>>>
>>>>>> 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
>>>>
>>>> Craig L Russell
>>>> clr@apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>
>> Craig L Russell
>> clr@apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to understand cut a release
Posted by Zhang Yonglun <zh...@apache.org>.
Hi Craig,
Thanks for your reply.
Actually, I followed this guide [1] and created a pull request [2] to the
incubator repo [3] yesterday. Could you help to review?
Besides, are there any relevant steps should be done together in the ASF
Website [4] you mentioned?
[1] http://incubator.apache.org/guides/website.html
[2] https://github.com/apache/incubator/pull/93/files
[3] https://github.com/apache/incubator
[4] https://github.com/apache/www-site/
--
Zhang Yonglun
Apache ShenYu (Incubating)
Apache ShardingSphere
Craig Russell <ap...@gmail.com> 于2021年5月20日周四 上午4:51写道：
> Hi Yonglun,
>
> > On May 18, 2021, at 8:27 PM, Zhang Yonglun <zh...@apache.org>
> wrote:
> >
> > Hi Craig,
> >
> > Got it. Thank you for the detailed explanation.
> >
> > I'd like to update the doc to reflect the two phase to making releases.
>
> That would be great. You can submit a patch here:
> https://github.com/apache/www-site/
>
> It is not quite live yet but that's where the content will be shortly.
>
> Best,
> Craig
> >
> > --
> >
> > Zhang Yonglun
> > Apache ShenYu (Incubating)
> > Apache ShardingSphere
> >
> >
> > Craig Russell <ap...@gmail.com> 于2021年5月19日周三 上午8:17写道：
> >
> >> Hi,
> >>
> >> I'd say that there are two distinct parts to making releases, and would
> >> recommend that we update the docs to reflect:
> >>
> >> 1. "Preparing a release" is something that is done by a release manager.
> >> Some documentation refers to this as "cutting" a release. Preparing a
> >> release means following the project-specific instructions for creating
> the
> >> release artifacts and putting them in a repository that is a staging
> area
> >> for voting and subsequent publishing the release.
> >>
> >> 2. "Publishing a release" is done after the podling and then the IPMC
> >> approve the release that has been prepared, using a formal [VOTE]
> process.
> >> If the vote fails, the release manager can prepare an improved release.
> >> Publishing means that the release artifacts are moved to the official
> >> distribution area where they are picked up by the mirror system.
> >>
> >> So, cutting a release == creating a release == preparing a release
> >> but these != publishing a release.
> >>
> >> Craig
> >>
> >>> On May 17, 2021, at 8:10 AM, Zhang Yonglun <zh...@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.
> >>>
> >>>> 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
> >>
> >> Craig L Russell
> >> clr@apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: How to understand cut a release
Posted by Craig Russell <ap...@gmail.com>.
Hi Yonglun,
> On May 18, 2021, at 8:27 PM, Zhang Yonglun <zh...@apache.org> wrote:
>
> Hi Craig,
>
> Got it. Thank you for the detailed explanation.
>
> I'd like to update the doc to reflect the two phase to making releases.
That would be great. You can submit a patch here:
https://github.com/apache/www-site/
It is not quite live yet but that's where the content will be shortly.
Best,
Craig
>
> --
>
> Zhang Yonglun
> Apache ShenYu (Incubating)
> Apache ShardingSphere
>
>
> Craig Russell <ap...@gmail.com> 于2021年5月19日周三 上午8:17写道：
>
>> Hi,
>>
>> I'd say that there are two distinct parts to making releases, and would
>> recommend that we update the docs to reflect:
>>
>> 1. "Preparing a release" is something that is done by a release manager.
>> Some documentation refers to this as "cutting" a release. Preparing a
>> release means following the project-specific instructions for creating the
>> release artifacts and putting them in a repository that is a staging area
>> for voting and subsequent publishing the release.
>>
>> 2. "Publishing a release" is done after the podling and then the IPMC
>> approve the release that has been prepared, using a formal [VOTE] process.
>> If the vote fails, the release manager can prepare an improved release.
>> Publishing means that the release artifacts are moved to the official
>> distribution area where they are picked up by the mirror system.
>>
>> So, cutting a release == creating a release == preparing a release
>> but these != publishing a release.
>>
>> Craig
>>
>>> On May 17, 2021, at 8:10 AM, Zhang Yonglun <zh...@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.
>>>
>>>> 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
>>
>> Craig L Russell
>> clr@apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to understand cut a release
Posted by Zhang Yonglun <zh...@apache.org>.
Hi Craig,
Got it. Thank you for the detailed explanation.
I'd like to update the doc to reflect the two phase to making releases.
--
Zhang Yonglun
Apache ShenYu (Incubating)
Apache ShardingSphere
Craig Russell <ap...@gmail.com> 于2021年5月19日周三 上午8:17写道：
> Hi,
>
> I'd say that there are two distinct parts to making releases, and would
> recommend that we update the docs to reflect:
>
> 1. "Preparing a release" is something that is done by a release manager.
> Some documentation refers to this as "cutting" a release. Preparing a
> release means following the project-specific instructions for creating the
> release artifacts and putting them in a repository that is a staging area
> for voting and subsequent publishing the release.
>
> 2. "Publishing a release" is done after the podling and then the IPMC
> approve the release that has been prepared, using a formal [VOTE] process.
> If the vote fails, the release manager can prepare an improved release.
> Publishing means that the release artifacts are moved to the official
> distribution area where they are picked up by the mirror system.
>
> So, cutting a release == creating a release == preparing a release
> but these != publishing a release.
>
> Craig
>
> > On May 17, 2021, at 8:10 AM, Zhang Yonglun <zh...@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.
> >
> >> 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
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: How to understand cut a release
Posted by Craig Russell <ap...@gmail.com>.
Hi,
I'd say that there are two distinct parts to making releases, and would recommend that we update the docs to reflect:
1. "Preparing a release" is something that is done by a release manager. Some documentation refers to this as "cutting" a release. Preparing a release means following the project-specific instructions for creating the release artifacts and putting them in a repository that is a staging area for voting and subsequent publishing the release.
2. "Publishing a release" is done after the podling and then the IPMC approve the release that has been prepared, using a formal [VOTE] process. If the vote fails, the release manager can prepare an improved release. Publishing means that the release artifacts are moved to the official distribution area where they are picked up by the mirror system.
So, cutting a release == creating a release == preparing a release
but these != publishing a release.
Craig
> On May 17, 2021, at 8:10 AM, Zhang Yonglun <zh...@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.
>
>> 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
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org