For 5.1 you should be able to just follow the post-release steps on
the release TODO? Ryan simplified this a while back...
Mike McCandless
http://blog.mikemccandless.com
On Tue, Apr 14, 2015 at 11:11 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: This fail seems like I might have
What post release step are you referring to?
http://wiki.apache.org/lucene-java/ReleaseTodo#Post-release I did the
JIRA stuff ... wasn't sure if I should delete the 5.0 artifacts, but
that doesn't seem related a build failure?
On Wed, Apr 15, 2015 at 8:20 AM, Michael McCandless
On Wed, Apr 15, 2015 at 12:04 PM, Timothy Potter thelabd...@gmail.com wrote:
What post release step are you referring to?
Urgh, you're right ... I thought the steps were listed but they are not.
OK indeed this was split out from addVersion.py to a new
addBackCompatIndices.py ... so the
This fail seems like I might have missed something doing the 5.1
release ... any thoughts?
-- Forwarded message --
From: Apache Jenkins Server jenk...@builds.apache.org
Date: Tue, Apr 14, 2015 at 8:08 PM
Subject: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 253 - Failure
To:
: This fail seems like I might have missed something doing the 5.1
: release ... any thoughts?
I think it's a post release step? once the release is final, someone needs
to manually generate test indexes (using the released version of the code)
and then commit those on trunk backport to the
