Those forking kibana on github and issuing a pull request - is their effort in vain?
On 17 September 2014 23:37, Rashid Khan <rashid.k...@elasticsearch.com> wrote: > Unfortunately I can’t give you an ETA other than soon ;-) > > Initially backwards compatibility will not be available as there have been > a large number of core changes. We’re looking at providing a compatibility > layer to ease the transition, but there are some challenges there. > > > On Thu, Aug 14, 2014 at 10:22 AM, Antonio Augusto Santos < > mkha...@gmail.com> wrote: > >> Thanks a lot for the update Rashid. >> I know it might be too much but... any dates we can mark on out calendar? >> ;) >> >> On Thursday, August 14, 2014 1:04:24 PM UTC-3, Rashid Khan wrote: >>> >>> Yes there is a new version in the works. >>> >>> Elasticsearch has grown considerably in the last 18 months. With >>> Elasticsearch 1.0, and the introduction of aggregations, we quickly >>> realized we needed a better platform for building more powerful interfaces. >>> So for the last few months we've been head down, working to polish Kibana 4 >>> to the point where we can collect feedback and contributions. >>> >>> We've left lots of pull requests open for a couple reasons: For the >>> community to pull into their own fork if needed, and for our own >>> inspiration. When someone submits code it says "I really want this!". Even >>> if the code doesn't get merged, we take it very seriously. Once we push out >>> the first preview of Kibana 4 we'll be cleaning up lots of pull requests >>> for features we're implemented. >>> >>> As for the features you're looking for: User separation and event >>> correlation are things we're looking to do in Elasticsearch. Multi-value >>> metric aggregations are a feature I'm looking forward to in Kibana. It >>> will, of course, be open source. >>> >>> On Tuesday, August 12, 2014 9:44:55 AM UTC-7, Antonio Augusto Santos >>> wrote: >>>> >>>> This one is for the devs, and Rashid in special: there is any new >>>> version of Kibana in the works? >>>> I'm asking this because I'm about to start a project in my company for >>>> log management, and there are some requisites to it (user separation, event >>>> correlation, histogram to compare two values, and so on). >>>> >>>> So, any changes of these functionalities landing on Kibana 4.0? ;) >>>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "elasticsearch" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elasticsearch/I7um1mX4GSk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> elasticsearch+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/0a3bb3d3-c2dc-418b-bce0-5d376065fb7f%40googlegroups.com >> <https://groups.google.com/d/msgid/elasticsearch/0a3bb3d3-c2dc-418b-bce0-5d376065fb7f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/1410993466818.29294e6a%40Nodemailer > <https://groups.google.com/d/msgid/elasticsearch/1410993466818.29294e6a%40Nodemailer?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawj49An6csfQfy8Sc34jihhDCH1x-s2OETzbqSXinJeiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
