Re: Next release...

Le jeu. 12 nov. 2015 à 18:21, Erick Erickson a écrit : > Are there any tentative (not firm commitments) time frames for 6.0? > I don't think we talked about it before. Maybe we could aim for something like February 2016. This would be one year after 5.0, which I think

Re: Next release...

+1 to not sooner than February 2016 (one year later) On Fri, Nov 13, 2015 at 6:25 AM Adrien Grand wrote: > Le jeu. 12 nov. 2015 à 18:21, Erick Erickson a > écrit : > >> Are there any tentative (not firm commitments) time frames for 6.0? >> > > I

Re: Next release...

e data loss problems in CDCR so I don't >>>> think we should put CDCR in 5.4 unless that issue is fixed first. >>>> >>>> On Mon, Nov 9, 2015 at 9:02 PM, Erick Erickson <ericke

Re: Next release...

SOLR-6273) > is about ready to rock-n-roll. It's a lot of code, and I don't want to > push it into 5x just before we cut the next release. So if 5.4 is > imminent I'd like to know for my planning. > > Thanks! > Erick > >

Re: Next release...

the CCR (SOLR-6273) > > is about ready to rock-n-roll. It's a lot of code, and I don't want to > > push it into 5x just before we cut the next release. So if 5.4 is > > imminent I'd like to know for my planning. > > > > Thanks! > > Erick > > > > -

Re: Next release...

Created a blocker https://issues.apache.org/jira/browse/SOLR-8269 so we don’t forget… There could be other workarounds than waiting for their release, feel free to degrade priority if necessary. -- Jan Høydahl, search solution architect

Re: Next release...

Erick Erickson <erickerick...@gmail.com> >> wrote: >> > What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) >> > is about ready to rock-n-roll. It's a lot of code, and I don't want to >> > push it into

Re: Next release...

2 PM, Erick Erickson <erickerick...@gmail.com> >>> wrote: >>> > What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) >>> > is about ready to rock-n-roll. It's a lot of code, and I don't want to >>> > push it into 5x just before we

Re: Next release...

Le lun. 9 nov. 2015 à 19:16, Upayavira a écrit : > I would love to see a 5.4 release. All the tasks I had planned for the > admin UI are done, so, barring any unforseen and as yet unreported bugs, > it is ready to go. > > How much time commitment does it typically take to make

Re: Next release...

Grand <jpou...@gmail.com> wrote: > > Le lun. 9 nov. 2015 à 16:32, Erick Erickson <erickerick...@gmail.com> a > > écrit : > >> > >> What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) > >> is about ready to rock-n-roll. It's a lot

Re: Next release...

Le lun. 9 nov. 2015 à 16:32, Erick Erickson <erickerick...@gmail.com> a écrit : > What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) > is about ready to rock-n-roll. It's a lot of code, and I don't want to > push it into 5x just before we cut the next rel

Next release...

What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) is about ready to rock-n-roll. It's a lot of code, and I don't want to push it into 5x just before we cut the next release. So if 5.4 is imminent I'd like to know for my planning. Thanks! Erick

Re: Next release...

>> What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) >> is about ready to rock-n-roll. It's a lot of code, and I don't want to >> push it into 5x just before we cut the next release. So if 5.4 is >> imminent I'd like to know for my planning. > > > I t

Re: Next release...

erick...@gmail.com> > wrote: > > What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) > > is about ready to rock-n-roll. It's a lot of code, and I don't want to > > push it into 5x just before we cut the next release. So if 5.4 is > > imminent I'd like to

Re: Next release...

Make that CDCR On Mon, Nov 9, 2015 at 7:32 AM, Erick Erickson <erickerick...@gmail.com> wrote: > What is the thinking on cutting 5.4? It looks like the CCR (SOLR-6273) > is about ready to rock-n-roll. It's a lot of code, and I don't want to > push it into 5x just before

Re: Next release...

on, Nov 9, 2015 at 8:00 AM, Adrien Grand <jpou...@gmail.com> wrote: > > > Le lun. 9 nov. 2015 à 16:32, Erick Erickson <erickerick...@gmail.com> > a > > > écrit : > > >> > > >> What is the thinking on cutting 5.4? It looks like the CCR (SOLR-62

[jira] Commented: (SOLR-831) revist jar packaging prior to next release

-900. Now solr-core does not contain solrj and there is no solr-commons jar anymore. Hoss's comment on moving the source folders remains valid. But I think we can mark this one as resolved/invalid. revist jar packaging prior to next release

[jira] Assigned: (SOLR-831) revist jar packaging prior to next release

[ https://issues.apache.org/jira/browse/SOLR-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar reassigned SOLR-831: -- Assignee: Shalin Shekhar Mangar revist jar packaging prior to next release

[jira] Created: (SOLR-831) revist jar packaging prior to next release

revist jar packaging prior to next release -- Key: SOLR-831 URL: https://issues.apache.org/jira/browse/SOLR-831 Project: Solr Issue Type: Bug Components: clients - java Affects Versions

Re: Next release?

Hi, On Tue, Feb 19, 2008 at 11:14 PM, Andrzej Bialecki [EMAIL PROTECTED] wrote: Hi all, I propose to start planning for the next release, and tentatively I propose to schedule it for the beginning of April. I'm going to close a lot of old and outdated issues in JIRA - other committers

Re: Next release?

Andrzej Bialecki wrote: Hi all, I propose to start planning for the next release, and tentatively I propose to schedule it for the beginning of April. Sounds good. I'm going to close a lot of old and outdated issues in JIRA - other committers, please do the same if you know

Re: Next release?

Doğacan Güney wrote: There are some issues I want to put in before a release. Most are trivial but I would like to draw attention to NUTCH-442, as it is an issue that I (and looking at its votes, others) want to see resolved before another release. I really could use some review and

Next release?

Hi all, I propose to start planning for the next release, and tentatively I propose to schedule it for the beginning of April. I'm going to close a lot of old and outdated issues in JIRA - other committers, please do the same if you know that a given issue no longer applies. Out

Next release - 0.10.0 or 1.0.0 ?

Hi all, I know it's a trivial issue, but still ... When this release is out, I propose that we should name the next release 1.0.0, and not 0.10.0. The effect is purely psychological, but it also reflects our confidence in the platform. Many Open Source projects are afraid of going to 1.0.0

RE: Next release - 0.10.0 or 1.0.0 ?

: Andrzej Bialecki [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 2:38 PM To: nutch-dev@lucene.apache.org Subject: Next release - 0.10.0 or 1.0.0 ? Hi all, I know it's a trivial issue, but still ... When this release is out, I propose that we should name the next release 1.0.0

Re: Next release - 0.10.0 or 1.0.0 ?

+1 Andrzej Bialecki wrote: Hi all, I know it's a trivial issue, but still ... When this release is out, I propose that we should name the next release 1.0.0, and not 0.10.0. The effect is purely psychological, but it also reflects our confidence in the platform. I think that a 1.0

Re: Next release - 0.10.0 or 1.0.0 ?

that we should name the next release 1.0.0, and not 0.10.0. The effect is purely psychological, but it also reflects our confidence in the platform. Many Open Source projects are afraid of going to 1.0.0 and seem to be unable to ever reach this level, as if it were a magic step beyond which