I don’t think it’s useful to have release manager instructions on the page for new contributors. I’m curious why you think so?
Steve > On Mar 17, 2015, at 6:34 PM, Alexandre Rafalovitch <[email protected]> wrote: > > Thank you Steve and Shawn. > > For my purposes, "ant -Dversion=X.Y.Z prepare-release" was a bit of an > overkill it seems, as it was trying to copy files around as well. So, > I just used "ant -Dversion=5.0.0 package" and it worked as I wanted. > > Interestingly, there does not seem to be a link to the mentioned > release document from the http://wiki.apache.org/solr/HowToContribute > , which is where I went looking for the information. Should there be? > > Regards, > Alex. > ---- > Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: > http://www.solr-start.com/ > > > On 17 March 2015 at 21:09, Shawn Heisey <[email protected]> wrote: >> On 3/17/2015 6:17 PM, Alexandre Rafalovitch wrote: >>> A tiny question, but I want to get it right. Right now I build the >>> jars from source and all the Lucene/Solr jars are generated with >>> -SNAPSHOT suffix. >>> >>> What do I need to do to generate artifacts exactly like a release manager >>> would. >>> >>> I can see lucene/version.properties, but it says NOT to change the >>> version.suffix/version/spec.version variables. So, what do I change >>> then? >> >> It looks like you can use Option 2 on the instructions found here: >> >> https://wiki.apache.org/lucene-java/ReleaseTodo#Building_the_Release_artifacts >> >> I am trying this now on branch_5x to see how it turns out. The >> "prepare-release" target does not work in the top directory of the >> checkout, you must descend to lucene or solr to use it. This is the >> command that I'm running: >> >> ant -Dversion=5.1.0 prepare-release >> >> When I tried it the first time, I went into the solr directory, and it >> failed. After that, taking my cue from the nature of the error message, >> I cleaned the source tree and then tried prepare-release first in the >> lucene directory, then the solr directory. That worked. >> >> The lucene artifacts end up in the lucene/dist directory, and the solr >> artifacts end up in solr/package. >> >> It did ask me for a passphrase on my GPG key, but the value I typed was >> wrong ... it still succeeded. >> >> Thanks, >> Shawn >> >> >> --------------------------------------------------------------------- >> 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]
