You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by "Moorhead,Richard" <Ri...@cerner.com> on 2019/05/08 13:10:30 UTC
request for beam minor release
Is there a process for tagging a commit in master for a minor release?
I am trying to get this<https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb> commit released into 2.10.1
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: request for beam minor release
Posted by Maximilian Michels <mx...@apache.org>.
> Assuming 2.13 will include or otherwise be supported by flink-runner-1.7 then this should not be an issue.
Yes, we will keep supporting Flink 1.7 for Beam 2.13.
-Max
On 08.05.19 19:54, Kenneth Knowles wrote:
> For the benefit of the thread, I will also call out our incubating LTS
> (Long-Term Support) policy. For critical fixes, we will issue patch
> releases on the 2.7 branch. We are currently gathering proposals for
> cherry-picks to 2.7.1 to do that release. Other than that, releases are
> a lot of work so we focus on a steady rate of minor version releases
> instead of patching non-LTS versions.
>
> You can read at https://beam.apache.org/community/policies/.
>
> Kenn
>
> On Wed, May 8, 2019 at 9:22 AM Moorhead,Richard
> <Richard.Moorhead2@cerner.com <ma...@cerner.com>> wrote:
>
> Assuming 2.13 will include or otherwise be supported by
> flink-runner-1.7 then this should not be an issue.
>
> ------------------------------------------------------------------------
> *From:* Jean-Baptiste Onofré <jb@nanthrax.net <ma...@nanthrax.net>>
> *Sent:* Wednesday, May 8, 2019 10:09 AM
> *To:* dev@beam.apache.org <ma...@beam.apache.org>
> *Subject:* Re: request for beam minor release
> I second Max here. If you are just looking for this specific commit, you
> can take a next release that will include it.
>
> Regards
> JB
>
> On 08/05/2019 16:27, Maximilian Michels wrote:
> > Hi Richard,
> >
> > Would it be an option to use the upcoming 2.13.0 release? The commit
> > will be part of that release.
> >
> > Thanks,
> > Max
> >
> > On 08.05.19 15:43, Jean-Baptiste Onofré wrote:
> >> Hi,
> >>
> >> Any release are tagging. We create a branch based on a master commit.
> >>
> >> Are you requesting 2.10.1 maintenance release ?
> >>
> >> Regards
> >> JB
> >>
> >> On 08/05/2019 15:10, Moorhead,Richard wrote:
> >>> Is there a process for tagging a commit in master for a minor release?
> >>>
> >>> I am trying to get this
> >>> <https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb> commit
> >>>
> >>> released into 2.10.1
> >>>
> >>> CONFIDENTIALITY NOTICE This message and any included attachments are
> >>> from Cerner Corporation and are intended only for the addressee. The
> >>> information contained in this message is confidential and may constitute
> >>> inside or non-public information under international, federal, or state
> >>> securities laws. Unauthorized forwarding, printing, copying,
> >>> distribution, or use of such information is strictly prohibited and may
> >>> be unlawful. If you are not the addressee, please promptly delete this
> >>> message and notify the sender of the delivery error by e-mail or you may
> >>> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
> >>> (816)221-1024.
> >>>
> >>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> CONFIDENTIALITY NOTICE This message and any included attachments are
> from Cerner Corporation and are intended only for the addressee. The
> information contained in this message is confidential and may
> constitute inside or non-public information under international,
> federal, or state securities laws. Unauthorized forwarding,
> printing, copying, distribution, or use of such information is
> strictly prohibited and may be unlawful. If you are not the
> addressee, please promptly delete this message and notify the sender
> of the delivery error by e-mail or you may call Cerner's corporate
> offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>
Re: request for beam minor release
Posted by Kenneth Knowles <ke...@apache.org>.
For the benefit of the thread, I will also call out our incubating LTS
(Long-Term Support) policy. For critical fixes, we will issue patch
releases on the 2.7 branch. We are currently gathering proposals for
cherry-picks to 2.7.1 to do that release. Other than that, releases are a
lot of work so we focus on a steady rate of minor version releases instead
of patching non-LTS versions.
You can read at https://beam.apache.org/community/policies/.
Kenn
On Wed, May 8, 2019 at 9:22 AM Moorhead,Richard <
Richard.Moorhead2@cerner.com> wrote:
> Assuming 2.13 will include or otherwise be supported by flink-runner-1.7
> then this should not be an issue.
>
> ------------------------------
> *From:* Jean-Baptiste Onofré <jb...@nanthrax.net>
> *Sent:* Wednesday, May 8, 2019 10:09 AM
> *To:* dev@beam.apache.org
> *Subject:* Re: request for beam minor release
>
> I second Max here. If you are just looking for this specific commit, you
> can take a next release that will include it.
>
> Regards
> JB
>
> On 08/05/2019 16:27, Maximilian Michels wrote:
> > Hi Richard,
> >
> > Would it be an option to use the upcoming 2.13.0 release? The commit
> > will be part of that release.
> >
> > Thanks,
> > Max
> >
> > On 08.05.19 15:43, Jean-Baptiste Onofré wrote:
> >> Hi,
> >>
> >> Any release are tagging. We create a branch based on a master commit.
> >>
> >> Are you requesting 2.10.1 maintenance release ?
> >>
> >> Regards
> >> JB
> >>
> >> On 08/05/2019 15:10, Moorhead,Richard wrote:
> >>> Is there a process for tagging a commit in master for a minor release?
> >>>
> >>> I am trying to get this
> >>> <
> https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb
> > commit
> >>>
> >>> released into 2.10.1
> >>>
> >>> CONFIDENTIALITY NOTICE This message and any included attachments are
> >>> from Cerner Corporation and are intended only for the addressee. The
> >>> information contained in this message is confidential and may
> constitute
> >>> inside or non-public information under international, federal, or state
> >>> securities laws. Unauthorized forwarding, printing, copying,
> >>> distribution, or use of such information is strictly prohibited and may
> >>> be unlawful. If you are not the addressee, please promptly delete this
> >>> message and notify the sender of the delivery error by e-mail or you
> may
> >>> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
> >>> (816)221-1024.
> >>>
> >>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
> CONFIDENTIALITY NOTICE This message and any included attachments are from
> Cerner Corporation and are intended only for the addressee. The information
> contained in this message is confidential and may constitute inside or
> non-public information under international, federal, or state securities
> laws. Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you are not
> the addressee, please promptly delete this message and notify the sender of
> the delivery error by e-mail or you may call Cerner's corporate offices in
> Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>
Re: request for beam minor release
Posted by "Moorhead,Richard" <Ri...@cerner.com>.
Assuming 2.13 will include or otherwise be supported by flink-runner-1.7 then this should not be an issue.
________________________________
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Wednesday, May 8, 2019 10:09 AM
To: dev@beam.apache.org
Subject: Re: request for beam minor release
I second Max here. If you are just looking for this specific commit, you
can take a next release that will include it.
Regards
JB
On 08/05/2019 16:27, Maximilian Michels wrote:
> Hi Richard,
>
> Would it be an option to use the upcoming 2.13.0 release? The commit
> will be part of that release.
>
> Thanks,
> Max
>
> On 08.05.19 15:43, Jean-Baptiste Onofré wrote:
>> Hi,
>>
>> Any release are tagging. We create a branch based on a master commit.
>>
>> Are you requesting 2.10.1 maintenance release ?
>>
>> Regards
>> JB
>>
>> On 08/05/2019 15:10, Moorhead,Richard wrote:
>>> Is there a process for tagging a commit in master for a minor release?
>>>
>>> I am trying to get this
>>> <https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb> commit
>>>
>>> released into 2.10.1
>>>
>>> CONFIDENTIALITY NOTICE This message and any included attachments are
>>> from Cerner Corporation and are intended only for the addressee. The
>>> information contained in this message is confidential and may constitute
>>> inside or non-public information under international, federal, or state
>>> securities laws. Unauthorized forwarding, printing, copying,
>>> distribution, or use of such information is strictly prohibited and may
>>> be unlawful. If you are not the addressee, please promptly delete this
>>> message and notify the sender of the delivery error by e-mail or you may
>>> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
>>> (816)221-1024.
>>>
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: request for beam minor release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I second Max here. If you are just looking for this specific commit, you
can take a next release that will include it.
Regards
JB
On 08/05/2019 16:27, Maximilian Michels wrote:
> Hi Richard,
>
> Would it be an option to use the upcoming 2.13.0 release? The commit
> will be part of that release.
>
> Thanks,
> Max
>
> On 08.05.19 15:43, Jean-Baptiste Onofré wrote:
>> Hi,
>>
>> Any release are tagging. We create a branch based on a master commit.
>>
>> Are you requesting 2.10.1 maintenance release ?
>>
>> Regards
>> JB
>>
>> On 08/05/2019 15:10, Moorhead,Richard wrote:
>>> Is there a process for tagging a commit in master for a minor release?
>>>
>>> I am trying to get this
>>> <https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb> commit
>>>
>>> released into 2.10.1
>>>
>>> CONFIDENTIALITY NOTICE This message and any included attachments are
>>> from Cerner Corporation and are intended only for the addressee. The
>>> information contained in this message is confidential and may constitute
>>> inside or non-public information under international, federal, or state
>>> securities laws. Unauthorized forwarding, printing, copying,
>>> distribution, or use of such information is strictly prohibited and may
>>> be unlawful. If you are not the addressee, please promptly delete this
>>> message and notify the sender of the delivery error by e-mail or you may
>>> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
>>> (816)221-1024.
>>>
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: request for beam minor release
Posted by Maximilian Michels <mx...@apache.org>.
Hi Richard,
Would it be an option to use the upcoming 2.13.0 release? The commit
will be part of that release.
Thanks,
Max
On 08.05.19 15:43, Jean-Baptiste Onofré wrote:
> Hi,
>
> Any release are tagging. We create a branch based on a master commit.
>
> Are you requesting 2.10.1 maintenance release ?
>
> Regards
> JB
>
> On 08/05/2019 15:10, Moorhead,Richard wrote:
>> Is there a process for tagging a commit in master for a minor release?
>>
>> I am trying to get this
>> <https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb> commit
>> released into 2.10.1
>>
>>
>> CONFIDENTIALITY NOTICE This message and any included attachments are
>> from Cerner Corporation and are intended only for the addressee. The
>> information contained in this message is confidential and may constitute
>> inside or non-public information under international, federal, or state
>> securities laws. Unauthorized forwarding, printing, copying,
>> distribution, or use of such information is strictly prohibited and may
>> be unlawful. If you are not the addressee, please promptly delete this
>> message and notify the sender of the delivery error by e-mail or you may
>> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
>> (816)221-1024.
>>
>
Re: request for beam minor release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
Any release are tagging. We create a branch based on a master commit.
Are you requesting 2.10.1 maintenance release ?
Regards
JB
On 08/05/2019 15:10, Moorhead,Richard wrote:
> Is there a process for tagging a commit in master for a minor release?
>
> I am trying to get this
> <https://github.com/apache/beam/pull/8503/commits/ffa5632bca8c7264993702c39c6ca013a9f6ecdb> commit
> released into 2.10.1
>
>
> CONFIDENTIALITY NOTICE This message and any included attachments are
> from Cerner Corporation and are intended only for the addressee. The
> information contained in this message is confidential and may constitute
> inside or non-public information under international, federal, or state
> securities laws. Unauthorized forwarding, printing, copying,
> distribution, or use of such information is strictly prohibited and may
> be unlawful. If you are not the addressee, please promptly delete this
> message and notify the sender of the delivery error by e-mail or you may
> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
> (816)221-1024.
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com