You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by Aditya <ad...@apache.org> on 2014/10/07 23:32:17 UTC

Moving the master branch to next release sanpshot version

As the release vote on 0.6 is under progress on the general-incubator list
which may take a while and we have a build up of patches targeted for the
next release, I propose that we move the version to next release snapshot,
i.e. "0.7.0-incubating-SNAPSHOT".

If the release vote for 0.6.0 passes without modification, the commit
29dde769bb8c82743b9128c4cc1be4ec149ce939[1] can be tagged as "
0.6.0-incubating" release or a branch can be created of it in case
additional commits need to be applied.

I am planning to update the project version sometime later today unless I
hear an argument against it.

aditya...

Re: Moving the master branch to next release sanpshot version

Posted by Aditya <ad...@apache.org>.
I have updated the version to "0.7.0-incubating-SNAPSHOT" in the master
branch. The repository is open for merging feature/fixes targeted for next
release.

On Tue, Oct 7, 2014 at 2:32 PM, Aditya <ad...@apache.org> wrote:

> As the release vote on 0.6 is under progress on the general-incubator list
> which may take a while and we have a build up of patches targeted for the
> next release, I propose that we move the version to next release snapshot,
> i.e. "0.7.0-incubating-SNAPSHOT".
>
> If the release vote for 0.6.0 passes without modification, the commit
> 29dde769bb8c82743b9128c4cc1be4ec149ce939[1] can be tagged as "
> 0.6.0-incubating" release or a branch can be created of it in case
> additional commits need to be applied.
>
> I am planning to update the project version sometime later today unless I
> hear an argument against it.
>
> aditya...
>