Hi Michael - this sounds similar to what I ran into last time I did a
release, is it this?
https://issues.apache.org/jira/browse/INFRA-16540

Patrick

On Mon, Jul 16, 2018 at 6:40 PM Michael Han <h...@apache.org> wrote:

> The release artifacts are published, but for an infrastructure issue [1],
> the zookeeper web site is not updated.
>
> I'll send out release announcement email once the infra issue is resolved.
>
> [1] https://issues.apache.org/jira/browse/INFRA-16777
>
> On Mon, Jul 16, 2018 at 9:00 AM, Michael Han <h...@apache.org> wrote:
>
> > With 3 binding +1, two non-binding +1, this vote passes.
> >
> > I will finish publishing the release tonight. Thanks everyone for helping
> > on the release.
> >
> > On Wed, Jul 11, 2018 at 7:54 PM, Michael Han <h...@apache.org> wrote:
> >
> >> Thanks Pat for confirmation.
> >>
> >> I'll leave the rest of the week for folks to try the release candidate
> >> and provide feedback. As Pat mentioned, helping voting a release is a
> great
> >> way to make contributions to ZooKeeper, so any help will be very
> welcome!
> >>
> >> I'll start publish the new release early next week if no blocking issue
> >> is reported.
> >>
> >>
> >> On Wed, Jul 11, 2018 at 7:44 PM, Patrick Hunt <ph...@apache.org> wrote:
> >>
> >>> Your vote counts - 3 +1 from PMC is all we need. Would be great to see
> >>> some
> >>> of the other folks vote though.
> >>>
> >>> Patrick
> >>>
> >>> On Wed, Jul 11, 2018 at 6:54 PM Michael Han <h...@apache.org> wrote:
> >>>
> >>> > Thanks Pat!
> >>> >
> >>> > Just double check, a release requires at least three binding (PMC)
> >>> votes,
> >>> > right? I guess my own vote (as the release manager) does not count,
> so
> >>> we
> >>> > need one more vote from a PMC member before we can release this
> >>> (currently
> >>> > two bindings are from you and Rakesh).
> >>> >
> >>> > On Wed, Jul 11, 2018 at 10:39 AM, Patrick Hunt <ph...@apache.org>
> >>> wrote:
> >>> >
> >>> > > +1. the xsum/sig are good. rat seemed fine. ran through a number of
> >>> > cluster
> >>> > > scenarios and it seemed to work fine.
> >>> > >
> >>> > > I notice that the dynamic IP change is in - I'd recommend folks
> that
> >>> have
> >>> > > been advocating for that change to give the RC a try and verify
> that
> >>> it's
> >>> > > working for them. Great way to pay back the community!
> >>> > >
> >>> > > Regards,
> >>> > >
> >>> > > Patrick
> >>> > >
> >>> > > On Sat, Jun 30, 2018 at 5:17 PM Michael Han <h...@apache.org>
> wrote:
> >>> > >
> >>> > > > This is a bugfix release candidate for 3.4.13. It fixes 17
> issues,
> >>> > > > including issues such as ZOOKEEPER-2959
> >>> > > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2959> that
> could
> >>> > cause
> >>> > > > data loss when observer is used, and ZOOKEEPER-2184
> >>> > > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2184> that
> >>> prevents
> >>> > > > ZooKeeper Java clients working in dynamic IP (container / cloud)
> >>> > > > environment.
> >>> > > >
> >>> > > > The full release notes is available at:
> >>> > > >
> >>> > > > *
> >>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> > > projectId=12310801&version=12342973
> >>> > > > <
> >>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> > > projectId=12310801&version=12342973
> >>> > > > >*
> >>> > > >
> >>> > > > *** Please download, test and vote by July 7th 2018, 23:59 UTC+0.
> >>> ***
> >>> > > >
> >>> > > > Source files:
> >>> > > > *http://people.apache.org/~hanm/zookeeper/zookeeper-3.4.13-rc1/
> >>> > > > <http://people.apache.org/~hanm/zookeeper/zookeeper-3.4.13-rc1/
> >*
> >>> > > >
> >>> > > > Maven staging repo:
> >>> > > > https://repository.apache.org/content/groups/staging/org/
> >>> > > > apache/zookeeper/zookeeper/3.4.13/
> >>> > > >
> >>> > > > The release candidate tag in git to be voted upon:
> >>> release-3.4.13-rc1
> >>> > > >
> >>> > > > ZooKeeper's KEYS file containing PGP keys we use to sign the
> >>> release:
> >>> > > > http://www.apache.org/dist/zookeeper/KEYS
> >>> > > >
> >>> > > > Should we release this candidate?
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>

Reply via email to