Re: Question about release plans amidst the git transition

Thanks Uwe, much appreciated. Dawid On Fri, Jan 22, 2016 at 1:55 PM, Uwe Schindler wrote: > I am on a trip in Amsterdam, returning this evening. I will take care of > Jenkins! Will update Policeman's JDKs, too, and install all necessary Git > tools on Slave VMs. > > Uwe > > Am

Re: Question about release plans amidst the git transition

So, we do the switch, right? Seeing the discussions and conflicting arguments/ preferences I'm no longer that enthusiastic about the whole ordeal... it feels like we're trying to disturb people in their work. Sigh. Anyway, if this experiment doesn't work we *can* revert. It's not the end of the

Re: Question about release plans amidst the git transition

I am on a trip in Amsterdam, returning this evening. I will take care of Jenkins! Will update Policeman's JDKs, too, and install all necessary Git tools on Slave VMs. Uwe Am 22. Januar 2016 13:21:40 MEZ, schrieb Dawid Weiss : >So, we do the switch, right? Seeing the

Re: Question about release plans amidst the git transition

It's nothing personal, Erik! I honestly wouldn't want people to put additional effort just for the sake of saying "we've switched to git". But at the same time what's driving me is what I mentioned at the beginning -- I was reluctant to switch to git (with my other projects) at first too, but I

Re: Question about release plans amidst the git transition

Dawid: Ignore me. Mostly raising the issue to make sure it was considered. I'm not about to argue with the "heavies" on this issue... Full Speed Ahead! On Fri, Jan 22, 2016 at 4:57 AM, Dawid Weiss wrote: > Thanks Uwe, much appreciated. > > Dawid > > On Fri, Jan 22, 2016

RE: Question about release plans amidst the git transition

+1 - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Robert Muir [mailto:rcm...@gmail.com] > Sent: Thursday, January 21, 2016 8:18 AM > To: dev@lucene.apache.org > Subject: Re: Questio

Re: Question about release plans amidst the git transition

+1 Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Jan 21, 2016 at 4:18 AM, Adrien Grand wrote: > Another reason I would be +1 to releasing 5.5 is that there are some > appealing changes sitting on the 5.x branch like better rewriting of > boolean queries or better

Re: Question about release plans amidst the git transition

+1 fine idea Rob! On Thu, Jan 21, 2016 at 2:18 AM Robert Muir wrote: > one idea, we could use it to our advantage: as soon as we go to git, > immediately (e.g. after just a few days or whatever) start a 5.5 > release? > > besides keeping things less confusing, it could make

Re: Question about release plans amidst the git transition

Another reason I would be +1 to releasing 5.5 is that there are some appealing changes sitting on the 5.x branch like better rewriting of boolean queries or better handling of "slow" (two-phased) queries in disjunctions and negations. Le jeu. 21 janv. 2016 à 08:18, Robert Muir

Re: Question about release plans amidst the git transition

On Thu, Jan 21, 2016 at 2:17 AM, Robert Muir wrote: > one idea, we could use it to our advantage: as soon as we go to git, > immediately (e.g. after just a few days or whatever) start a 5.5 > release? +1 Mike McCandless http://blog.mikemccandless.com

Re: Question about release plans amidst the git transition

+1 to have a 5.5 release. On Thu, Jan 21, 2016 at 10:12 PM, Erick Erickson wrote: > I like the idea of doing a 5.5 Git-based release, your points about > separating the pain of the first Git build and a major release are > well taken, thanks for thinking about it! > >

Re: Question about release plans amidst the git transition

On Thu, Jan 21, 2016 at 11:42 AM, Erick Erickson wrote: > > My only comment is that 5.5 coming just a few days after 5.4.x seems > pretty short, but maybe it'll take a month to get the first Git build > ironed out anyway... I don't understand this: 5.4 was released over

Re: Question about release plans amidst the git transition

I a thinking 5.4.1, RC2, vote just passed. No big deal either way, whoever's doing the work can decide how much runway they want to have if any. On Thu, Jan 21, 2016 at 8:55 AM, Robert Muir wrote: > On Thu, Jan 21, 2016 at 11:42 AM, Erick Erickson >

Re: Question about release plans amidst the git transition

I dont see how a bugfix release relates to it. Thats a bugfix release with a corruption fix: its totally unrelated. we have over a months worth of improvements and features in 5.5! On Thu, Jan 21, 2016 at 12:32 PM, Erick Erickson wrote: > I a thinking 5.4.1, RC2, vote

Re: Question about release plans amidst the git transition

Yeah, a month is fine for a release. No one has to upgrade at the pace we release, and previous bug fix releases will often come out even *after* the next point release. We would have to spend an insane amount of effort to get too releasing too often IMO. - Mark On Thu, Jan 21, 2016 at 12:36 PM

Re: Question about release plans amidst the git transition

I like the idea of doing a 5.5 Git-based release, your points about separating the pain of the first Git build and a major release are well taken, thanks for thinking about it! My only comment is that 5.5 coming just a few days after 5.4.x seems pretty short, but maybe it'll take a month to get

Re: Question about release plans amidst the git transition

: My only comment is that 5.5 coming just a few days after 5.4.x seems : pretty short, but maybe it'll take a month to get the first Git build : ironed out anyway... Even if if everything goes smoothly and we discover that magically everything still works and we are "ready" to do a 5.5 release

Re: Question about release plans amidst the git transition

+1 to a 5.5 release. I really think we should do a deprecation release before 6.0, and that may/may not be 5.5. On Wed, Jan 20, 2016 at 11:17 PM, Robert Muir wrote: > one idea, we could use it to our advantage: as soon as we go to git, > immediately (e.g. after just a few days

Re: Question about release plans amidst the git transition

one idea, we could use it to our advantage: as soon as we go to git, immediately (e.g. after just a few days or whatever) start a 5.5 release? besides keeping things less confusing, it could make the 6.0 release more easygoing. because we'd have already worked through the pain of release process