+1 SUCCESS! [1:09:40.299603]

Le dim. 14 févr. 2016 à 14:45, Michael McCandless <[email protected]>
a écrit :

> Thanks Uwe, you're right.  I'll move them up now, in case we re-spin...
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sun, Feb 14, 2016 at 8:38 AM, Uwe Schindler <[email protected]> wrote:
> > Hi,
> >
> > I just noticed that the CHANGES.txt of Lucene contains a 5.4.2 section,
> which was just started but never released. I think the changes there should
> be moved forward to 5.5.0. That’s not a blocker, but if we need to respin,
> we should fix this!
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [email protected]
> >
> >> -----Original Message-----
> >> From: Michael McCandless [mailto:[email protected]]
> >> Sent: Sunday, February 14, 2016 1:41 PM
> >> To: Lucene/Solr dev <[email protected]>
> >> Subject: [VOTE] Release Lucene/Solr 5.5.0 RC2
> >>
> >> Please vote for the RC2 release candidate for Lucene/Solr 5.5.0, the
> >> last feature release before Lucene 6.0.0 and the first Lucene/Solr
> >> release since we switched from Subversion to git!
> >>
> >> Artifacts:
> >>
> >>   https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.5.0-RC2-
> >> rev528fb8702b91aaeb7a0491a638ed10ae8ae57f2c
> >>
> >> Smoke tester:
> >>
> >>   python3 -u dev-tools/scripts/smokeTestRelease.py
> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.5.0-RC2-
> >> rev528fb8702b91aaeb7a0491a638ed10ae8ae57f2c
> >>
> >> I'm +1 based on my smoke tester run:
> >>
> >>   SUCCESS! [0:32:38.720729]
> >>
> >> And I also previously ran all our 2B monster tests successfully with 40
> GB
> >> heap.
> >>
> >> Please remember a release is not the time to shove last minute changes
> >> in.  Instead, shove those changes in immediately after the release so
> >> CI has plenty of time to chew on them.
> >>
> >> Mike McCandless
> >>
> >> http://blog.mikemccandless.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to