I'm still trying to figure the problem out. I think there's a conflict between an explicit dependency and an implicit one.
On Tue, Oct 24, 2017 at 1:29 PM, Reuven Lax <re...@google.com> wrote: > Update: there is a dependency error in the release branch, so am fixing > that and retrying. > > On Tue, Oct 24, 2017 at 12:43 PM, Reuven Lax <re...@google.com> wrote: > >> We've been blocked for a couple of weeks on BEAM-3011, however that is >> now in and I just merged the PR into the release branch. We've been having >> a lot of problems with the Jenkins test infrastructure for Beam the last >> few weeks, which is why it took so long to merge. >> >> I am now manually verifying that everything passes on the release branch. >> Once verification completes, I will cut an RC1. >> >> Reuven >> >> On Mon, Oct 23, 2017 at 9:33 PM, Jean-Baptiste Onofré <j...@nanthrax.net> >> wrote: >> >>> Hi guys, >>> >>> can we move forward on 2.2.0 release ? >>> >>> Only two Jira are still open for 2.2.0: >>> >>> BEAM-3011 - Pin Runner harness container image in Python SDK >>> BEAM-2271 - Release guide or pom.xml needs update to avoid releasing >>> Python binary artifacts >>> >>> Both are related to Python SDK. >>> Can we have an update about this ? >>> Are they blocker for the 2.2.0 release ? >>> >>> @Reuven: I think we are good to do a 2.2.0.RC1. Thoughts ? >>> >>> Thanks ! >>> Regards >>> JB >>> >>> On 10/10/2017 12:53 AM, Reuven Lax wrote: >>> >>>> I've now cut a release branch for 2.2.0. >>>> >>>> On Mon, Oct 9, 2017 at 2:01 AM, Jean-Baptiste Onofré <j...@nanthrax.net> >>>> wrote: >>>> >>>> It sounds good to me. >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> >>>>> On 10/09/2017 12:38 AM, Reuven Lax wrote: >>>>> >>>>> At this point it's taken over three weeks to resolve release-blocking >>>>>> issues, and there are still some remaining. Monday morning I will go >>>>>> ahead >>>>>> and cut an initial release candidate, so we get a snapshot to base >>>>>> on. The >>>>>> remaining blocking issues will either be cherry picked into an >>>>>> additional >>>>>> release candidate or punted to 2.3.0, depending on severity. >>>>>> >>>>>> Reuven >>>>>> >>>>>> On Wed, Sep 20, 2017 at 5:34 AM, Jean-Baptiste Onofré < >>>>>> j...@nanthrax.net> >>>>>> wrote: >>>>>> >>>>>> Hi Reuven, >>>>>> >>>>>>> >>>>>>> thanks for the update. I will pick up some Jira in my bucket (to >>>>>>> verify/double check or implement). >>>>>>> >>>>>>> Regards >>>>>>> JB >>>>>>> >>>>>>> >>>>>>> On 09/20/2017 04:23 AM, Reuven Lax wrote: >>>>>>> >>>>>>> There are 7 issues left on >>>>>>> >>>>>>>> https://issues.apache.org/jira/projects/BEAM/versions/12341044 >>>>>>>> after I >>>>>>>> moved some items to 2.3.0 if they appeared to not need to be in >>>>>>>> 2.2.0 >>>>>>>> (some >>>>>>>> were originally slated for 2.1.0, and there was no apparent >>>>>>>> progress on >>>>>>>> them). Please object if you feel that it's important that any of >>>>>>>> these >>>>>>>> be >>>>>>>> in 2.2.0 >>>>>>>> >>>>>>>> Of the remaining issues, three (BEAM-2956, BEAM-2298, BEAM-2271) >>>>>>>> appear >>>>>>>> to >>>>>>>> already be fixed; please verify this and close the issue if you are >>>>>>>> the >>>>>>>> reporter. The remaining issues (BEAM-2834, BEAM-2858, BEAM-2870, >>>>>>>> BEAM-29540) all have outstanding pull requests. As soon as all of >>>>>>>> these >>>>>>>> pull requests are merged, I will start the release cut. >>>>>>>> >>>>>>>> Reuven >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>> Jean-Baptiste Onofré >>>>>>> jbono...@apache.org >>>>>>> http://blog.nanthrax.net >>>>>>> Talend - http://www.talend.com >>>>>>> >>>>>>> >>>>>>> >>>>>> -- >>>>> Jean-Baptiste Onofré >>>>> jbono...@apache.org >>>>> http://blog.nanthrax.net >>>>> Talend - http://www.talend.com >>>>> >>>>> >>>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >> >> >
