Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D642811EFA for ; Fri, 19 Sep 2014 07:19:08 +0000 (UTC) Received: (qmail 69793 invoked by uid 500); 19 Sep 2014 07:19:08 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 69747 invoked by uid 500); 19 Sep 2014 07:19:08 -0000 Mailing-List: contact dev-help@tajo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.apache.org Delivered-To: mailing list dev@tajo.apache.org Received: (qmail 69736 invoked by uid 99); 19 Sep 2014 07:19:08 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 07:19:08 +0000 Received: from localhost (HELO mail-qc0-f173.google.com) (127.0.0.1) (smtp-auth username hyunsik, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 07:19:08 +0000 Received: by mail-qc0-f173.google.com with SMTP id i8so2654400qcq.4 for ; Fri, 19 Sep 2014 00:19:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.43.180 with SMTP id e49mr5760650qga.76.1411111147624; Fri, 19 Sep 2014 00:19:07 -0700 (PDT) Received: by 10.96.166.38 with HTTP; Fri, 19 Sep 2014 00:19:07 -0700 (PDT) In-Reply-To: References: <1410960438252.0ce1b659@Nodemailer> Date: Fri, 19 Sep 2014 00:19:07 -0700 Message-ID: Subject: Re: 0.9.0 release From: Hyunsik Choi To: "dev@tajo.apache.org" Content-Type: text/plain; charset=UTF-8 Yes, I totally agree with you guys. We need to update documentation. Actually, I expect that our documentation explains about 1/3 features of all features that Tajo provide. I've created the jira issue for 0.9.0 documentation, and I've moved the jira issue from 0.8.0 documentation issue to new jira. We also need to create more jira for new and updated documentation. Feel free to create new jira. Also, I'll reschedule some jira issues which are not critical to next version. Best regards, Hyunsik On Thu, Sep 18, 2014 at 7:20 PM, Jihoon Son wrote: > Hi guys, > I happily agree on that we are ready for the next release. > Even though some issues are not resolved, we can reschedule them for future > releases. > Here is my +1. > > Anyway, as Thanh said, we should update our documents. I think that it will > helpful for us to discuss the documentation progress. For example, each of > us can take a topic, and update documents when any issues on that topic are > resolved. > > Thanks, > Jihoon > > > 2014-09-18 9:14 GMT+09:00 Thanh Mai : > >> Hi, >> >> I hope that the release 0.9.0 will come with more detailed and complete >> documents, especially about what Tajo can do. It will also be nice if there >> will be a performance comparison between Tajo and related projects. >> >> Sincerely, >> Thanh >> >> >> >> On Wed, Sep 17, 2014 at 10:27 PM, wrote: >> >> > I glanced the change note. >> > >> > >> > >> > >> > It looks sufficient to get +1. >> > >> > >> > >> > >> > Thanks. >> > >> > On Wed, Sep 17, 2014 at 12:00 AM, Hyunsik Choi >> wrote: >> > >> > > Hi folks, >> > > Above all, I greatly apologize the miss of 0.8.1 release. For release, >> > > I had to spend not few time on refineing incomplete features and >> > > arranging some configs. I didn't do it. I'm sorry for that again. >> > > Besides, we have continued to contribute lots of codes and made Tajo >> > > much more stability. Especially, for several months, some guys have >> > > made much effort to deploy Tajo in some companies as production. I'm >> > > very happy and proud about that. Soon, we can officially post very >> > > interesting news in Apache blog. >> > > As a result, I think that now is the right time to discuss 0.9.0 >> > > release. How about your think? Currently, even though 50 issues are >> > > still scheduled to 0.9.0 in Jira, I think that most of them can be >> > > rescheduled to next version. There are only few critical issues which >> > > must be resolved in 0.9.0. >> > > If you are all agree with my suggestion, I'd like to reschedule >> > > trivial issues in 0.9.0. I'd like to start work for 0.9.0 release. >> > > Please feel free to suggest your idea. >> > > Best regards, >> > > Hyunsik >> > >>