Also don't forget to make sure all of your text files have the Apache header on top and do not have other copy right messages.
.. Owen > On Apr 20, 2015, at 20:30, Adunuthula, Seshu <[email protected]> wrote: > > Any updates? > > >> On 4/8/15, 11:46 PM, "Luke Han" <[email protected]> wrote: >> >> Thanks Julian, your guide and Calcite experience are really valuable >> reference. We will try first and also draft some HOW To for further >> release. >> >> >> >> >> Best Regards! >> --------------------- >> >> Luke Han >> >> 2015-04-09 11:48 GMT+08:00 Ted Dunning <[email protected]>: >> >>> Do not be surprised if this first release takes a month to get out. >>> >>> As Julian says, it is covering issues that haven't been looked at >>> nearly as >>> carefully as the code so there will be warts. >>> >>> On Wed, Apr 8, 2015 at 12:00 PM, Adunuthula, Seshu >>> <[email protected]> >>> wrote: >>> >>>> Julian, >>>> >>>> Thanks you for all the awesome details. That should help us a lot to >>> get >>>> the first release outŠ >>>> >>>> Regards >>>> Seshu >>>> >>>>> On 4/8/15, 9:52 AM, "Julian Hyde" <[email protected]> wrote: >>>>> >>>>> A release is a distribution of intellectual property. And an Apache >>>>> release has to be approved by a vote. So complexity lies in the >>>>> packaging and the process, not in the code. >>>>> >>>>> It takes many iterations to get that right. >>>>> >>>>> I suggest that you start by trying to make a >>>>> apache-kylin-0.7.0-incubating-src.tar.gz source tarball. Make sure >>>>> that it has the necessary files, including LICENSE, NOTICE etc. It >>>>> should not contain any binary files. See the incubator site for more >>>>> detailed instructions. >>>>> >>>>> Your release manager will also need to set up keys, and get an >>> account >>>>> on Apache's nexus server. Try to make a snapshot (see >>> >>> https://github.com/apache/incubator-calcite/blob/master/doc/HOWTO.md#maki >>> n >>>>> g-a-snapshot-for-calcite-committers >>>>> for how we do it in Calcite) and you'll solve some of the challenges >>>>> that need to be solved before you make a release. >>>>> >>>>> When you have a source tarball you can start the voting process. >>>>> >>>>> Feel free to use the Calcite instructions. I think you'll follow a >>>>> very similar process for Kylin. >>>>> >>>>> Julian >>>>> >>>>>> On Mon, Apr 6, 2015 at 11:28 PM, Li Yang <[email protected]> wrote: >>>>>> We are waiting for Luke back from vacation. :-) >>>>>> >>>>>> Well, actually nothing is blocking from an apache release. It's >>> just >>>>>> some >>>>>> process to go through, which we are not familiar with yet. Luke is >>> back >>>>>> tomorrow. He can estimate a reasonable date. >>>>>> >>>>>> Previous plan was to have enough QA test internally first, however >>> for >>>>>> some >>>>>> reason, the deployment of 0.7 was delayed. As our mentor has said, >>> the >>>>>> apache release has nothing to do quality technically. And we got >>> many >>>>>> external users who have helped a lot in testing 0.7. I don't see >>> any >>>>>> blocker from this perspective. >>>>>> >>>>>> Cheers >>>>>> Yang >>>>>> >>>>>> On Tue, Apr 7, 2015 at 12:52 AM, Adunuthula, Seshu >>>>>> <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Luke/Yang, >>>>>>> >>>>>>> What does it take to make 0.7 an Apache release. All the versions >>> on >>>>>>> https://issues.apache.org/jira/browse/KYLIN/ are still in an >>>> unreleased >>>>>>> state. What is blocking us from doing an Apache Release. >>>>>>> >>>>>>> Regards >>>>>>> Seshu >>>>>>> >>>>>>> On 4/3/15, 3:06 PM, "Adunuthula, Seshu" <[email protected]> >>> wrote: >>>>>>> >>>>>>>> Folks, >>>>>>>> >>>>>>>> Can we set a date for our First Apache Release? >>>>>>>> >>>>>>>> Regards >>>>>>>> Seshu >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -------------------- >>>>>>>> Kylin >>>>>>>> >>>>>>>> Kylin is a distributed and scalable OLAP engine built on Hadoop >>> to >>>>>>> support >>>>>>>> extremely large datasets. >>>>>>>> >>>>>>>> Kylin has been incubating since 2014-11-25. >>>>>>>> >>>>>>>> Three most important issues to address in the move towards >>> graduation: >>>>>>>> >>>>>>>> 1. Make the first release from apache >
