Well, the key is to see the target.  That target is to have an artifact
such as a tar file that can be verified to be exactly what Apache
releases.  That means that it has to be cryptographically signed and
inspected in exactly the released form.  That release should also be
traceable back to a specific commit in Apache's git repo.

Early discussions can talk about the state of JIRA, or look at specific
versions of the code or whatever, but when it comes down to voting on a
release, there has to be a specific file that is voted on.

The vote, btw, is not primarily to do with whether the code functions.
That is nice, but not even required.  What the vote is all about is whether
the release meets the Apache legal requirements for licensing.  That vote
then is translated into the PMC chairs action of saying that the release is
an official Apache release.  That release action, in turn, engages the
legal machinery of the Apache license.

So....

The first step is to build the distribution artifact and sign it.  It will
probably take a number of tries to get the build system to automate the
correct construction of such a source distribution and also to get all of
the license notifications in place.



On Mon, Feb 2, 2015 at 3:33 PM, Han, Luke <[email protected]> wrote:

> Code are already in staging git, will be available in next merge to Apache
> git today or tomorroe.
> This is discussion thread would like to have all your help to prepare this
> release, to make sure new release could go with Apache process .
>
>
>
> Regards!
> Luke Han
>
>
>
>
> On Mon, Feb 2, 2015 at 8:20 AM -0800, "Ted Dunning" <[email protected]
> <mailto:[email protected]>> wrote:
>
> Where is the code at Apache?
>
> Do you have signed source artifacts to review?
>
> Or is this just preparation for review?
>
>
>
> On Mon, Feb 2, 2015 at 7:00 AM, Luke Han <[email protected]> wrote:
>
> > Hi all,
> >     After many refactor and bug fixes, we would like to release a new
> > version: v0.6.5, tag here:
> > https://github.com/KylinOLAP/Kylin/releases/tag/v0.6.5 (staging repo of
> > Apache git repo)
> >     This is latest stable version which also running on our production
> > platform, also fixed some bugs especially during deployment and cube
> > building.
> >
> >     It's first release under Apache, we would like to have everyone's
> help
> > to review and make sure there's no show stopper issue.
> >
> >     Moving forward, we are working on new generation of Kylin to support
> > both MOLAP and InvertedIndex to cover more query requirements, which will
> > be release with 0.7.x number after v0.6.5 released successfully.
> >
> >      Please feel free to leave you comments here.
> >      Thank you very much.
> >
> > Luke
> >
>

Reply via email to