Hi Nick,
That was an oversight when the release was created. As Stephan
mentioned, we have a policy that the corresponding final release
branch is read-only. Creating the tag is just a formality but of
course important. I've pushed a 'release-0.10.1' release tag. The
corresponding hash is 2e9b231
han
> mentioned, we have a policy that the corresponding final release
> branch is read-only. Creating the tag is just a formality but of
> course important. I've pushed a 'release-0.10.1' release tag. The
> corresponding hash is 2e9b231.
>
> Cheers,
> Max
>
> On Mon,
have not pushed a release tag, but have a frozen release-0.10.1-RC1
> > branch (https://github.com/apache/flink/tree/release-0.10.1-rc1)
> > A tag would be great, agree!
> >
> > Flink does in its core not depend on Hadoop. The parts that reference
> > Hadoop (HDFS filesystem
Hi Nick!
We have not pushed a release tag, but have a frozen release-0.10.1-RC1
branch (https://github.com/apache/flink/tree/release-0.10.1-rc1)
A tag would be great, agree!
Flink does in its core not depend on Hadoop. The parts that reference
Hadoop (HDFS filesystem, YARN, MapReduce function
Hi Devs,
It seems no release tag was pushed to 0.10.1. I presume this was an
oversight. Is there some place I can look to see from which sha the 0.10.1
release was built? Are the RC vote threads the only cannon in this matter?
Thanks,
Nick
it would other users.
On Friday, January 8, 2016, Stephan Ewen <se...@apache.org> wrote:
> Hi Nick!
>
> We have not pushed a release tag, but have a frozen release-0.10.1-RC1
> branch (https://github.com/apache/flink/tree/release-0.10.1-rc1)
> A tag would be great, agree!
