keep in mind there may not be one in the URL. Its nice to smoke-test before uploading to your home directory. also its useful to run 'ant nightly-smoke' and run a smoke test, and if someone commits something while this is happening, its no problem. jenkins does this automatically too.
so can we have not a failure but a warning, like: ***WARNING***: not the latest SVN version On Fri, Apr 19, 2013 at 6:16 PM, Uwe Schindler <u...@thetaphi.de> wrote: > I think, maybe Smoketester should compare the revision from the URL in the > RC vote with the one recorded in the JAR files? Everything else makes no > sense as the: > a) The SVN server always replies with the latest committed version on the > whole repository not the one of the newest file in the branch. > b) We can have changes in the RC branch after RC started > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > > -----Original Message----- > > From: Michael McCandless [mailto:luc...@mikemccandless.com] > > Sent: Saturday, April 20, 2013 12:12 AM > > To: dev@lucene.apache.org; simon.willna...@gmail.com > > Cc: Uwe Schindler > > Subject: Re: [VOTE] Lucene/Solr 4.3 RC1 > > > > On Fri, Apr 19, 2013 at 6:07 PM, Simon Willnauer > > <simon.willna...@gmail.com> wrote: > > > Hmm @hoss did you check this manually, I mean the revision? > > > > > > I think our smoketester should check the revision of the release > > > branch and the revision of the RC to make sure this doesn't happen? > > > > SmokeTester might be too anal? Like sometimes we backport stuff to the > > release branch just in case another RC is cut ... > > > > But I think buildAndPushRelease is a good place to do it? > > > > Mike McCandless > > > > http://blog.mikemccandless.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
