In case you didn't see the other thread, Andrew just discovered a problem
in SQL's jar build. It may be a release blocker.
Just an FYI. Since the fix is likely small fixes to build file it seems ok
to cut the branch and cherry pick.
On Thu, May 17, 2018, 17:41 Ahmet Altay <al...@google.com> wrote:
> Hi JB and all,
> I wanted to follow up on my previous email. The python streaming issue I
> mentioned is resolved and removed from the blocker list. Blocker list is
> empty now. You can go ahead with the release branch cut when you are ready.
> Thank you,
> On Sun, May 13, 2018 at 8:43 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
>> Hi guys,
>> just to let you know that the build fully passed on my box.
>> I'm testing the artifacts right now.
>> On 06/04/2018 10:48, Jean-Baptiste Onofré wrote:
>>> Hi guys,
>>> Apache Beam 2.4.0 has been released on March 20th.
>>> According to our cycle of release (roughly 6 weeks), we should think
>>> about 2.5.0.
>>> I'm volunteer to tackle this release.
>>> I'm proposing the following items:
>>> 1. We start the Jira triage now, up to Tuesday
>>> 2. I would like to cut the release on Tuesday night (Europe time)
>>> 2bis. I think it's wiser to still use Maven for this release. Do you
>>> think we
>>> will be ready to try a release with Gradle ?
>>> After this release, I would like a discussion about:
>>> 1. Gradle release (if we release 2.5.0 with Maven)
>>> 2. Isolate release cycle per Beam part. I think it would be interesting
>>> to have
>>> different release cycle: SDKs, DSLs, Runners, IOs. That's another
>>> discussion, I
>>> will start a thread about that.
>>> Thoughts ?