Re: 5.3.2 bug fix release

what's the status of 5.3.2 release ? On Tue, Dec 29, 2015 at 8:30 PM, Anshum Gupta wrote: > Thanks for committing those David. > > I just brought everything in synch on the 5.3.2 change log section on all > the branches. > > I have also committed everything but I want to also commit SOLR-8470 bef

Re: 5.3.2 bug fix release

Thanks for committing those David. I just brought everything in synch on the 5.3.2 change log section on all the branches. I have also committed everything but I want to also commit SOLR-8470 before cutting the RC (unless someone objects). In case someone has something else to back port, kindly d

Re: 5.3.2 bug fix release

Yikes; I’m sure that was painful. So I just back-ported a couple issues, SOLR-8340 & SOLR-8059. I was about to manually keep the 5.3.2 section in branch_5x & trunk in sync but then thought better of it. Might as well wait until 5.3.2 is voted and then do it, since there are bound to be others wh

Re: 5.3.2 bug fix release

Sorry for the long delay but I burnt my hand and so have been MIA. It's better now so I'll port the issues and cut an RC on Wednesday. On Wed, Dec 23, 2015 at 9:22 PM, Anshum Gupta wrote: > I've added the section for 5.3.2 in all the branches. Kindly back-port > stuff that you think makes sense

Re: 5.3.2 bug fix release

I've added the section for 5.3.2 in all the branches. Kindly back-port stuff that you think makes sense to go into a 'bug-fix' release for 5.3.1 only. I think it'd make sense to duplicate entries for JIRAs we back port. On Mon, Dec 21, 2015 at 11:38 AM, Anshum Gupta wrote: > Seems like Noble ra

Re: 5.3.2 bug fix release

Seems like Noble ran addVersion.py for 5.3.2 on the lucene_solr_5_3 branch during the 5.3.1 release. I can now run it for branch_5x and trunk with the old change id but there are a ton of property changes to multiple files. Can someone confirm that it'd be fine? The addVersion on 5.3.2, that I'm tr

Re: 5.3.2 bug fix release

I’d like to backport SOLR-8059 & SOLR-8060 (same as SOLR-8340): NPEs that can happen in DebugComponent & HighlightComponent when distrib.singlePass=true (which is implied under certain conditions even if not explicitly =true). On Thu, Dec 17, 2015 at 8:54 AM Jan Høydahl wrote: > If there is a 5.

Re: 5.3.2 bug fix release

If there is a 5.3.2 release, we should probably also backport this one: SOLR-8269 : Upgrade commons-collections to 3.2.2. This fixes a known serialization vulnerability -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 1

Re: 5.3.2 bug fix release

Yes, there was already a 5.3.2 version in JIRA. I will start back-porting stuff to the lucene_solr_5_3 branch later in the day today. On Thu, Dec 17, 2015 at 11:35 AM, Noble Paul wrote: > Agree with Shawn here. > > If a company has already done the work to upgrade their systems to > 5.3.1 , the

Re: 5.3.2 bug fix release

Agree with Shawn here. If a company has already done the work to upgrade their systems to 5.3.1 , they would rather have a bug fix for the old version . So anshum, is there a 5.3.2 version created in JIRA? can we start tagging issues to that release so that we can have a definitive list of bugs t

Re: 5.3.2 bug fix release

Thanks for explaining it so well Shawn :) Yes, that's pretty much the reason why it makes sense to have a 5.3.2 release. We might even need a 5.4.1 after that as there are more security bug fixes that are getting committed as the feature is being tried by users and bugs are being reported. On Th

Re: 5.3.2 bug fix release

On 12/16/2015 2:15 PM, Upayavira wrote: > Why don't people just upgrade to 5.4? Why do we need another release in > the 5.3.x range? I am using a third-party custom Solr plugin. The latest version of that plugin (which I have on my dev server) has only been certified to work with Solr 5.3.x. The

Re: 5.3.2 bug fix release

Historical aside: I was thinking we’d never produced a bugfix release on a previous minor branch, but I went looking and found that 4.9.1, released 9/21/14, was just such a one: 4.10.0 was released on 9/4/14. AFAICT Mike McCandless initially proposed a 4.9.1 release on 9/16/14 here:

Re: 5.3.2 bug fix release

Anshum, If there happens to be a security bugfix release, I'd like to have SOLR-8373 included as well. It is a deal breaker for anyone who uses Kerberos support and wants to have more than one solr node per host. Thanks, Ishan On Thu, Dec 17, 2015 at 2:45 AM, Upayavira wrote: > Why don't people

Re: 5.3.2 bug fix release

Why don't people just upgrade to 5.4? Why do we need another release in the 5.3.x range? Upayavira On Wed, Dec 16, 2015, at 09:12 PM, Shawn Heisey wrote: > On 12/16/2015 1:08 PM, Anshum Gupta wrote: > > There are a bunch of important bug fixes that call for a 5.3.2 in my > > opinion. I'm specific

Re: 5.3.2 bug fix release

On 12/16/2015 1:08 PM, Anshum Gupta wrote: > There are a bunch of important bug fixes that call for a 5.3.2 in my > opinion. I'm specifically talking about security plugins related fixes > but I'm sure there are others too. > > Unless someone else wants to do it, I'd volunteer to do the release > a