You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Udi Meiri <eh...@google.com> on 2020/06/01 19:06:41 UTC
latest release on Github
Hi,
Trying out the new Github layout (feature preview) I've noticed that the
latest release is featured more prominently and is at v2.16.0 for some
reason. https://github.com/apache/beam/releases/tag/v2.16.0
Any idea how to fix this, and what instructions should be added to the
release guide?
Re: latest release on Github
Posted by Udi Meiri <eh...@google.com>.
Thanks Nathan and Kyle!
On Mon, Jun 1, 2020 at 12:22 PM Kyle Weaver <kc...@google.com> wrote:
> Filed https://jira.apache.org/jira/browse/BEAM-10168
>
> On Mon, Jun 1, 2020 at 3:20 PM Kyle Weaver <kc...@google.com> wrote:
>
>> I fixed it. There was a discussion on the mailing list recently about
>> automating Github releases [1], short of that however we can just use the
>> UI.
>>
>> [1]
>> https://lists.apache.org/thread.html/re367d262333078501c47856e9b8a0fc3fd7db60c2d2ebb181275481a%40%3Cdev.beam.apache.org%3E
>>
>>
>> On Mon, Jun 1, 2020 at 3:07 PM Udi Meiri <eh...@google.com> wrote:
>>
>>> Hi,
>>> Trying out the new Github layout (feature preview) I've noticed that the
>>> latest release is featured more prominently and is at v2.16.0 for some
>>> reason. https://github.com/apache/beam/releases/tag/v2.16.0
>>>
>>> Any idea how to fix this, and what instructions should be added to the
>>> release guide?
>>>
>>
Re: latest release on Github
Posted by Kyle Weaver <kc...@google.com>.
Filed https://jira.apache.org/jira/browse/BEAM-10168
On Mon, Jun 1, 2020 at 3:20 PM Kyle Weaver <kc...@google.com> wrote:
> I fixed it. There was a discussion on the mailing list recently about
> automating Github releases [1], short of that however we can just use the
> UI.
>
> [1]
> https://lists.apache.org/thread.html/re367d262333078501c47856e9b8a0fc3fd7db60c2d2ebb181275481a%40%3Cdev.beam.apache.org%3E
>
>
> On Mon, Jun 1, 2020 at 3:07 PM Udi Meiri <eh...@google.com> wrote:
>
>> Hi,
>> Trying out the new Github layout (feature preview) I've noticed that the
>> latest release is featured more prominently and is at v2.16.0 for some
>> reason. https://github.com/apache/beam/releases/tag/v2.16.0
>>
>> Any idea how to fix this, and what instructions should be added to the
>> release guide?
>>
>
Re: latest release on Github
Posted by Kyle Weaver <kc...@google.com>.
I fixed it. There was a discussion on the mailing list recently about
automating Github releases [1], short of that however we can just use the
UI.
[1]
https://lists.apache.org/thread.html/re367d262333078501c47856e9b8a0fc3fd7db60c2d2ebb181275481a%40%3Cdev.beam.apache.org%3E
On Mon, Jun 1, 2020 at 3:07 PM Udi Meiri <eh...@google.com> wrote:
> Hi,
> Trying out the new Github layout (feature preview) I've noticed that the
> latest release is featured more prominently and is at v2.16.0 for some
> reason. https://github.com/apache/beam/releases/tag/v2.16.0
>
> Any idea how to fix this, and what instructions should be added to the
> release guide?
>
Re: latest release on Github
Posted by Nathan Fisher <nf...@junctionbox.ca>.
Hi Udi,
Tags were pushed which basically creates a placeholder for a release. In
order to make a tag an official release someone with admin rights needs to
edit the tag via the UI (or API) and publish additional information about
the release. Common to attach release notes and relevant files. An example
release edit is below:
[image: image.png]
On Mon, Jun 1, 2020 at 16:07, Udi Meiri <eh...@google.com> wrote:
> Hi,
> Trying out the new Github layout (feature preview) I've noticed that the
> latest release is featured more prominently and is at v2.16.0 for some
> reason. https://github.com/apache/beam/releases/tag/v2.16.0
>
> Any idea how to fix this, and what instructions should be added to the
> release guide?
>