Re: A 5.4 release?

nice upayavira. Every new RM adds value to the release todo. Enjoy the ride  On Dec 5, 2015 2:55 PM, "Upayavira" wrote: > * Make sure you don't have another Solr instance running on port 8983 > whilst running the smoke test (even a Vagrant instance sharing the port > without

Re: A 5.4 release?

* Make sure you don't have another Solr instance running on port 8983 whilst running the smoke test (even a Vagrant instance sharing the port without Solr running) as the smoke test will fail. Yes, I'm planning to "soften" the release notes to make them less dense and more accessible. Upayavira

Re: A 5.4 release?

Thanks Varun. As a first time Release Manager, I'm currently working through the steps needed to build a release. I'll call a vote as soon as I have uploaded artifacts that are passing smoke tests. Upayavira On Fri, Dec 4, 2015, at 07:16 AM, Varun Thacker wrote: > Hi Upayavira, > > I have

Re: A 5.4 release?

On Fri, Dec 4, 2015 at 2:29 PM, Upayavira wrote: > > On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote: >> >> On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote: >> >> > As a first time Release Manager >> >> Thanks Upayavira! >> >> But please, please,

Re: A 5.4 release?

On Fri, Dec 4, 2015, at 08:59 PM, Michael McCandless wrote: > On Fri, Dec 4, 2015 at 2:29 PM, Upayavira wrote: > > > > On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote: > >> > >> On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote: > >> > >> > As a

Re: A 5.4 release?

This is good ! :) just so that you know, make sure that your key is up on id.apache.org too! I struggled with that for almost a day during my first release (I believe I added that to the wiki too). On Sat, Dec 5, 2015 at 12:59 AM, Upayavira wrote: > > > On Fri, Dec 4, 2015,

Re: A 5.4 release?

On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote: > As a first time Release Manager Thanks Upayavira! But please, please, please take advantage of your newness to this, to edit https://wiki.apache.org/lucene-java/ReleaseTodo when things are confusing/missing/etc.! Being new

Re: A 5.4 release?

On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote: > On Fri, Dec 4, 2015 at 11:34 AM, Upayavira wrote: > > > As a first time Release Manager > > Thanks Upayavira! > > But please, please, please take advantage of your newness to this, to > edit

Re: A 5.4 release?

Hi Upayavira, I have committed a fix for SOLR-8363 . You should be good to go. On Thu, Dec 3, 2015 at 8:00 PM, Upayavira wrote: > Agreed. Waiting on SOLR-8363 right now. > > On Thu, Dec 3, 2015, at 02:14 PM, Shalin Shekhar Mangar wrote: > > Agreed, what's done is done but in

Re: A 5.4 release?

Hi Everyone, I think we should try to fix SOLR-8363 before the RC? Seems like this problem has been there for a while since the luceneMatchVersion hasn't updated in a while. So if others feel this isn't worth the delay then I'll remove it from being a blocker. On Thu, Dec 3, 2015 at 3:07 PM,

Re: A 5.4 release?

SOLR-8330 is not critical so I don't think it should have been committed to the 5.4 branch. This gives CI too little time to find problems before Upayavira cuts a release candidate. Le jeu. 3 déc. 2015 à 03:34, Anshum Gupta a écrit : > Hi, > > I'd like to get SOLR-8330

RE: A 5.4 release?

ct: Re: A 5.4 release? SOLR-8330 is not critical so I don't think it should have been committed to the 5.4 branch. This gives CI too little time to find problems before Upayavira cuts a release candidate. Le jeu. 3 déc. 2015 à 03:34, Anshum Gupta <ans...@anshumgupta.net &l

Re: A 5.4 release?

A really strong reason would be to not shove last minute changes right before releases. On Thu, Dec 3, 2015 at 9:08 AM, Anshum Gupta wrote: > I'll admit I committed it thinking it was safe and didn't bring any > flakiness into the system but it's not something critical.

Re: A 5.4 release?

I've just generated the first RC, but haven't posted it. How long do you expect it to take to get this bug resolved? It does seem worth doing. Upayavira On Thu, Dec 3, 2015, at 09:51 AM, Varun Thacker wrote: > Hi Everyone, > > I think we should try to fix SOLR-8363 before the RC? > > Seems like

Re: A 5.4 release?

Agreed, what's done is done but in future, let's avoid shoving anything other than critical bug fixes into release branches. On Thu, Dec 3, 2015 at 7:42 PM, Robert Muir wrote: > A really strong reason would be to not shove last minute changes right > before releases. > > On

Re: A 5.4 release?

Agreed. Waiting on SOLR-8363 right now. On Thu, Dec 3, 2015, at 02:14 PM, Shalin Shekhar Mangar wrote: > Agreed, what's done is done but in future, let's avoid shoving > anything other than critical bug fixes into release branches. > > On Thu, Dec 3, 2015 at 7:42 PM, Robert Muir

Re: A 5.4 release?

I'll admit I committed it thinking it was safe and didn't bring any flakiness into the system but it's not something critical. I'll let the release manager decide if it's fine being released with 5.4. If he thinks otherwise (or someone else has a really strong reason) we can roll this back, though

Re: A 5.4 release?

Sure. The last message on the thread was from about 8 days ago so I wasn't sure if it would be a while before the RC was cut giving this enough time on the branch. In any case, I agree with not shoving things in last moment. On Thu, Dec 3, 2015 at 8:00 PM, Upayavira wrote: >

Re: A 5.4 release?

Hi, I'd like to get SOLR-8330 in for 5.4. I'm currently merging and running tests so let me know if I shouldn't be merging this in. On Thu, Nov 26, 2015 at 11:00 PM, Upayavira wrote: > Thanks to Steve and Uwe, we now have both ASF and Policeman Jenkins > pointing at the 5.4

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

gt; Christine >> >> From: dev@lucene.apache.org At: Nov 30 2015 14:29:58 >> To: dev@lucene.apache.org >> Subject: Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 >> release?) >> >> The patch seems innocuous enough. From the ticket tho

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

cket title and summary. Will await > >> further opinions before applying or not applying the patch to 5.4 branch > >> (and trunk and branch_5x). > >> > >> Christine > >> > >> From: dev@lucene.apache.org At: Nov 30 2015 14:29:58 > >> To: dev@lucene.apa

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

patch to 5.4 > branch > > >> (and trunk and branch_5x). > > >> > > >> Christine > > >> > > >> From: dev@lucene.apache.org At: Nov 30 2015 14:29:58 > > >> To: dev@lucene.apache.org > > >> Subject: Re: 5.4 branch

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

ket title and summary. Will await > further opinions before applying or not applying the patch to 5.4 branch > (and trunk and branch_5x). > > Christine > > From: dev@lucene.apache.org At: Nov 30 2015 14:29:58 > To: dev@lucene.apache.org > Subject: Re: 5.4 branch created, featu

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

, feature freeze in place (was Re: A 5.4 release?) The patch seems innocuous enough. From the ticket though it isn't so clear to me what problem it solves. I'm open to the opinion of others. Upayavira On Mon, Nov 30, 2015, at 12:09 PM, Christine Poerschke (BLOOMBERG/ LONDON) wrote

Re:5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

As suggested I have now patched https://issues.apache.org/jira/browse/SOLR-8340 fix to 5.4 branch. From: dev@lucene.apache.org At: Nov 25 2015 14:11:46 To: dev@lucene.apache.org Subject: Re:5.4 branch created, feature freeze in place (was Re: A 5.4 release?) I have created

Re:5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

, feature freeze in place (was Re: A 5.4 release?) I have created the lucene_solr_5_4 branch. Please, no new features in this branch. Please update this thread with any changes you propose to make to this branch. Only JIRA tickets which are a blocker and have fix version 5.4 will delay

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

g/jira/browse/LUCENE-6911 fix into 5.4 solr or > not? Basically StandardQueryParser's existing getMultiFields method is > a no-op. > > From: dev@lucene.apache.org At: Nov 25 2015 14:11:46 To: > dev@lucene.apache.org Subject: Re:5.4 branch created, feature freeze > in place (was

Re: A 5.4 release?

@Upayavira is there a branch created for 5.4 already. I see one already On Thu, Nov 26, 2015 at 2:08 AM, Erick Erickson wrote: > Do note that this is the Thanksgiving holiday here in the US, lots of > people are out for the week. Mostly FYI, just don't be surprised if >

Re: A 5.4 release?

OK . So I need to commit my fixes there. I missed the branch creation mail On Thu, Nov 26, 2015 at 9:34 PM, Noble Paul wrote: > @Upayavira is there a branch created for 5.4 already. I see one already > > On Thu, Nov 26, 2015 at 2:08 AM, Erick Erickson

Re: A 5.4 release?

thx :-) On Thu, Nov 26, 2015, at 04:07 PM, Noble Paul wrote: > OK . So I need to commit my fixes there. I missed the branch creation > mail > > > On Thu, Nov 26, 2015 at 9:34 PM, Noble Paul wrote: > > @Upayavira is there a branch created for 5.4 already. I see one already

Re: A 5.4 release?

Thanks to Steve and Uwe, we now have both ASF and Policeman Jenkins pointing at the 5.4 branch. Upayavira On Thu, Nov 26, 2015, at 04:10 PM, Upayavira wrote: > thx :-) > > On Thu, Nov 26, 2015, at 04:07 PM, Noble Paul wrote: > > OK . So I need to commit my fixes there. I missed the branch

Re: A 5.4 release?

I closed LUCENE-6722 as a 'won't fix' On Wed, Nov 25, 2015 at 7:35 PM, Upayavira wrote: > I shall shortly create the 5.4 release branch. From this moment, the feature > freeze starts. > > Looking through JIRA, I see some 71 tickets assigned to fix version 5.4. I > suspect we

Re: A 5.4 release?

I'll take it up, Ishan. On Wed, Nov 25, 2015 at 9:11 PM, Ishan Chattopadhyaya wrote: >> SOLR-8073 should be marked as resolved for 5.4 > > Can someone please review and commit this? > > On Wed, Nov 25, 2015 at 9:09 PM, Shalin Shekhar Mangar >

Re: A 5.4 release?

> SOLR-8073 should be marked as resolved for 5.4 Can someone please review and commit this? On Wed, Nov 25, 2015 at 9:09 PM, Shalin Shekhar Mangar < shalinman...@gmail.com> wrote: > I closed LUCENE-6722 as a 'won't fix' > > On Wed, Nov 25, 2015 at 7:35 PM, Upayavira wrote: >

Re: A 5.4 release?

I would like to put SOLR-7169 (also fixes 8267) and SOLR-8101 into 5.4. I'll commit to trunk and 5x today ... let me know if there are any objections to also including in 5.4 branch Tim On Wed, Nov 25, 2015 at 6:05 AM, Upayavira wrote: > I shall shortly create the 5.4 release

Re: A 5.4 release?

Ok, those fixes are in 5.4 now, thanks! On Wed, Nov 25, 2015 at 9:49 AM, Upayavira wrote: > I'm for one am okay with these going into 5.4. > > Upayavira > > On Wed, Nov 25, 2015, at 05:28 PM, Timothy Potter wrote: >> I would like to put SOLR-7169 (also fixes 8267) and SOLR-8101

Re: A 5.4 release?

I'm for one am okay with these going into 5.4. Upayavira On Wed, Nov 25, 2015, at 05:28 PM, Timothy Potter wrote: > I would like to put SOLR-7169 (also fixes 8267) and SOLR-8101 into > 5.4. I'll commit to trunk and 5x today ... let me know if there are > any objections to also including in 5.4

Re: A 5.4 release?

Do note that this is the Thanksgiving holiday here in the US, lots of people are out for the week. Mostly FYI, just don't be surprised if you get more traffic on this starting next week ;) On Wed, Nov 25, 2015 at 11:35 AM, Timothy Potter wrote: > Ok, those fixes are in 5.4

Re: A 5.4 release?

Thanks for managing this release Upayavira! There's a patch on the issue which resolves it but I'll wait for Noble to commit it. I can do that as well, but he put up the original patch and also assigned the issue to himself so don't want to be rude. :) I think Noble would be able to commit this

Re: A 5.4 release?

I shall shortly create the 5.4 release branch. From this moment, the feature freeze starts. Looking through JIRA, I see some 71 tickets assigned to fix version 5.4. I suspect we won't be able to fix all 71 in one week, so I expect that the majority will be pushed, after this release, to 5.5.

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

I plan to address SOLR-8180 which is about adding jcl-over-slf4j as a dependency on SolrJ. On Wed, Nov 25, 2015 at 9:11 AM Upayavira wrote: > I have created the lucene_solr_5_4 branch. Please, no new features in this > branch. > > Please update this thread with any changes you

Re: A 5.4 release?

SOLR-8073 should be marked as resolved for 5.4 SOLR-6992 - I would love for somebody to fix it, it is absolutely trivial and would be good to have fixed for consistency at least in the last version 5.x (it is also incorrectly marked as Unresolved against 5.0) Newsletter and resources for

5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

I have created the lucene_solr_5_4 branch. Please, no new features in this branch. Please update this thread with any changes you propose to make to this branch. Only JIRA tickets which are a blocker and have fix version 5.4 will delay a release candidate build. Please do review the below - and

Re: A 5.4 release?

Given seeming acceptance of my proposal, I will create a feature branch Monday or Tuesday this week. From that point on, we will enter a feature freeze (on that new branch), which will last for a week, after which I will produce the first 5.4 release candidate. Let me know if anyone has any

Re: A 5.4 release?

+1 let's get 5.4 out! Thanks Upayavira for managing this release.

Re: A 5.4 release?

+1 It's long overdue On Wed, Nov 18, 2015 at 12:22 AM, Upayavira wrote: > Hi, > > I'm volunteering to make a 5.4 release. If there are no objections, I > will create a release branch next Monday/Tuesday and a release candidate > a week later. > > Anyone see any issues with

Re: A 5.4 release?

The typical process is just what you're doing: Announce a date not too far in the future and anyone who requires something for the 5.4 can plead for more time. Works for me. On Tue, Nov 17, 2015 at 11:07 AM, Noble Paul wrote: > +1 It's long overdue > > On Wed, Nov 18,