Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Steve Rowe
> On Jan 22, 2016, at 2:28 PM, Dawid Weiss wrote: > > 1) I'd notify infra because this permits any committer to destroy the > log history without a trace ;) For Lucene anyway (and I suspect most/all ASF projects?), there is an (out-of-band) trace: the archive of log

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Steve Rowe
On Jan 22, 2016, at 2:41 PM, Dawid Weiss wrote: > >> Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties >> (of which svn:log is one) cause the property's previous value to be >> permanently discarded” > > Hmm... They're not versioned in the SVN

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Anshum Gupta
Does anyone here know how to edit a log message after committing? I accidentally typed in lucene instead of solr for one of the release related commits. On Fri, Jan 22, 2016 at 11:03 AM, Anshum Gupta wrote: > Hi Adrien, > > I'm in the middle of publishing the artifacts.

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Dawid Weiss
I'm sorry, I wasn't precise enough -- have you tried it on the Apache SVN? Quote: "The first way is for the repository administrator to enable revision property modifications." I admit I didn't check, but I'd be surprised if these were allowed as this permits historical changes to the content of

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Anshum Gupta
Adrien, Seems like I'd have to wait until the release is on a decent number of Apache mirrors. Running addBackcompatIndexes.py for 5.3.2 leads to the following error: Could not find version 5.3.2 in apache mirror or archives Is there a work around for this? On Fri, Jan 22, 2016 at 7:58 AM,

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Dawid Weiss
> Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties > (of which svn:log is one) cause the property's previous value to be > permanently discarded” Hmm... They're not versioned in the SVN dumps I looked at? In any case, I wouldn't do it, Anshum -- if it's a typo, it's

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Anshum Gupta
Thanks Steve, but seems like that required 'admin' permissions. Not sure if I/we have it. Dawid: Thanks. I've used stuff from that point on so I don't think I'll be able to revert it. In any case, The commit message is about copying rc to the release repo and has 'lucene' instead of 'solr'. I

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Steve Rowe
Again, not true :) In modern versions of Subversion, properties are also versioned. So, no history destruction to see here. -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:28 PM, Dawid Weiss wrote: > > Interesting! If it does work then: > > 1) I'd notify infra

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Steve Rowe
Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties (of which svn:log is one) cause the property's previous value to be permanently discarded” Digging… -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:30 PM, Steve Rowe wrote: > > Again, not true

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Dawid Weiss
No way to do it in SVN. You can revert your commit and commit the same one again, with proper message. In the git world this would be possible (locally, with git commit --amend), but after you push to a remote repository this would be discouraged and the same way as above would be advised since

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Steve Rowe
Not true - you can fix it in SVN. From : svn propset -r N --revprop svn:log "new log message” URL -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:13 PM, Dawid Weiss wrote: > > No way to do it in SVN. You can

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Dawid Weiss
Interesting! If it does work then: 1) I'd notify infra because this permits any committer to destroy the log history without a trace ;) 2) the consequences for git mirrors of any project that did such a change are also interesting -- incremental git svn won't pick these up and effectively the

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Uwe Schindler
Hi, Works on Apache Lucene without problems. Not sure about distribution repo. Used it several times to fix typos in issue number. Only JIRA robot does not get it, so it won't auto-comment. Uwe Am 22. Januar 2016 20:21:29 MEZ, schrieb Dawid Weiss : >I'm sorry, I wasn't

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Anshum Gupta
Hi Adrien, I'm in the middle of publishing the artifacts. I should be able to get to it in just a bit. Thanks for reminding. On Fri, Jan 22, 2016 at 7:58 AM, Adrien Grand wrote: > Anshum, I would like to draw your attention to the fact that Dawid plans > to start the git

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Ishan Chattopadhyaya
Seems to have worked for Dennis: http://lucene.472066.n3.nabble.com/Update-commit-message-td4249465.html#a4249469 On Sat, Jan 23, 2016 at 12:51 AM, Dawid Weiss wrote: > I'm sorry, I wasn't precise enough -- have you tried it on the Apache > SVN? Quote: > > "The first way

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Anshum Gupta
I'll leave it as is. I don't think this is a cause of concern. Thanks to you and Steve for all the suggestions! On Fri, Jan 22, 2016 at 11:41 AM, Dawid Weiss wrote: > > Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision > properties (of which svn:log is

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Anshum Gupta
I've added the back-compat indexes for 5.3.2 to lucene_solr_5_3, branch_5x, and trunk. Think we are good to go in terms the 5.3.2 release-svn dependency. On Fri, Jan 22, 2016 at 11:41 AM, Anshum Gupta wrote: > Adrien, > > Seems like I'd have to wait until the release is

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Jan Høydahl
Thanks. Fixed a trivial typo in the Solr notes: "Solr 5.3.1 includes 11 bug fixes” —> "Solr 5.3.2 includes 11 bug fixes" -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 21. jan. 2016 kl. 20.16 skrev Anshum Gupta : > > The vote has

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-22 Thread Adrien Grand
Anshum, I would like to draw your attention to the fact that Dawid plans to start the git migration at 4PM PST, and I think it would be preferable to commit the backward compatibility indices before that (which I think is the only remaining step that requires you to modify the code base). If you

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-21 Thread Anshum Gupta
The vote has now passed. Thank you everyone for voting. Here is the draft for the 5.3.2 release notes. Let me know if I missed something. Lucene: https://wiki.apache.org/lucene-java/ReleaseNote532 Solr: https://wiki.apache.org/solr/ReleaseNote532 On Wed, Jan 20, 2016 at 3:33 AM, Ahmet Arslan

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-20 Thread Ahmet Arslan
+1 SUCCESS! [1:38:55.940645] On Tuesday, January 19, 2016 10:25 PM, Yonik Seeley wrote: +1 -Yonik On Mon, Jan 18, 2016 at 11:23 AM, Anshum Gupta wrote: > Please vote for the RC2 release candidate for Lucene/Solr 5.3.2 > > The artifacts can be

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-19 Thread Yonik Seeley
+1 -Yonik On Mon, Jan 18, 2016 at 11:23 AM, Anshum Gupta wrote: > Please vote for the RC2 release candidate for Lucene/Solr 5.3.2 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.3.2-RC2-rev1725196 > > You can run

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-19 Thread Steve Rowe
+1 Docs, changes and javadocs look good. Smoke tester with Java7 & Java8: SUCCESS! [0:47:55.140380] -- Steve www.lucidworks.com > On Jan 19, 2016, at 2:39 AM, Noble Paul wrote: > > +1 > > SUCCESS! [1:32:46.196214] > > using java 7 > > On Tue, Jan 19, 2016 at 12:53

[VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-18 Thread Anshum Gupta
Please vote for the RC2 release candidate for Lucene/Solr 5.3.2 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.3.2-RC2-rev1725196 You can run the smoke tester directly with this command: python3 -u dev-tools/scripts/smokeTestRelease.py

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-18 Thread Michael McCandless
+1 SUCCESS! [0:30:48.710775] Mike McCandless http://blog.mikemccandless.com On Mon, Jan 18, 2016 at 11:23 AM, Anshum Gupta wrote: > Please vote for the RC2 release candidate for Lucene/Solr 5.3.2 > > The artifacts can be downloaded from: >

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-18 Thread Tomás Fernández Löbbe
SUCCESS! [1:16:42.067861] +1 On Mon, Jan 18, 2016 at 11:09 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > +1 > > SUCCESS! [0:30:48.710775] > > Mike McCandless > > http://blog.mikemccandless.com > > > On Mon, Jan 18, 2016 at 11:23 AM, Anshum Gupta > wrote: >

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-18 Thread Noble Paul
+1 SUCCESS! [1:32:46.196214] using java 7 On Tue, Jan 19, 2016 at 12:53 PM, Shalin Shekhar Mangar wrote: > +1 > > SUCCESS! [1:27:55.806617] > > On Mon, Jan 18, 2016 at 9:53 PM, Anshum Gupta wrote: >> Please vote for the RC2 release candidate for

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

2016-01-18 Thread Shalin Shekhar Mangar
+1 SUCCESS! [1:27:55.806617] On Mon, Jan 18, 2016 at 9:53 PM, Anshum Gupta wrote: > Please vote for the RC2 release candidate for Lucene/Solr 5.3.2 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.3.2-RC2-rev1725196