Sounds good, thanks J.B. Feel free to ping if you need anything.

On Mon, Apr 30, 2018 at 10:12 PM Jean-Baptiste Onofré <jb@nanthrax.net> wrote:
That's a good idea ! I think using Slack to ping/ask is a good way as it's async.

Regards
JB

On 05/01/2018 06:51 AM, Reuven Lax wrote:
> I think it makes sense to have someone who hadn't done the Gradle migration to
> run the release. However would it make sense for someone who did work on the
> migration to partner with you JB? There may be issues that are simply due to
> things that were not documented well. In that case the partner can quickly help
> resolve, and can then be the one who makes sure that the documentation is updated.
>
> Reuven
>
> On Mon, Apr 30, 2018 at 9:36 PM Jean-Baptiste Onofré <jb@nanthrax.net
> <mailto:jb@nanthrax.net>> wrote:
>
>     Hi Scott,
>
>     Thanks for the update. The Gradle build crashed on my machine (not related to
>     Gradle). I launched a new one.
>
>     I'm volunteer to cut the release: I think I know Gradle decently, and even if I
>     didn't work on the gradle "migration" during the last two weeks, I think it's
>     actually better: I have an "external" view on the latest changes.
>
>     Thoughts ?
>
>     Regards
>     JB
>
>     On 05/01/2018 02:05 AM, Scott Wegner wrote:
>     > Welcome back JB!
>     >
>     > I just sent a separate update about Gradle [1]-- the build migration is
>     complete
>     > and the release documentation has been updated.
>     >
>     > I recommend we produce the 2.5.0 release using Gradle. Having a successful
>     > release should be the final validation before declaring the Gradle migration
>     > complete. So the sooner we can have a Gradle release, the sooner we can
>     get back
>     > to a single build system :)
>     >
>     > If it would be helpful, I suggest that somebody who's been working on the
>     Gradle
>     > migration to manage the 2.5.0 release. That way if we encounter any issues
>     from
>     > the build system, they should have sufficient expertise to fix it.
>     >
>     >
>     [1] https://lists.apache.org/thread.html/e543b3850bfc4950d57bc18624e1d4131324c6cf691fd10034947cad@%3Cdev.beam.apache.org%3E 
>     >
>     > On Mon, Apr 30, 2018 at 11:38 AM Romain Manni-Bucau <rmannibucau@gmail.com
>     <mailto:rmannibucau@gmail.com>
>     > <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>> wrote:
>     >
>     >
>     >
>     >     Le 30 avr. 2018 19:39, "Jean-Baptiste Onofré" <jb@nanthrax.net
>     <mailto:jb@nanthrax.net>
>     >     <mailto:jb@nanthrax.net <mailto:jb@nanthrax.net>>> a écrit :
>     >
>     >         Hi guys,
>     >
>     >         now that I'm back from vacations, I bring back 2.5.0 release on
>     the table ;)
>     >
>     >         This is also related to the current status of build (Maven/Gradle).
>     >
>     >         FYI, I gonna start the Jira triage tomorrow and I launched couple of
>     >         build on my
>     >         machine (both Maven and Gradle) to get an update on the current
>     status.
>     >
>     >         Please, let me know if you have an opinion about Gradle vs Maven
>     for the
>     >         release.
>     >
>     >
>     >     Produced artifacts are still too different to use gradle IMHO. Jira were
>     >     created but not yet fixed last time i tried gradle so clearly maven IMHO.
>     >
>     >
>     >         Thanks !
>     >         Regards
>     >         JB
>     >
>     >         On 04/06/2018 10:48 AM, 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 ?
>     >         >
>     >         > Regards
>     >         > JB
>     >         >
>     >
>     >         --
>     >         Jean-Baptiste Onofré
>     >         jbonofre@apache.org <mailto:jbonofre@apache.org>
>     <mailto:jbonofre@apache.org <mailto:jbonofre@apache.org>>
>     >         http://blog.nanthrax.net
>     >         Talend - http://www.talend.com
>     >
>     >
>     > --
>     >
>     >
>     > Got feedback? http://go/swegner-feedback
>
>     --
>     Jean-Baptiste Onofré
>     jbonofre@apache.org <mailto:jbonofre@apache.org>
>     http://blog.nanthrax.net
>     Talend - http://www.talend.com
>

--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--


Got feedback? http://go/swegner-feedback