You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Boris Shulman <sh...@gmail.com> on 2016/05/20 22:41:40 UTC
[VOTE] Release Apache REEF 0.15.0 (rc1)
This is to call for a new vote for the source release of Apache REEF 0.15.0
(rc1).
The source tar ball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/reef/0.15.0-rc1/
The Git tag is release-0.15.0-rc1
The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
Checksums of apache-reef-0.15.0-rc1.tar.gz:
MD5: c210138b0415c316bae5e1f779ba62e2
SHA:
845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe25684054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
Release artifacts are signed with a key found in the KEYS file available
here:
https://dist.apache.org/repos/dist/release/reef/KEYS
Issues resolved in this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12334912
The vote will be open for 72 hours. Please download the release
candidate, check the hashes/signature, build it and test it, and then
please vote:
[ ] +1 Release this package as Apache REEF 0.15.0
[ ] +0 no opinion
[ ] -1 Do not release this package because ...
Thanks!
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Also do I need to create new branch for rc2? I don't think I will need to check in anything to fix it. I will probably create new tar ball on Linux. Can I just upload new tar ball and send a new vote for rc1?
Sent from my iPhone
> On May 20, 2016, at 5:38 PM, Dongjoon Hyun <do...@apache.org> wrote:
>
> As I remember correctly, the rule is keeping the same permission of Git
> repository.
>
> I can give you some example, but that might not be exhaustive.
>
> - bin/*.sh
> - dev/docker/*.sh
>
> At least the above files are used in integration tests with docker.
>
> Dongjoon.
>
>> On Friday, May 20, 2016, Boris Shulman <sh...@gmail.com> wrote:
>>
>> Dongjoon,
>>
>> Can you please let me know what files has wrong permissions and what are
>> the correct values?
>>
>> On Fri, May 20, 2016 at 4:50 PM, Julia Wang (QIUHE) <
>> Qiuhe.Wang@microsoft.com <javascript:;>> wrote:
>>
>>> I didn't encounter this issue, however, I had some issues that was not
>>> obviously visible from windows :(
>>>
>>> -----Original Message-----
>>> From: Mariia Mykhailova [mailto:mamykhai@microsoft.com <javascript:;>]
>>> Sent: Friday, May 20, 2016 4:48 PM
>>> To: dev@reef.apache.org <javascript:;>
>>> Subject: RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
>>>
>>> I did everything in release 0.13 from a Windows box and didn't have this
>>> issue (or it went unnoticed?)
>>>
>>> -Mariia
>>>
>>> -----Original Message-----
>>> From: Boris Shulman [mailto:shulmanb@gmail.com <javascript:;>]
>>> Sent: Friday, May 20, 2016 4:42 PM
>>> To: dev@reef.apache.org <javascript:;>
>>> Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
>>>
>>> Does it mean that we need to release from linux boxes? It doesn't make
>>> sense to me.
>>>
>>>> On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <shulmanb@gmail.com
>>> <javascript:;>> wrote:
>>>
>>>> Can someone with linux box check that and fix it?
>>>>
>>>> On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <shulmanb@gmail.com
>> <javascript:;>>
>>> wrote:
>>>>
>>>>> I do that from windows so I don't see how can I change that.
>>>>>
>>>>> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <dongjoon@apache.org
>> <javascript:;>>
>>>>> wrote:
>>>>>
>>>>>> Hi, thank you for all these efforts!
>>>>>>
>>>>>> But, -1. All bash script permissions are different (644) from our
>>>>>> git repository.
>>>>>>
>>>>>> For the other things,
>>>>>> - Signing: OK
>>>>>> - MD5/SHA: OK
>>>>>> - Maven clean build with tests: Passed.
>>>>>>
>>>>>> Warmly,
>>>>>> Dongjoon.
>>>>>>
>>>>>>
>>>>>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <shulmanb@gmail.com
>> <javascript:;>>
>>>>>> wrote:
>>>>>>
>>>>>>> This is to call for a new vote for the source release of Apache
>>>>>>> REEF
>>>>>> 0.15.0
>>>>>>> (rc1).
>>>>>>>
>>>>>>> The source tar ball, including signatures, digests, etc can be
>>>>>>> found
>>>>>> at:
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>>>>>> ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
>>>>>>> %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
>>>>>>> e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
>>>>>>> tEJ4xZHEiaGD4DZuvOV7HxIw%3d
>>>>>>>
>>>>>>> The Git tag is release-0.15.0-rc1
>>>>>>> The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>>>>>>>
>>>>>>>
>>>>>>> Checksums of apache-reef-0.15.0-rc1.tar.gz:
>>>>>>>
>>>>>>> MD5: c210138b0415c316bae5e1f779ba62e2
>>>>>>> SHA:
>>>>>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
>>>>>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>>>>>>>
>>>>>>> Release artifacts are signed with a key found in the KEYS file
>>>>>> available
>>>>>>> here:
>>>>>>>
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>>>>>> ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
>>>>>>> %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
>>>>>>> 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
>>>>>>> dSOzPBrFR%2bft6jpre%2fFmQ%3d
>>>>>>>
>>>>>>>
>>>>>>> Issues resolved in this release:
>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>>>>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
>>>>>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
>>>>>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
>>>>>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The vote will be open for 72 hours. Please download the release
>>>>>>> candidate, check the hashes/signature, build it and test it, and
>>>>>>> then please vote:
>>>>>>>
>>>>>>> [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
>>>>>>> opinion [ ] -1 Do not release this package because ...
>>>>>>>
>>>>>>> Thanks!
>>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
When I look on the git repo I see that permission for bin/run.sh for
example is: -rwxr-xr-x, but after I checkout on ubuntu it is -rwxrwxr-x. So
it is different even for master. Any ideas?
On Fri, May 20, 2016 at 7:56 PM, Dongjoon Hyun <do...@apache.org> wrote:
> I'm not sure about the process.
> Maybe, Markus know that. :)
> For both cases, I think you need to send new VOTE email with new MD5 and
> SHA.
>
>
>
> On Fri, May 20, 2016 at 7:50 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > Thanks.
> >
> > I will create new tarball on an ubuntu image after validating
> permissions.
> > If permissions on a git branch are fine I am not going to create RC2, but
> > we will vote on RC1 again.
> >
> > On Fri, May 20, 2016 at 7:43 PM, Dongjoon Hyun <do...@apache.org>
> > wrote:
> >
> > > Hi, Boris.
> > >
> > > You can look at our real git repository.
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> > >
> > > Also, in Windows, I think you can see the permission on file using just
> > > standard GIT commands.
> > >
> > > > $ git log -p bin/run.sh
> > > > ...
> > > > index b5bb0a4..e408adf 100755
> > >
> > > When you see the git commit logs every time, they also shows the
> > > permission, too.
> > >
> > > > $ git show HEAD~1
> > > > ...
> > > > index d561cd3..62d5372 100644
> > >
> > > I hope this is helpful for you.
> > >
> > > Sincerely,
> > > Dongjoon.
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
Oh, what I ask to Markus is about the process for next release manager. I
was wondered ASF allows that.
It's not related to your preparation. Sorry for making you confused.
By the way, I think Markus already answered that you need to cancel the
first vote and make rc2 tarball with the same branch.
For your question, `How it will be different?`. If that is about benefits
to get archives on Github, the followings are the benefits.
* New release manager don't need to have Ubuntu OS.
* New release manager can not make mistakes on archiving.
- Wrong permissions
- Including irrelevant file (this happened before.)
* We can have more simplified release manager guide.
Dongjoon.
On Sat, May 21, 2016 at 12:29 AM, Boris Shulman <sh...@gmail.com> wrote:
> That what I meant. How is it different from preparing new rc1 tarball on
> Ubuntu (which I already did)? Or rc2 tarball? And sending new vote?
>
> Sent from my iPhone
>
> > On May 21, 2016, at 12:24 AM, Dongjoon Hyun <do...@apache.org> wrote:
> >
> > Sorry, but I can not understand what you mean `I don't think they are
> > signed`.
> >
> > Of course, they are just archive files. I think what you need is to sign
> on
> > them, especially, *.tar.gz, and get *.tar.gz.asc.
> >
> > Did I miss something?
> >
> > Dongjoon.
> >
> >
> >> On Sat, May 21, 2016 at 12:12 AM, Boris Shulman <sh...@gmail.com>
> wrote:
> >>
> >> I prepared new rc2 tarball. Please let me know what to do with branch
> (if
> >> anything is needed at all as we do not change anything on the branch).
> >>
> >> Boris.
> >>
> >> On Sat, May 21, 2016 at 12:00 AM, Boris Shulman <sh...@gmail.com>
> >> wrote:
> >>
> >>> I don't think they are signed.
> >>>
> >>> On Fri, May 20, 2016 at 11:58 PM, Dongjoon Hyun <do...@apache.org>
> >>> wrote:
> >>>
> >>>> Great.
> >>>>
> >>>> By the way, I think we might have a more convenient solution.
> >>>>
> >>>> I've checked the release file which you made on Github.
> >>>>
> >>>> https://github.com/apache/reef/releases/tag/release-0.15.0-rc1
> >>>> - reef-release-0.15.0-rc1.tar.gz
> >>>> - reef-release-0.15.0-rc1.zip
> >>>>
> >>>> They looks fine. Maybe, they are generated automatically.
> >>>>
> >>>> Markus, is it possible for us to rename them and use it from now?
> >>>>
> >>>> Dongjoon.
> >>>>
> >>>>
> >>>> On Fri, May 20, 2016 at 11:32 PM, Boris Shulman <sh...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Thanks Dongjoon,
> >>>>>
> >>>>> It is fine with running umask. It basically means we have to release
> >>>> from
> >>>>> Linux/OSX to get that right, and use umask 0022 for linux.
> >>>>>
> >>>>> Markus,
> >>>>>
> >>>>> I don't need a new branch, but just a new tarball. What should I do?
> >>>> Cancel
> >>>>> the vote, prepare new tarball, upload it to RC2 and call a new vote?
> >>>> Should
> >>>>> I change the label of a branch to RC2?
> >>>>>
> >>>>> Boris.
> >>>>>
> >>>>> On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <dongjoon@apache.org
> >
> >>>>> wrote:
> >>>>>
> >>>>>>>
> >>>>>>> You can see 100755 when you run `git log -p bin/run.sh` at every
> >> OS.
> >>>>>>> (It's the real value of that file as you see in Github web
> >> viewer.)
> >>>>>>
> >>>>>> ====> Sorry. Not **Github** web viewer, our *Git repository* web
> >>>> viewer.
> >> https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> >>>>>>
> >>>>>> It's consistent with our github master.
> >>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
That what I meant. How is it different from preparing new rc1 tarball on Ubuntu (which I already did)? Or rc2 tarball? And sending new vote?
Sent from my iPhone
> On May 21, 2016, at 12:24 AM, Dongjoon Hyun <do...@apache.org> wrote:
>
> Sorry, but I can not understand what you mean `I don't think they are
> signed`.
>
> Of course, they are just archive files. I think what you need is to sign on
> them, especially, *.tar.gz, and get *.tar.gz.asc.
>
> Did I miss something?
>
> Dongjoon.
>
>
>> On Sat, May 21, 2016 at 12:12 AM, Boris Shulman <sh...@gmail.com> wrote:
>>
>> I prepared new rc2 tarball. Please let me know what to do with branch (if
>> anything is needed at all as we do not change anything on the branch).
>>
>> Boris.
>>
>> On Sat, May 21, 2016 at 12:00 AM, Boris Shulman <sh...@gmail.com>
>> wrote:
>>
>>> I don't think they are signed.
>>>
>>> On Fri, May 20, 2016 at 11:58 PM, Dongjoon Hyun <do...@apache.org>
>>> wrote:
>>>
>>>> Great.
>>>>
>>>> By the way, I think we might have a more convenient solution.
>>>>
>>>> I've checked the release file which you made on Github.
>>>>
>>>> https://github.com/apache/reef/releases/tag/release-0.15.0-rc1
>>>> - reef-release-0.15.0-rc1.tar.gz
>>>> - reef-release-0.15.0-rc1.zip
>>>>
>>>> They looks fine. Maybe, they are generated automatically.
>>>>
>>>> Markus, is it possible for us to rename them and use it from now?
>>>>
>>>> Dongjoon.
>>>>
>>>>
>>>> On Fri, May 20, 2016 at 11:32 PM, Boris Shulman <sh...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Dongjoon,
>>>>>
>>>>> It is fine with running umask. It basically means we have to release
>>>> from
>>>>> Linux/OSX to get that right, and use umask 0022 for linux.
>>>>>
>>>>> Markus,
>>>>>
>>>>> I don't need a new branch, but just a new tarball. What should I do?
>>>> Cancel
>>>>> the vote, prepare new tarball, upload it to RC2 and call a new vote?
>>>> Should
>>>>> I change the label of a branch to RC2?
>>>>>
>>>>> Boris.
>>>>>
>>>>> On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <do...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>>
>>>>>>> You can see 100755 when you run `git log -p bin/run.sh` at every
>> OS.
>>>>>>> (It's the real value of that file as you see in Github web
>> viewer.)
>>>>>>
>>>>>> ====> Sorry. Not **Github** web viewer, our *Git repository* web
>>>> viewer.
>> https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
>>>>>>
>>>>>> It's consistent with our github master.
>>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
Sorry, but I can not understand what you mean `I don't think they are
signed`.
Of course, they are just archive files. I think what you need is to sign on
them, especially, *.tar.gz, and get *.tar.gz.asc.
Did I miss something?
Dongjoon.
On Sat, May 21, 2016 at 12:12 AM, Boris Shulman <sh...@gmail.com> wrote:
> I prepared new rc2 tarball. Please let me know what to do with branch (if
> anything is needed at all as we do not change anything on the branch).
>
> Boris.
>
> On Sat, May 21, 2016 at 12:00 AM, Boris Shulman <sh...@gmail.com>
> wrote:
>
> > I don't think they are signed.
> >
> > On Fri, May 20, 2016 at 11:58 PM, Dongjoon Hyun <do...@apache.org>
> > wrote:
> >
> >> Great.
> >>
> >> By the way, I think we might have a more convenient solution.
> >>
> >> I've checked the release file which you made on Github.
> >>
> >> https://github.com/apache/reef/releases/tag/release-0.15.0-rc1
> >> - reef-release-0.15.0-rc1.tar.gz
> >> - reef-release-0.15.0-rc1.zip
> >>
> >> They looks fine. Maybe, they are generated automatically.
> >>
> >> Markus, is it possible for us to rename them and use it from now?
> >>
> >> Dongjoon.
> >>
> >>
> >> On Fri, May 20, 2016 at 11:32 PM, Boris Shulman <sh...@gmail.com>
> >> wrote:
> >>
> >> > Thanks Dongjoon,
> >> >
> >> > It is fine with running umask. It basically means we have to release
> >> from
> >> > Linux/OSX to get that right, and use umask 0022 for linux.
> >> >
> >> > Markus,
> >> >
> >> > I don't need a new branch, but just a new tarball. What should I do?
> >> Cancel
> >> > the vote, prepare new tarball, upload it to RC2 and call a new vote?
> >> Should
> >> > I change the label of a branch to RC2?
> >> >
> >> > Boris.
> >> >
> >> > On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <do...@apache.org>
> >> > wrote:
> >> >
> >> > > >
> >> > > > You can see 100755 when you run `git log -p bin/run.sh` at every
> OS.
> >> > > > (It's the real value of that file as you see in Github web
> viewer.)
> >> > > >
> >> > >
> >> > > ====> Sorry. Not **Github** web viewer, our *Git repository* web
> >> viewer.
> >> > >
> https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> >> > >
> >> > > It's consistent with our github master.
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
I prepared new rc2 tarball. Please let me know what to do with branch (if
anything is needed at all as we do not change anything on the branch).
Boris.
On Sat, May 21, 2016 at 12:00 AM, Boris Shulman <sh...@gmail.com> wrote:
> I don't think they are signed.
>
> On Fri, May 20, 2016 at 11:58 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
>
>> Great.
>>
>> By the way, I think we might have a more convenient solution.
>>
>> I've checked the release file which you made on Github.
>>
>> https://github.com/apache/reef/releases/tag/release-0.15.0-rc1
>> - reef-release-0.15.0-rc1.tar.gz
>> - reef-release-0.15.0-rc1.zip
>>
>> They looks fine. Maybe, they are generated automatically.
>>
>> Markus, is it possible for us to rename them and use it from now?
>>
>> Dongjoon.
>>
>>
>> On Fri, May 20, 2016 at 11:32 PM, Boris Shulman <sh...@gmail.com>
>> wrote:
>>
>> > Thanks Dongjoon,
>> >
>> > It is fine with running umask. It basically means we have to release
>> from
>> > Linux/OSX to get that right, and use umask 0022 for linux.
>> >
>> > Markus,
>> >
>> > I don't need a new branch, but just a new tarball. What should I do?
>> Cancel
>> > the vote, prepare new tarball, upload it to RC2 and call a new vote?
>> Should
>> > I change the label of a branch to RC2?
>> >
>> > Boris.
>> >
>> > On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <do...@apache.org>
>> > wrote:
>> >
>> > > >
>> > > > You can see 100755 when you run `git log -p bin/run.sh` at every OS.
>> > > > (It's the real value of that file as you see in Github web viewer.)
>> > > >
>> > >
>> > > ====> Sorry. Not **Github** web viewer, our *Git repository* web
>> viewer.
>> > > https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
>> > >
>> > > It's consistent with our github master.
>> > > >
>> > >
>> >
>>
>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
I don't think they are signed.
On Fri, May 20, 2016 at 11:58 PM, Dongjoon Hyun <do...@apache.org> wrote:
> Great.
>
> By the way, I think we might have a more convenient solution.
>
> I've checked the release file which you made on Github.
>
> https://github.com/apache/reef/releases/tag/release-0.15.0-rc1
> - reef-release-0.15.0-rc1.tar.gz
> - reef-release-0.15.0-rc1.zip
>
> They looks fine. Maybe, they are generated automatically.
>
> Markus, is it possible for us to rename them and use it from now?
>
> Dongjoon.
>
>
> On Fri, May 20, 2016 at 11:32 PM, Boris Shulman <sh...@gmail.com>
> wrote:
>
> > Thanks Dongjoon,
> >
> > It is fine with running umask. It basically means we have to release from
> > Linux/OSX to get that right, and use umask 0022 for linux.
> >
> > Markus,
> >
> > I don't need a new branch, but just a new tarball. What should I do?
> Cancel
> > the vote, prepare new tarball, upload it to RC2 and call a new vote?
> Should
> > I change the label of a branch to RC2?
> >
> > Boris.
> >
> > On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <do...@apache.org>
> > wrote:
> >
> > > >
> > > > You can see 100755 when you run `git log -p bin/run.sh` at every OS.
> > > > (It's the real value of that file as you see in Github web viewer.)
> > > >
> > >
> > > ====> Sorry. Not **Github** web viewer, our *Git repository* web
> viewer.
> > > https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> > >
> > > It's consistent with our github master.
> > > >
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
Great.
By the way, I think we might have a more convenient solution.
I've checked the release file which you made on Github.
https://github.com/apache/reef/releases/tag/release-0.15.0-rc1
- reef-release-0.15.0-rc1.tar.gz
- reef-release-0.15.0-rc1.zip
They looks fine. Maybe, they are generated automatically.
Markus, is it possible for us to rename them and use it from now?
Dongjoon.
On Fri, May 20, 2016 at 11:32 PM, Boris Shulman <sh...@gmail.com> wrote:
> Thanks Dongjoon,
>
> It is fine with running umask. It basically means we have to release from
> Linux/OSX to get that right, and use umask 0022 for linux.
>
> Markus,
>
> I don't need a new branch, but just a new tarball. What should I do? Cancel
> the vote, prepare new tarball, upload it to RC2 and call a new vote? Should
> I change the label of a branch to RC2?
>
> Boris.
>
> On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
>
> > >
> > > You can see 100755 when you run `git log -p bin/run.sh` at every OS.
> > > (It's the real value of that file as you see in Github web viewer.)
> > >
> >
> > ====> Sorry. Not **Github** web viewer, our *Git repository* web viewer.
> > https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> >
> > It's consistent with our github master.
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Thanks Dongjoon,
It is fine with running umask. It basically means we have to release from
Linux/OSX to get that right, and use umask 0022 for linux.
Markus,
I don't need a new branch, but just a new tarball. What should I do? Cancel
the vote, prepare new tarball, upload it to RC2 and call a new vote? Should
I change the label of a branch to RC2?
Boris.
On Fri, May 20, 2016 at 11:26 PM, Dongjoon Hyun <do...@apache.org> wrote:
> >
> > You can see 100755 when you run `git log -p bin/run.sh` at every OS.
> > (It's the real value of that file as you see in Github web viewer.)
> >
>
> ====> Sorry. Not **Github** web viewer, our *Git repository* web viewer.
> https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
>
> It's consistent with our github master.
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
>
> You can see 100755 when you run `git log -p bin/run.sh` at every OS.
> (It's the real value of that file as you see in Github web viewer.)
>
====> Sorry. Not **Github** web viewer, our *Git repository* web viewer.
https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
It's consistent with our github master.
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
Hi, All.
As Yunseong said, we are talking about the mixing effect of `umask`.
Let's think it simple.
We needs to release the tar file having the exact same content with our
master repository. That's all.
You can see 100755 when you run `git log -p bin/run.sh` at every OS.
(It's the real value of that file as you see in Github web viewer.)
It's consistent with our github master.
To Boris.
As a quick test, could you try again by running `umask 0022` and clone the
git?
I think that would solve your situation.
Dongjoon.
On Fri, May 20, 2016 at 10:04 PM, Boris Shulman <sh...@gmail.com> wrote:
> It looks like permissions depend on the OS only and different between all
> OSs (windows OSX, Ubuntu). Can we set permissions for all the .sh files in
> the python script when creating the tarball?
>
>
> Boris.
>
> On Fri, May 20, 2016 at 9:46 PM, Yunseong Lee <yu...@gmail.com>
> wrote:
>
> > Hi Boris,
> > That's quite interesting.
> >
> > In my local machine (OSX 10.11.4), the permission of the files are
> > identical between the master and 0.14.0.
> >
> > total 48
> > drwxr-xr-x 8 yunseong staff 272 May 21 13:03 .
> > drwxr-xr-x 17 yunseong staff 578 May 21 13:03 ..
> > -rwxr-xr-x 1 yunseong staff 1428 May 21 13:03 run.sh
> > -rwxr-xr-x 1 yunseong staff 1706 May 21 13:03 runmesostests.sh
> > -rw-r--r-- 1 yunseong staff 1932 May 21 13:03 runreef.ps1
> > -rw-r--r-- 1 yunseong staff 2841 May 21 13:03 runreef.psm1
> > -rw-r--r-- 1 yunseong staff 1848 May 21 13:03 runtests.ps1
> > -rwxr-xr-x 1 yunseong staff 1099 May 21 13:03 runyarntests.sh
> >
> >
> > However, on the linux machine (Ubuntu 14.04.3 LTS), the master has
> > different permission.
> >
> > total 32
> > drwxrwxr-x 2 yunseong yunseong 4096 May 21 13:35 .
> > drwxrwxr-x 7 yunseong yunseong 4096 May 21 13:35 ..
> > -rwxrwxr-x 1 yunseong yunseong 1428 May 21 13:35 run.sh
> > -rwxrwxr-x 1 yunseong yunseong 1706 May 21 13:35 runmesostests.sh
> > -rw-rw-r-- 1 yunseong yunseong 1932 May 21 13:35 runreef.ps1
> > -rw-rw-r-- 1 yunseong yunseong 2841 May 21 13:35 runreef.psm1
> > -rw-rw-r-- 1 yunseong yunseong 1848 May 21 13:35 runtests.ps1
> > -rwxrwxr-x 1 yunseong yunseong 1099 May 21 13:35 runyarntests.sh
> >
> > Maybe it's just a umask issue? I found an article:
> >
> >
> http://stackoverflow.com/questions/5519864/git-clone-produces-different-permissions-on-different-servers
> >
> > Thanks,
> > Yunseong
> >
> > On Sat, May 21, 2016 at 1:29 PM, Boris Shulman <sh...@gmail.com>
> wrote:
> >
> > > But why do you think permissions of checked out files on ubuntu are
> > > different as well? -rwxrwxr-x on the chcekout files vs -rwxr-xr-x in
> > > 0.14.0. I checked out the master.
> > >
> > > On Fri, May 20, 2016 at 9:26 PM, Yunseong Lee <yunseong.lee0@gmail.com
> >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I've checked all the previous releases, and found that only 0.13.0
> has
> > > the
> > > > different permission (-rw-rw-r--) of the scripts. As your 0.15.0 rc
> > shows
> > > > the same permission with the ones in 0.13.0, it seems that Windows
> > > somehow
> > > > changes the permission on the executable scripts.
> > > >
> > > > Thanks,
> > > > Yunseong
> > > >
> > > >
> > > >
> > > >
> > > > On Sat, May 21, 2016 at 12:53 PM, Boris Shulman <sh...@gmail.com>
> > > > wrote:
> > > >
> > > > > I looked on our previous releases and the current rc.
> > > > >
> > > > > reef 13:
> > > > > shulmanb@shulmanb-ubuntu
> > > > > :~/github/reefbin/13/apache-reef-0.13.0-incubating/bin$
> > > > > ls -al
> > > > > total 32
> > > > > drwxrwxr-x 2 shulmanb shulmanb 4096 Sep 1 2015 .
> > > > > drwxrwxr-x 6 shulmanb shulmanb 4096 Oct 6 2015 ..
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1706 Aug 18 2015 runmesostests.sh
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1932 Aug 18 2015 runreef.ps1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 2841 Aug 18 2015 runreef.psm1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1428 Sep 1 2015 run.sh
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1848 Aug 18 2015 runtests.ps1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1099 Aug 18 2015 runyarntests.sh
> > > > >
> > > > > reef 14:
> > > > > shulmanb@shulmanb-ubuntu
> :~/github/reefbin/14/apache-reef-0.14.0/bin$
> > > ls
> > > > > -al
> > > > > total 32
> > > > > drwxr-xr-x 2 shulmanb shulmanb 4096 Feb 8 07:20 .
> > > > > drwxr-xr-x 6 shulmanb shulmanb 4096 Mar 16 18:03 ..
> > > > > -rwxr-xr-x 1 shulmanb shulmanb 1706 Feb 8 07:20 runmesostests.sh
> > > > > -rw-r--r-- 1 shulmanb shulmanb 1932 Feb 8 07:20 runreef.ps1
> > > > > -rw-r--r-- 1 shulmanb shulmanb 2841 Feb 8 07:20 runreef.psm1
> > > > > -rwxr-xr-x 1 shulmanb shulmanb 1428 Feb 8 07:20 run.sh
> > > > > -rw-r--r-- 1 shulmanb shulmanb 1848 Feb 8 07:20 runtests.ps1
> > > > > -rwxr-xr-x 1 shulmanb shulmanb 1099 Feb 8 07:20 runyarntests.sh
> > > > >
> > > > >
> > > > > reef 15:
> > > > > shulmanb@shulmanb-ubuntu
> :~/github/reefbin/15/apache-reef-0.15.0/bin$
> > > ls
> > > > > -al
> > > > > total 32
> > > > > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 15:28 .
> > > > > drwxrwxr-x 6 shulmanb shulmanb 4096 May 20 15:31 ..
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1706 May 20 15:28 runmesostests.sh
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 15:28 runreef.ps1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 15:28 runreef.psm1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1428 May 20 15:28 run.sh
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 15:28 runtests.ps1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1099 May 20 15:28 runyarntests.sh
> > > > >
> > > > >
> > > > > checkout master:
> > > > >
> > > > > shulmanb@shulmanb-ubuntu:~/github/reef/bin$ ls -al
> > > > > total 32
> > > > > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 20:14 .
> > > > > drwxrwxr-x 7 shulmanb shulmanb 4096 May 20 20:21 ..
> > > > > -rwxrwxr-x 1 shulmanb shulmanb 1706 May 20 20:14 runmesostests.sh
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 20:14 runreef.ps1
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 20:14 runreef.psm1
> > > > > -rwxrwxr-x 1 shulmanb shulmanb 1428 May 20 20:14 run.sh
> > > > > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 20:14 runtests.ps1
> > > > > -rwxrwxr-x 1 shulmanb shulmanb 1099 May 20 20:14 runyarntests.sh
> > > > >
> > > > >
> > > > > So from what I see current tarball is similar to the previous
> Windows
> > > > > build, but different from reef 0.14.0. But the interesting part is
> > that
> > > > the
> > > > > master is different from reef 0.14.0 as well.
> > > > >
> > > > > Any suggestions?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, May 20, 2016 at 8:41 PM, Boris Shulman <shulmanb@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Will do that now.
> > > > > >
> > > > > > On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de>
> > > > wrote:
> > > > > >
> > > > > >> On 2016-05-20 20:37, Boris Shulman wrote:
> > > > > >>
> > > > > >>> I see. Lets first see if we have an actual problem with
> > permissions
> > > > and
> > > > > >>> how
> > > > > >>> we fix it if we have one.
> > > > > >>>
> > > > > >>
> > > > > >> I think it is an actual problem, because it means that our
> > > > instructions
> > > > > >> may not work.
> > > > > >>
> > > > > >> Have you looked at older releases on a UNIX box? Do they have
> the
> > > > right
> > > > > >> permissions? Specifically the releases done on Windows would be
> > > > > interesting.
> > > > > >>
> > > > > >> Markus
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
It looks like permissions depend on the OS only and different between all
OSs (windows OSX, Ubuntu). Can we set permissions for all the .sh files in
the python script when creating the tarball?
Boris.
On Fri, May 20, 2016 at 9:46 PM, Yunseong Lee <yu...@gmail.com>
wrote:
> Hi Boris,
> That's quite interesting.
>
> In my local machine (OSX 10.11.4), the permission of the files are
> identical between the master and 0.14.0.
>
> total 48
> drwxr-xr-x 8 yunseong staff 272 May 21 13:03 .
> drwxr-xr-x 17 yunseong staff 578 May 21 13:03 ..
> -rwxr-xr-x 1 yunseong staff 1428 May 21 13:03 run.sh
> -rwxr-xr-x 1 yunseong staff 1706 May 21 13:03 runmesostests.sh
> -rw-r--r-- 1 yunseong staff 1932 May 21 13:03 runreef.ps1
> -rw-r--r-- 1 yunseong staff 2841 May 21 13:03 runreef.psm1
> -rw-r--r-- 1 yunseong staff 1848 May 21 13:03 runtests.ps1
> -rwxr-xr-x 1 yunseong staff 1099 May 21 13:03 runyarntests.sh
>
>
> However, on the linux machine (Ubuntu 14.04.3 LTS), the master has
> different permission.
>
> total 32
> drwxrwxr-x 2 yunseong yunseong 4096 May 21 13:35 .
> drwxrwxr-x 7 yunseong yunseong 4096 May 21 13:35 ..
> -rwxrwxr-x 1 yunseong yunseong 1428 May 21 13:35 run.sh
> -rwxrwxr-x 1 yunseong yunseong 1706 May 21 13:35 runmesostests.sh
> -rw-rw-r-- 1 yunseong yunseong 1932 May 21 13:35 runreef.ps1
> -rw-rw-r-- 1 yunseong yunseong 2841 May 21 13:35 runreef.psm1
> -rw-rw-r-- 1 yunseong yunseong 1848 May 21 13:35 runtests.ps1
> -rwxrwxr-x 1 yunseong yunseong 1099 May 21 13:35 runyarntests.sh
>
> Maybe it's just a umask issue? I found an article:
>
> http://stackoverflow.com/questions/5519864/git-clone-produces-different-permissions-on-different-servers
>
> Thanks,
> Yunseong
>
> On Sat, May 21, 2016 at 1:29 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > But why do you think permissions of checked out files on ubuntu are
> > different as well? -rwxrwxr-x on the chcekout files vs -rwxr-xr-x in
> > 0.14.0. I checked out the master.
> >
> > On Fri, May 20, 2016 at 9:26 PM, Yunseong Lee <yu...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I've checked all the previous releases, and found that only 0.13.0 has
> > the
> > > different permission (-rw-rw-r--) of the scripts. As your 0.15.0 rc
> shows
> > > the same permission with the ones in 0.13.0, it seems that Windows
> > somehow
> > > changes the permission on the executable scripts.
> > >
> > > Thanks,
> > > Yunseong
> > >
> > >
> > >
> > >
> > > On Sat, May 21, 2016 at 12:53 PM, Boris Shulman <sh...@gmail.com>
> > > wrote:
> > >
> > > > I looked on our previous releases and the current rc.
> > > >
> > > > reef 13:
> > > > shulmanb@shulmanb-ubuntu
> > > > :~/github/reefbin/13/apache-reef-0.13.0-incubating/bin$
> > > > ls -al
> > > > total 32
> > > > drwxrwxr-x 2 shulmanb shulmanb 4096 Sep 1 2015 .
> > > > drwxrwxr-x 6 shulmanb shulmanb 4096 Oct 6 2015 ..
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1706 Aug 18 2015 runmesostests.sh
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1932 Aug 18 2015 runreef.ps1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 2841 Aug 18 2015 runreef.psm1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1428 Sep 1 2015 run.sh
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1848 Aug 18 2015 runtests.ps1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1099 Aug 18 2015 runyarntests.sh
> > > >
> > > > reef 14:
> > > > shulmanb@shulmanb-ubuntu:~/github/reefbin/14/apache-reef-0.14.0/bin$
> > ls
> > > > -al
> > > > total 32
> > > > drwxr-xr-x 2 shulmanb shulmanb 4096 Feb 8 07:20 .
> > > > drwxr-xr-x 6 shulmanb shulmanb 4096 Mar 16 18:03 ..
> > > > -rwxr-xr-x 1 shulmanb shulmanb 1706 Feb 8 07:20 runmesostests.sh
> > > > -rw-r--r-- 1 shulmanb shulmanb 1932 Feb 8 07:20 runreef.ps1
> > > > -rw-r--r-- 1 shulmanb shulmanb 2841 Feb 8 07:20 runreef.psm1
> > > > -rwxr-xr-x 1 shulmanb shulmanb 1428 Feb 8 07:20 run.sh
> > > > -rw-r--r-- 1 shulmanb shulmanb 1848 Feb 8 07:20 runtests.ps1
> > > > -rwxr-xr-x 1 shulmanb shulmanb 1099 Feb 8 07:20 runyarntests.sh
> > > >
> > > >
> > > > reef 15:
> > > > shulmanb@shulmanb-ubuntu:~/github/reefbin/15/apache-reef-0.15.0/bin$
> > ls
> > > > -al
> > > > total 32
> > > > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 15:28 .
> > > > drwxrwxr-x 6 shulmanb shulmanb 4096 May 20 15:31 ..
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1706 May 20 15:28 runmesostests.sh
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 15:28 runreef.ps1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 15:28 runreef.psm1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1428 May 20 15:28 run.sh
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 15:28 runtests.ps1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1099 May 20 15:28 runyarntests.sh
> > > >
> > > >
> > > > checkout master:
> > > >
> > > > shulmanb@shulmanb-ubuntu:~/github/reef/bin$ ls -al
> > > > total 32
> > > > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 20:14 .
> > > > drwxrwxr-x 7 shulmanb shulmanb 4096 May 20 20:21 ..
> > > > -rwxrwxr-x 1 shulmanb shulmanb 1706 May 20 20:14 runmesostests.sh
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 20:14 runreef.ps1
> > > > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 20:14 runreef.psm1
> > > > -rwxrwxr-x 1 shulmanb shulmanb 1428 May 20 20:14 run.sh
> > > > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 20:14 runtests.ps1
> > > > -rwxrwxr-x 1 shulmanb shulmanb 1099 May 20 20:14 runyarntests.sh
> > > >
> > > >
> > > > So from what I see current tarball is similar to the previous Windows
> > > > build, but different from reef 0.14.0. But the interesting part is
> that
> > > the
> > > > master is different from reef 0.14.0 as well.
> > > >
> > > > Any suggestions?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, May 20, 2016 at 8:41 PM, Boris Shulman <sh...@gmail.com>
> > > wrote:
> > > >
> > > > > Will do that now.
> > > > >
> > > > > On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de>
> > > wrote:
> > > > >
> > > > >> On 2016-05-20 20:37, Boris Shulman wrote:
> > > > >>
> > > > >>> I see. Lets first see if we have an actual problem with
> permissions
> > > and
> > > > >>> how
> > > > >>> we fix it if we have one.
> > > > >>>
> > > > >>
> > > > >> I think it is an actual problem, because it means that our
> > > instructions
> > > > >> may not work.
> > > > >>
> > > > >> Have you looked at older releases on a UNIX box? Do they have the
> > > right
> > > > >> permissions? Specifically the releases done on Windows would be
> > > > interesting.
> > > > >>
> > > > >> Markus
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Yunseong Lee <yu...@gmail.com>.
Hi Boris,
That's quite interesting.
In my local machine (OSX 10.11.4), the permission of the files are
identical between the master and 0.14.0.
total 48
drwxr-xr-x 8 yunseong staff 272 May 21 13:03 .
drwxr-xr-x 17 yunseong staff 578 May 21 13:03 ..
-rwxr-xr-x 1 yunseong staff 1428 May 21 13:03 run.sh
-rwxr-xr-x 1 yunseong staff 1706 May 21 13:03 runmesostests.sh
-rw-r--r-- 1 yunseong staff 1932 May 21 13:03 runreef.ps1
-rw-r--r-- 1 yunseong staff 2841 May 21 13:03 runreef.psm1
-rw-r--r-- 1 yunseong staff 1848 May 21 13:03 runtests.ps1
-rwxr-xr-x 1 yunseong staff 1099 May 21 13:03 runyarntests.sh
However, on the linux machine (Ubuntu 14.04.3 LTS), the master has
different permission.
total 32
drwxrwxr-x 2 yunseong yunseong 4096 May 21 13:35 .
drwxrwxr-x 7 yunseong yunseong 4096 May 21 13:35 ..
-rwxrwxr-x 1 yunseong yunseong 1428 May 21 13:35 run.sh
-rwxrwxr-x 1 yunseong yunseong 1706 May 21 13:35 runmesostests.sh
-rw-rw-r-- 1 yunseong yunseong 1932 May 21 13:35 runreef.ps1
-rw-rw-r-- 1 yunseong yunseong 2841 May 21 13:35 runreef.psm1
-rw-rw-r-- 1 yunseong yunseong 1848 May 21 13:35 runtests.ps1
-rwxrwxr-x 1 yunseong yunseong 1099 May 21 13:35 runyarntests.sh
Maybe it's just a umask issue? I found an article:
http://stackoverflow.com/questions/5519864/git-clone-produces-different-permissions-on-different-servers
Thanks,
Yunseong
On Sat, May 21, 2016 at 1:29 PM, Boris Shulman <sh...@gmail.com> wrote:
> But why do you think permissions of checked out files on ubuntu are
> different as well? -rwxrwxr-x on the chcekout files vs -rwxr-xr-x in
> 0.14.0. I checked out the master.
>
> On Fri, May 20, 2016 at 9:26 PM, Yunseong Lee <yu...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I've checked all the previous releases, and found that only 0.13.0 has
> the
> > different permission (-rw-rw-r--) of the scripts. As your 0.15.0 rc shows
> > the same permission with the ones in 0.13.0, it seems that Windows
> somehow
> > changes the permission on the executable scripts.
> >
> > Thanks,
> > Yunseong
> >
> >
> >
> >
> > On Sat, May 21, 2016 at 12:53 PM, Boris Shulman <sh...@gmail.com>
> > wrote:
> >
> > > I looked on our previous releases and the current rc.
> > >
> > > reef 13:
> > > shulmanb@shulmanb-ubuntu
> > > :~/github/reefbin/13/apache-reef-0.13.0-incubating/bin$
> > > ls -al
> > > total 32
> > > drwxrwxr-x 2 shulmanb shulmanb 4096 Sep 1 2015 .
> > > drwxrwxr-x 6 shulmanb shulmanb 4096 Oct 6 2015 ..
> > > -rw-rw-r-- 1 shulmanb shulmanb 1706 Aug 18 2015 runmesostests.sh
> > > -rw-rw-r-- 1 shulmanb shulmanb 1932 Aug 18 2015 runreef.ps1
> > > -rw-rw-r-- 1 shulmanb shulmanb 2841 Aug 18 2015 runreef.psm1
> > > -rw-rw-r-- 1 shulmanb shulmanb 1428 Sep 1 2015 run.sh
> > > -rw-rw-r-- 1 shulmanb shulmanb 1848 Aug 18 2015 runtests.ps1
> > > -rw-rw-r-- 1 shulmanb shulmanb 1099 Aug 18 2015 runyarntests.sh
> > >
> > > reef 14:
> > > shulmanb@shulmanb-ubuntu:~/github/reefbin/14/apache-reef-0.14.0/bin$
> ls
> > > -al
> > > total 32
> > > drwxr-xr-x 2 shulmanb shulmanb 4096 Feb 8 07:20 .
> > > drwxr-xr-x 6 shulmanb shulmanb 4096 Mar 16 18:03 ..
> > > -rwxr-xr-x 1 shulmanb shulmanb 1706 Feb 8 07:20 runmesostests.sh
> > > -rw-r--r-- 1 shulmanb shulmanb 1932 Feb 8 07:20 runreef.ps1
> > > -rw-r--r-- 1 shulmanb shulmanb 2841 Feb 8 07:20 runreef.psm1
> > > -rwxr-xr-x 1 shulmanb shulmanb 1428 Feb 8 07:20 run.sh
> > > -rw-r--r-- 1 shulmanb shulmanb 1848 Feb 8 07:20 runtests.ps1
> > > -rwxr-xr-x 1 shulmanb shulmanb 1099 Feb 8 07:20 runyarntests.sh
> > >
> > >
> > > reef 15:
> > > shulmanb@shulmanb-ubuntu:~/github/reefbin/15/apache-reef-0.15.0/bin$
> ls
> > > -al
> > > total 32
> > > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 15:28 .
> > > drwxrwxr-x 6 shulmanb shulmanb 4096 May 20 15:31 ..
> > > -rw-rw-r-- 1 shulmanb shulmanb 1706 May 20 15:28 runmesostests.sh
> > > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 15:28 runreef.ps1
> > > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 15:28 runreef.psm1
> > > -rw-rw-r-- 1 shulmanb shulmanb 1428 May 20 15:28 run.sh
> > > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 15:28 runtests.ps1
> > > -rw-rw-r-- 1 shulmanb shulmanb 1099 May 20 15:28 runyarntests.sh
> > >
> > >
> > > checkout master:
> > >
> > > shulmanb@shulmanb-ubuntu:~/github/reef/bin$ ls -al
> > > total 32
> > > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 20:14 .
> > > drwxrwxr-x 7 shulmanb shulmanb 4096 May 20 20:21 ..
> > > -rwxrwxr-x 1 shulmanb shulmanb 1706 May 20 20:14 runmesostests.sh
> > > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 20:14 runreef.ps1
> > > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 20:14 runreef.psm1
> > > -rwxrwxr-x 1 shulmanb shulmanb 1428 May 20 20:14 run.sh
> > > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 20:14 runtests.ps1
> > > -rwxrwxr-x 1 shulmanb shulmanb 1099 May 20 20:14 runyarntests.sh
> > >
> > >
> > > So from what I see current tarball is similar to the previous Windows
> > > build, but different from reef 0.14.0. But the interesting part is that
> > the
> > > master is different from reef 0.14.0 as well.
> > >
> > > Any suggestions?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Fri, May 20, 2016 at 8:41 PM, Boris Shulman <sh...@gmail.com>
> > wrote:
> > >
> > > > Will do that now.
> > > >
> > > > On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de>
> > wrote:
> > > >
> > > >> On 2016-05-20 20:37, Boris Shulman wrote:
> > > >>
> > > >>> I see. Lets first see if we have an actual problem with permissions
> > and
> > > >>> how
> > > >>> we fix it if we have one.
> > > >>>
> > > >>
> > > >> I think it is an actual problem, because it means that our
> > instructions
> > > >> may not work.
> > > >>
> > > >> Have you looked at older releases on a UNIX box? Do they have the
> > right
> > > >> permissions? Specifically the releases done on Windows would be
> > > interesting.
> > > >>
> > > >> Markus
> > > >>
> > > >
> > > >
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
But why do you think permissions of checked out files on ubuntu are
different as well? -rwxrwxr-x on the chcekout files vs -rwxr-xr-x in
0.14.0. I checked out the master.
On Fri, May 20, 2016 at 9:26 PM, Yunseong Lee <yu...@gmail.com>
wrote:
> Hi,
>
> I've checked all the previous releases, and found that only 0.13.0 has the
> different permission (-rw-rw-r--) of the scripts. As your 0.15.0 rc shows
> the same permission with the ones in 0.13.0, it seems that Windows somehow
> changes the permission on the executable scripts.
>
> Thanks,
> Yunseong
>
>
>
>
> On Sat, May 21, 2016 at 12:53 PM, Boris Shulman <sh...@gmail.com>
> wrote:
>
> > I looked on our previous releases and the current rc.
> >
> > reef 13:
> > shulmanb@shulmanb-ubuntu
> > :~/github/reefbin/13/apache-reef-0.13.0-incubating/bin$
> > ls -al
> > total 32
> > drwxrwxr-x 2 shulmanb shulmanb 4096 Sep 1 2015 .
> > drwxrwxr-x 6 shulmanb shulmanb 4096 Oct 6 2015 ..
> > -rw-rw-r-- 1 shulmanb shulmanb 1706 Aug 18 2015 runmesostests.sh
> > -rw-rw-r-- 1 shulmanb shulmanb 1932 Aug 18 2015 runreef.ps1
> > -rw-rw-r-- 1 shulmanb shulmanb 2841 Aug 18 2015 runreef.psm1
> > -rw-rw-r-- 1 shulmanb shulmanb 1428 Sep 1 2015 run.sh
> > -rw-rw-r-- 1 shulmanb shulmanb 1848 Aug 18 2015 runtests.ps1
> > -rw-rw-r-- 1 shulmanb shulmanb 1099 Aug 18 2015 runyarntests.sh
> >
> > reef 14:
> > shulmanb@shulmanb-ubuntu:~/github/reefbin/14/apache-reef-0.14.0/bin$ ls
> > -al
> > total 32
> > drwxr-xr-x 2 shulmanb shulmanb 4096 Feb 8 07:20 .
> > drwxr-xr-x 6 shulmanb shulmanb 4096 Mar 16 18:03 ..
> > -rwxr-xr-x 1 shulmanb shulmanb 1706 Feb 8 07:20 runmesostests.sh
> > -rw-r--r-- 1 shulmanb shulmanb 1932 Feb 8 07:20 runreef.ps1
> > -rw-r--r-- 1 shulmanb shulmanb 2841 Feb 8 07:20 runreef.psm1
> > -rwxr-xr-x 1 shulmanb shulmanb 1428 Feb 8 07:20 run.sh
> > -rw-r--r-- 1 shulmanb shulmanb 1848 Feb 8 07:20 runtests.ps1
> > -rwxr-xr-x 1 shulmanb shulmanb 1099 Feb 8 07:20 runyarntests.sh
> >
> >
> > reef 15:
> > shulmanb@shulmanb-ubuntu:~/github/reefbin/15/apache-reef-0.15.0/bin$ ls
> > -al
> > total 32
> > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 15:28 .
> > drwxrwxr-x 6 shulmanb shulmanb 4096 May 20 15:31 ..
> > -rw-rw-r-- 1 shulmanb shulmanb 1706 May 20 15:28 runmesostests.sh
> > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 15:28 runreef.ps1
> > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 15:28 runreef.psm1
> > -rw-rw-r-- 1 shulmanb shulmanb 1428 May 20 15:28 run.sh
> > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 15:28 runtests.ps1
> > -rw-rw-r-- 1 shulmanb shulmanb 1099 May 20 15:28 runyarntests.sh
> >
> >
> > checkout master:
> >
> > shulmanb@shulmanb-ubuntu:~/github/reef/bin$ ls -al
> > total 32
> > drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 20:14 .
> > drwxrwxr-x 7 shulmanb shulmanb 4096 May 20 20:21 ..
> > -rwxrwxr-x 1 shulmanb shulmanb 1706 May 20 20:14 runmesostests.sh
> > -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 20:14 runreef.ps1
> > -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 20:14 runreef.psm1
> > -rwxrwxr-x 1 shulmanb shulmanb 1428 May 20 20:14 run.sh
> > -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 20:14 runtests.ps1
> > -rwxrwxr-x 1 shulmanb shulmanb 1099 May 20 20:14 runyarntests.sh
> >
> >
> > So from what I see current tarball is similar to the previous Windows
> > build, but different from reef 0.14.0. But the interesting part is that
> the
> > master is different from reef 0.14.0 as well.
> >
> > Any suggestions?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Fri, May 20, 2016 at 8:41 PM, Boris Shulman <sh...@gmail.com>
> wrote:
> >
> > > Will do that now.
> > >
> > > On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de>
> wrote:
> > >
> > >> On 2016-05-20 20:37, Boris Shulman wrote:
> > >>
> > >>> I see. Lets first see if we have an actual problem with permissions
> and
> > >>> how
> > >>> we fix it if we have one.
> > >>>
> > >>
> > >> I think it is an actual problem, because it means that our
> instructions
> > >> may not work.
> > >>
> > >> Have you looked at older releases on a UNIX box? Do they have the
> right
> > >> permissions? Specifically the releases done on Windows would be
> > interesting.
> > >>
> > >> Markus
> > >>
> > >
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Yunseong Lee <yu...@gmail.com>.
Hi,
I've checked all the previous releases, and found that only 0.13.0 has the
different permission (-rw-rw-r--) of the scripts. As your 0.15.0 rc shows
the same permission with the ones in 0.13.0, it seems that Windows somehow
changes the permission on the executable scripts.
Thanks,
Yunseong
On Sat, May 21, 2016 at 12:53 PM, Boris Shulman <sh...@gmail.com> wrote:
> I looked on our previous releases and the current rc.
>
> reef 13:
> shulmanb@shulmanb-ubuntu
> :~/github/reefbin/13/apache-reef-0.13.0-incubating/bin$
> ls -al
> total 32
> drwxrwxr-x 2 shulmanb shulmanb 4096 Sep 1 2015 .
> drwxrwxr-x 6 shulmanb shulmanb 4096 Oct 6 2015 ..
> -rw-rw-r-- 1 shulmanb shulmanb 1706 Aug 18 2015 runmesostests.sh
> -rw-rw-r-- 1 shulmanb shulmanb 1932 Aug 18 2015 runreef.ps1
> -rw-rw-r-- 1 shulmanb shulmanb 2841 Aug 18 2015 runreef.psm1
> -rw-rw-r-- 1 shulmanb shulmanb 1428 Sep 1 2015 run.sh
> -rw-rw-r-- 1 shulmanb shulmanb 1848 Aug 18 2015 runtests.ps1
> -rw-rw-r-- 1 shulmanb shulmanb 1099 Aug 18 2015 runyarntests.sh
>
> reef 14:
> shulmanb@shulmanb-ubuntu:~/github/reefbin/14/apache-reef-0.14.0/bin$ ls
> -al
> total 32
> drwxr-xr-x 2 shulmanb shulmanb 4096 Feb 8 07:20 .
> drwxr-xr-x 6 shulmanb shulmanb 4096 Mar 16 18:03 ..
> -rwxr-xr-x 1 shulmanb shulmanb 1706 Feb 8 07:20 runmesostests.sh
> -rw-r--r-- 1 shulmanb shulmanb 1932 Feb 8 07:20 runreef.ps1
> -rw-r--r-- 1 shulmanb shulmanb 2841 Feb 8 07:20 runreef.psm1
> -rwxr-xr-x 1 shulmanb shulmanb 1428 Feb 8 07:20 run.sh
> -rw-r--r-- 1 shulmanb shulmanb 1848 Feb 8 07:20 runtests.ps1
> -rwxr-xr-x 1 shulmanb shulmanb 1099 Feb 8 07:20 runyarntests.sh
>
>
> reef 15:
> shulmanb@shulmanb-ubuntu:~/github/reefbin/15/apache-reef-0.15.0/bin$ ls
> -al
> total 32
> drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 15:28 .
> drwxrwxr-x 6 shulmanb shulmanb 4096 May 20 15:31 ..
> -rw-rw-r-- 1 shulmanb shulmanb 1706 May 20 15:28 runmesostests.sh
> -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 15:28 runreef.ps1
> -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 15:28 runreef.psm1
> -rw-rw-r-- 1 shulmanb shulmanb 1428 May 20 15:28 run.sh
> -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 15:28 runtests.ps1
> -rw-rw-r-- 1 shulmanb shulmanb 1099 May 20 15:28 runyarntests.sh
>
>
> checkout master:
>
> shulmanb@shulmanb-ubuntu:~/github/reef/bin$ ls -al
> total 32
> drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 20:14 .
> drwxrwxr-x 7 shulmanb shulmanb 4096 May 20 20:21 ..
> -rwxrwxr-x 1 shulmanb shulmanb 1706 May 20 20:14 runmesostests.sh
> -rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 20:14 runreef.ps1
> -rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 20:14 runreef.psm1
> -rwxrwxr-x 1 shulmanb shulmanb 1428 May 20 20:14 run.sh
> -rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 20:14 runtests.ps1
> -rwxrwxr-x 1 shulmanb shulmanb 1099 May 20 20:14 runyarntests.sh
>
>
> So from what I see current tarball is similar to the previous Windows
> build, but different from reef 0.14.0. But the interesting part is that the
> master is different from reef 0.14.0 as well.
>
> Any suggestions?
>
>
>
>
>
>
>
>
>
> On Fri, May 20, 2016 at 8:41 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > Will do that now.
> >
> > On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de> wrote:
> >
> >> On 2016-05-20 20:37, Boris Shulman wrote:
> >>
> >>> I see. Lets first see if we have an actual problem with permissions and
> >>> how
> >>> we fix it if we have one.
> >>>
> >>
> >> I think it is an actual problem, because it means that our instructions
> >> may not work.
> >>
> >> Have you looked at older releases on a UNIX box? Do they have the right
> >> permissions? Specifically the releases done on Windows would be
> interesting.
> >>
> >> Markus
> >>
> >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
I looked on our previous releases and the current rc.
reef 13:
shulmanb@shulmanb-ubuntu:~/github/reefbin/13/apache-reef-0.13.0-incubating/bin$
ls -al
total 32
drwxrwxr-x 2 shulmanb shulmanb 4096 Sep 1 2015 .
drwxrwxr-x 6 shulmanb shulmanb 4096 Oct 6 2015 ..
-rw-rw-r-- 1 shulmanb shulmanb 1706 Aug 18 2015 runmesostests.sh
-rw-rw-r-- 1 shulmanb shulmanb 1932 Aug 18 2015 runreef.ps1
-rw-rw-r-- 1 shulmanb shulmanb 2841 Aug 18 2015 runreef.psm1
-rw-rw-r-- 1 shulmanb shulmanb 1428 Sep 1 2015 run.sh
-rw-rw-r-- 1 shulmanb shulmanb 1848 Aug 18 2015 runtests.ps1
-rw-rw-r-- 1 shulmanb shulmanb 1099 Aug 18 2015 runyarntests.sh
reef 14:
shulmanb@shulmanb-ubuntu:~/github/reefbin/14/apache-reef-0.14.0/bin$ ls -al
total 32
drwxr-xr-x 2 shulmanb shulmanb 4096 Feb 8 07:20 .
drwxr-xr-x 6 shulmanb shulmanb 4096 Mar 16 18:03 ..
-rwxr-xr-x 1 shulmanb shulmanb 1706 Feb 8 07:20 runmesostests.sh
-rw-r--r-- 1 shulmanb shulmanb 1932 Feb 8 07:20 runreef.ps1
-rw-r--r-- 1 shulmanb shulmanb 2841 Feb 8 07:20 runreef.psm1
-rwxr-xr-x 1 shulmanb shulmanb 1428 Feb 8 07:20 run.sh
-rw-r--r-- 1 shulmanb shulmanb 1848 Feb 8 07:20 runtests.ps1
-rwxr-xr-x 1 shulmanb shulmanb 1099 Feb 8 07:20 runyarntests.sh
reef 15:
shulmanb@shulmanb-ubuntu:~/github/reefbin/15/apache-reef-0.15.0/bin$ ls -al
total 32
drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 15:28 .
drwxrwxr-x 6 shulmanb shulmanb 4096 May 20 15:31 ..
-rw-rw-r-- 1 shulmanb shulmanb 1706 May 20 15:28 runmesostests.sh
-rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 15:28 runreef.ps1
-rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 15:28 runreef.psm1
-rw-rw-r-- 1 shulmanb shulmanb 1428 May 20 15:28 run.sh
-rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 15:28 runtests.ps1
-rw-rw-r-- 1 shulmanb shulmanb 1099 May 20 15:28 runyarntests.sh
checkout master:
shulmanb@shulmanb-ubuntu:~/github/reef/bin$ ls -al
total 32
drwxrwxr-x 2 shulmanb shulmanb 4096 May 20 20:14 .
drwxrwxr-x 7 shulmanb shulmanb 4096 May 20 20:21 ..
-rwxrwxr-x 1 shulmanb shulmanb 1706 May 20 20:14 runmesostests.sh
-rw-rw-r-- 1 shulmanb shulmanb 1932 May 20 20:14 runreef.ps1
-rw-rw-r-- 1 shulmanb shulmanb 2841 May 20 20:14 runreef.psm1
-rwxrwxr-x 1 shulmanb shulmanb 1428 May 20 20:14 run.sh
-rw-rw-r-- 1 shulmanb shulmanb 1848 May 20 20:14 runtests.ps1
-rwxrwxr-x 1 shulmanb shulmanb 1099 May 20 20:14 runyarntests.sh
So from what I see current tarball is similar to the previous Windows
build, but different from reef 0.14.0. But the interesting part is that the
master is different from reef 0.14.0 as well.
Any suggestions?
On Fri, May 20, 2016 at 8:41 PM, Boris Shulman <sh...@gmail.com> wrote:
> Will do that now.
>
> On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de> wrote:
>
>> On 2016-05-20 20:37, Boris Shulman wrote:
>>
>>> I see. Lets first see if we have an actual problem with permissions and
>>> how
>>> we fix it if we have one.
>>>
>>
>> I think it is an actual problem, because it means that our instructions
>> may not work.
>>
>> Have you looked at older releases on a UNIX box? Do they have the right
>> permissions? Specifically the releases done on Windows would be interesting.
>>
>> Markus
>>
>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Will do that now.
On Fri, May 20, 2016 at 8:40 PM, Markus Weimer <ma...@weimo.de> wrote:
> On 2016-05-20 20:37, Boris Shulman wrote:
>
>> I see. Lets first see if we have an actual problem with permissions and
>> how
>> we fix it if we have one.
>>
>
> I think it is an actual problem, because it means that our instructions
> may not work.
>
> Have you looked at older releases on a UNIX box? Do they have the right
> permissions? Specifically the releases done on Windows would be interesting.
>
> Markus
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Markus Weimer <ma...@weimo.de>.
On 2016-05-20 20:37, Boris Shulman wrote:
> I see. Lets first see if we have an actual problem with permissions and how
> we fix it if we have one.
I think it is an actual problem, because it means that our instructions
may not work.
Have you looked at older releases on a UNIX box? Do they have the right
permissions? Specifically the releases done on Windows would be interesting.
Markus
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
I see. Lets first see if we have an actual problem with permissions and how
we fix it if we have one. I tried getting the master on ubuntu and after
checking it out I see that permissions are different from what I see on the
repository. So I am not sure what I need to do here.
If I need an RC2 what is the right way to create RC2 branch (we are not
changing anything really)?
On Fri, May 20, 2016 at 8:33 PM, Markus Weimer <ma...@weimo.de> wrote:
> On 2016-05-20 19:57, Boris Shulman wrote:
>
>> Markus, WDYT?
>>
>
> This vote thread needs to be cancelled. And yes, we need an RC2. The next
> vote pertains to a specific release artifact with specific content, as
> summarized by the hashes. We cannot have two different RC1s flying around
> with different hashes.
>
> Markus
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Markus Weimer <ma...@weimo.de>.
On 2016-05-20 19:57, Boris Shulman wrote:
> Markus, WDYT?
This vote thread needs to be cancelled. And yes, we need an RC2. The
next vote pertains to a specific release artifact with specific content,
as summarized by the hashes. We cannot have two different RC1s flying
around with different hashes.
Markus
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Markus, WDYT?
On Fri, May 20, 2016 at 7:56 PM, Dongjoon Hyun <do...@apache.org> wrote:
> I'm not sure about the process.
> Maybe, Markus know that. :)
> For both cases, I think you need to send new VOTE email with new MD5 and
> SHA.
>
>
>
> On Fri, May 20, 2016 at 7:50 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > Thanks.
> >
> > I will create new tarball on an ubuntu image after validating
> permissions.
> > If permissions on a git branch are fine I am not going to create RC2, but
> > we will vote on RC1 again.
> >
> > On Fri, May 20, 2016 at 7:43 PM, Dongjoon Hyun <do...@apache.org>
> > wrote:
> >
> > > Hi, Boris.
> > >
> > > You can look at our real git repository.
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> > >
> > > Also, in Windows, I think you can see the permission on file using just
> > > standard GIT commands.
> > >
> > > > $ git log -p bin/run.sh
> > > > ...
> > > > index b5bb0a4..e408adf 100755
> > >
> > > When you see the git commit logs every time, they also shows the
> > > permission, too.
> > >
> > > > $ git show HEAD~1
> > > > ...
> > > > index d561cd3..62d5372 100644
> > >
> > > I hope this is helpful for you.
> > >
> > > Sincerely,
> > > Dongjoon.
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
I'm not sure about the process.
Maybe, Markus know that. :)
For both cases, I think you need to send new VOTE email with new MD5 and
SHA.
On Fri, May 20, 2016 at 7:50 PM, Boris Shulman <sh...@gmail.com> wrote:
> Thanks.
>
> I will create new tarball on an ubuntu image after validating permissions.
> If permissions on a git branch are fine I am not going to create RC2, but
> we will vote on RC1 again.
>
> On Fri, May 20, 2016 at 7:43 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
>
> > Hi, Boris.
> >
> > You can look at our real git repository.
> >
> > https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
> >
> > Also, in Windows, I think you can see the permission on file using just
> > standard GIT commands.
> >
> > > $ git log -p bin/run.sh
> > > ...
> > > index b5bb0a4..e408adf 100755
> >
> > When you see the git commit logs every time, they also shows the
> > permission, too.
> >
> > > $ git show HEAD~1
> > > ...
> > > index d561cd3..62d5372 100644
> >
> > I hope this is helpful for you.
> >
> > Sincerely,
> > Dongjoon.
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Thanks.
I will create new tarball on an ubuntu image after validating permissions.
If permissions on a git branch are fine I am not going to create RC2, but
we will vote on RC1 again.
On Fri, May 20, 2016 at 7:43 PM, Dongjoon Hyun <do...@apache.org> wrote:
> Hi, Boris.
>
> You can look at our real git repository.
>
> https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
>
> Also, in Windows, I think you can see the permission on file using just
> standard GIT commands.
>
> > $ git log -p bin/run.sh
> > ...
> > index b5bb0a4..e408adf 100755
>
> When you see the git commit logs every time, they also shows the
> permission, too.
>
> > $ git show HEAD~1
> > ...
> > index d561cd3..62d5372 100644
>
> I hope this is helpful for you.
>
> Sincerely,
> Dongjoon.
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
Hi, Boris.
You can look at our real git repository.
https://git-wip-us.apache.org/repos/asf?p=reef.git;a=tree
Also, in Windows, I think you can see the permission on file using just
standard GIT commands.
> $ git log -p bin/run.sh
> ...
> index b5bb0a4..e408adf 100755
When you see the git commit logs every time, they also shows the
permission, too.
> $ git show HEAD~1
> ...
> index d561cd3..62d5372 100644
I hope this is helpful for you.
Sincerely,
Dongjoon.
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Can u please check if permissions in the branch are good?
Sent from my iPhone
> On May 20, 2016, at 5:38 PM, Dongjoon Hyun <do...@apache.org> wrote:
>
> As I remember correctly, the rule is keeping the same permission of Git
> repository.
>
> I can give you some example, but that might not be exhaustive.
>
> - bin/*.sh
> - dev/docker/*.sh
>
> At least the above files are used in integration tests with docker.
>
> Dongjoon.
>
>> On Friday, May 20, 2016, Boris Shulman <sh...@gmail.com> wrote:
>>
>> Dongjoon,
>>
>> Can you please let me know what files has wrong permissions and what are
>> the correct values?
>>
>> On Fri, May 20, 2016 at 4:50 PM, Julia Wang (QIUHE) <
>> Qiuhe.Wang@microsoft.com <javascript:;>> wrote:
>>
>>> I didn't encounter this issue, however, I had some issues that was not
>>> obviously visible from windows :(
>>>
>>> -----Original Message-----
>>> From: Mariia Mykhailova [mailto:mamykhai@microsoft.com <javascript:;>]
>>> Sent: Friday, May 20, 2016 4:48 PM
>>> To: dev@reef.apache.org <javascript:;>
>>> Subject: RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
>>>
>>> I did everything in release 0.13 from a Windows box and didn't have this
>>> issue (or it went unnoticed?)
>>>
>>> -Mariia
>>>
>>> -----Original Message-----
>>> From: Boris Shulman [mailto:shulmanb@gmail.com <javascript:;>]
>>> Sent: Friday, May 20, 2016 4:42 PM
>>> To: dev@reef.apache.org <javascript:;>
>>> Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
>>>
>>> Does it mean that we need to release from linux boxes? It doesn't make
>>> sense to me.
>>>
>>>> On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <shulmanb@gmail.com
>>> <javascript:;>> wrote:
>>>
>>>> Can someone with linux box check that and fix it?
>>>>
>>>> On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <shulmanb@gmail.com
>> <javascript:;>>
>>> wrote:
>>>>
>>>>> I do that from windows so I don't see how can I change that.
>>>>>
>>>>> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <dongjoon@apache.org
>> <javascript:;>>
>>>>> wrote:
>>>>>
>>>>>> Hi, thank you for all these efforts!
>>>>>>
>>>>>> But, -1. All bash script permissions are different (644) from our
>>>>>> git repository.
>>>>>>
>>>>>> For the other things,
>>>>>> - Signing: OK
>>>>>> - MD5/SHA: OK
>>>>>> - Maven clean build with tests: Passed.
>>>>>>
>>>>>> Warmly,
>>>>>> Dongjoon.
>>>>>>
>>>>>>
>>>>>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <shulmanb@gmail.com
>> <javascript:;>>
>>>>>> wrote:
>>>>>>
>>>>>>> This is to call for a new vote for the source release of Apache
>>>>>>> REEF
>>>>>> 0.15.0
>>>>>>> (rc1).
>>>>>>>
>>>>>>> The source tar ball, including signatures, digests, etc can be
>>>>>>> found
>>>>>> at:
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>>>>>> ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
>>>>>>> %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
>>>>>>> e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
>>>>>>> tEJ4xZHEiaGD4DZuvOV7HxIw%3d
>>>>>>>
>>>>>>> The Git tag is release-0.15.0-rc1
>>>>>>> The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>>>>>>>
>>>>>>>
>>>>>>> Checksums of apache-reef-0.15.0-rc1.tar.gz:
>>>>>>>
>>>>>>> MD5: c210138b0415c316bae5e1f779ba62e2
>>>>>>> SHA:
>>>>>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
>>>>>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>>>>>>>
>>>>>>> Release artifacts are signed with a key found in the KEYS file
>>>>>> available
>>>>>>> here:
>>>>>>>
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>>>>>> ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
>>>>>>> %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
>>>>>>> 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
>>>>>>> dSOzPBrFR%2bft6jpre%2fFmQ%3d
>>>>>>>
>>>>>>>
>>>>>>> Issues resolved in this release:
>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>>>>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
>>>>>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
>>>>>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
>>>>>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The vote will be open for 72 hours. Please download the release
>>>>>>> candidate, check the hashes/signature, build it and test it, and
>>>>>>> then please vote:
>>>>>>>
>>>>>>> [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
>>>>>>> opinion [ ] -1 Do not release this package because ...
>>>>>>>
>>>>>>> Thanks!
>>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Permissions were probably changed by Windows as I never touched these files. How can I see the permissions of the git repository?
Sent from my iPhone
> On May 20, 2016, at 5:38 PM, Dongjoon Hyun <do...@apache.org> wrote:
>
> As I remember correctly, the rule is keeping the same permission of Git
> repository.
>
> I can give you some example, but that might not be exhaustive.
>
> - bin/*.sh
> - dev/docker/*.sh
>
> At least the above files are used in integration tests with docker.
>
> Dongjoon.
>
>> On Friday, May 20, 2016, Boris Shulman <sh...@gmail.com> wrote:
>>
>> Dongjoon,
>>
>> Can you please let me know what files has wrong permissions and what are
>> the correct values?
>>
>> On Fri, May 20, 2016 at 4:50 PM, Julia Wang (QIUHE) <
>> Qiuhe.Wang@microsoft.com <javascript:;>> wrote:
>>
>>> I didn't encounter this issue, however, I had some issues that was not
>>> obviously visible from windows :(
>>>
>>> -----Original Message-----
>>> From: Mariia Mykhailova [mailto:mamykhai@microsoft.com <javascript:;>]
>>> Sent: Friday, May 20, 2016 4:48 PM
>>> To: dev@reef.apache.org <javascript:;>
>>> Subject: RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
>>>
>>> I did everything in release 0.13 from a Windows box and didn't have this
>>> issue (or it went unnoticed?)
>>>
>>> -Mariia
>>>
>>> -----Original Message-----
>>> From: Boris Shulman [mailto:shulmanb@gmail.com <javascript:;>]
>>> Sent: Friday, May 20, 2016 4:42 PM
>>> To: dev@reef.apache.org <javascript:;>
>>> Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
>>>
>>> Does it mean that we need to release from linux boxes? It doesn't make
>>> sense to me.
>>>
>>>> On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <shulmanb@gmail.com
>>> <javascript:;>> wrote:
>>>
>>>> Can someone with linux box check that and fix it?
>>>>
>>>> On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <shulmanb@gmail.com
>> <javascript:;>>
>>> wrote:
>>>>
>>>>> I do that from windows so I don't see how can I change that.
>>>>>
>>>>> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <dongjoon@apache.org
>> <javascript:;>>
>>>>> wrote:
>>>>>
>>>>>> Hi, thank you for all these efforts!
>>>>>>
>>>>>> But, -1. All bash script permissions are different (644) from our
>>>>>> git repository.
>>>>>>
>>>>>> For the other things,
>>>>>> - Signing: OK
>>>>>> - MD5/SHA: OK
>>>>>> - Maven clean build with tests: Passed.
>>>>>>
>>>>>> Warmly,
>>>>>> Dongjoon.
>>>>>>
>>>>>>
>>>>>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <shulmanb@gmail.com
>> <javascript:;>>
>>>>>> wrote:
>>>>>>
>>>>>>> This is to call for a new vote for the source release of Apache
>>>>>>> REEF
>>>>>> 0.15.0
>>>>>>> (rc1).
>>>>>>>
>>>>>>> The source tar ball, including signatures, digests, etc can be
>>>>>>> found
>>>>>> at:
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>>>>>> ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
>>>>>>> %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
>>>>>>> e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
>>>>>>> tEJ4xZHEiaGD4DZuvOV7HxIw%3d
>>>>>>>
>>>>>>> The Git tag is release-0.15.0-rc1
>>>>>>> The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>>>>>>>
>>>>>>>
>>>>>>> Checksums of apache-reef-0.15.0-rc1.tar.gz:
>>>>>>>
>>>>>>> MD5: c210138b0415c316bae5e1f779ba62e2
>>>>>>> SHA:
>>>>>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
>>>>>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>>>>>>>
>>>>>>> Release artifacts are signed with a key found in the KEYS file
>>>>>> available
>>>>>>> here:
>>>>>>>
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>>>>>> ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
>>>>>>> %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
>>>>>>> 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
>>>>>>> dSOzPBrFR%2bft6jpre%2fFmQ%3d
>>>>>>>
>>>>>>>
>>>>>>> Issues resolved in this release:
>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>>>>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
>>>>>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
>>>>>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
>>>>>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The vote will be open for 72 hours. Please download the release
>>>>>>> candidate, check the hashes/signature, build it and test it, and
>>>>>>> then please vote:
>>>>>>>
>>>>>>> [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
>>>>>>> opinion [ ] -1 Do not release this package because ...
>>>>>>>
>>>>>>> Thanks!
>>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
As I remember correctly, the rule is keeping the same permission of Git
repository.
I can give you some example, but that might not be exhaustive.
- bin/*.sh
- dev/docker/*.sh
At least the above files are used in integration tests with docker.
Dongjoon.
On Friday, May 20, 2016, Boris Shulman <sh...@gmail.com> wrote:
> Dongjoon,
>
> Can you please let me know what files has wrong permissions and what are
> the correct values?
>
> On Fri, May 20, 2016 at 4:50 PM, Julia Wang (QIUHE) <
> Qiuhe.Wang@microsoft.com <javascript:;>> wrote:
>
> > I didn't encounter this issue, however, I had some issues that was not
> > obviously visible from windows :(
> >
> > -----Original Message-----
> > From: Mariia Mykhailova [mailto:mamykhai@microsoft.com <javascript:;>]
> > Sent: Friday, May 20, 2016 4:48 PM
> > To: dev@reef.apache.org <javascript:;>
> > Subject: RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
> >
> > I did everything in release 0.13 from a Windows box and didn't have this
> > issue (or it went unnoticed?)
> >
> > -Mariia
> >
> > -----Original Message-----
> > From: Boris Shulman [mailto:shulmanb@gmail.com <javascript:;>]
> > Sent: Friday, May 20, 2016 4:42 PM
> > To: dev@reef.apache.org <javascript:;>
> > Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
> >
> > Does it mean that we need to release from linux boxes? It doesn't make
> > sense to me.
> >
> > On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <shulmanb@gmail.com
> <javascript:;>> wrote:
> >
> > > Can someone with linux box check that and fix it?
> > >
> > > On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <shulmanb@gmail.com
> <javascript:;>>
> > wrote:
> > >
> > >> I do that from windows so I don't see how can I change that.
> > >>
> > >> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <dongjoon@apache.org
> <javascript:;>>
> > >> wrote:
> > >>
> > >>> Hi, thank you for all these efforts!
> > >>>
> > >>> But, -1. All bash script permissions are different (644) from our
> > >>> git repository.
> > >>>
> > >>> For the other things,
> > >>> - Signing: OK
> > >>> - MD5/SHA: OK
> > >>> - Maven clean build with tests: Passed.
> > >>>
> > >>> Warmly,
> > >>> Dongjoon.
> > >>>
> > >>>
> > >>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <shulmanb@gmail.com
> <javascript:;>>
> > >>> wrote:
> > >>>
> > >>> > This is to call for a new vote for the source release of Apache
> > >>> > REEF
> > >>> 0.15.0
> > >>> > (rc1).
> > >>> >
> > >>> > The source tar ball, including signatures, digests, etc can be
> > >>> > found
> > >>> at:
> > >>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
> > >>> > ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
> > >>> > %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
> > >>> > e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
> > >>> > tEJ4xZHEiaGD4DZuvOV7HxIw%3d
> > >>> >
> > >>> > The Git tag is release-0.15.0-rc1
> > >>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
> > >>> >
> > >>> >
> > >>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
> > >>> >
> > >>> > MD5: c210138b0415c316bae5e1f779ba62e2
> > >>> > SHA:
> > >>> >
> > >>> >
> > >>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
> > >>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
> > >>> >
> > >>> > Release artifacts are signed with a key found in the KEYS file
> > >>> available
> > >>> > here:
> > >>> >
> > >>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
> > >>> > ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
> > >>> > %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
> > >>> > 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
> > >>> > dSOzPBrFR%2bft6jpre%2fFmQ%3d
> > >>> >
> > >>> >
> > >>> > Issues resolved in this release:
> > >>> >
> > >>> >
> > >>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
> > >>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
> > >>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
> > >>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
> > >>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
> > >>> >
> > >>> >
> > >>> >
> > >>> > The vote will be open for 72 hours. Please download the release
> > >>> > candidate, check the hashes/signature, build it and test it, and
> > >>> > then please vote:
> > >>> >
> > >>> > [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
> > >>> > opinion [ ] -1 Do not release this package because ...
> > >>> >
> > >>> > Thanks!
> > >>> >
> > >>>
> > >>
> > >>
> > >
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Dongjoon,
Can you please let me know what files has wrong permissions and what are
the correct values?
On Fri, May 20, 2016 at 4:50 PM, Julia Wang (QIUHE) <
Qiuhe.Wang@microsoft.com> wrote:
> I didn't encounter this issue, however, I had some issues that was not
> obviously visible from windows :(
>
> -----Original Message-----
> From: Mariia Mykhailova [mailto:mamykhai@microsoft.com]
> Sent: Friday, May 20, 2016 4:48 PM
> To: dev@reef.apache.org
> Subject: RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
>
> I did everything in release 0.13 from a Windows box and didn't have this
> issue (or it went unnoticed?)
>
> -Mariia
>
> -----Original Message-----
> From: Boris Shulman [mailto:shulmanb@gmail.com]
> Sent: Friday, May 20, 2016 4:42 PM
> To: dev@reef.apache.org
> Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
>
> Does it mean that we need to release from linux boxes? It doesn't make
> sense to me.
>
> On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > Can someone with linux box check that and fix it?
> >
> > On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <sh...@gmail.com>
> wrote:
> >
> >> I do that from windows so I don't see how can I change that.
> >>
> >> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org>
> >> wrote:
> >>
> >>> Hi, thank you for all these efforts!
> >>>
> >>> But, -1. All bash script permissions are different (644) from our
> >>> git repository.
> >>>
> >>> For the other things,
> >>> - Signing: OK
> >>> - MD5/SHA: OK
> >>> - Maven clean build with tests: Passed.
> >>>
> >>> Warmly,
> >>> Dongjoon.
> >>>
> >>>
> >>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com>
> >>> wrote:
> >>>
> >>> > This is to call for a new vote for the source release of Apache
> >>> > REEF
> >>> 0.15.0
> >>> > (rc1).
> >>> >
> >>> > The source tar ball, including signatures, digests, etc can be
> >>> > found
> >>> at:
> >>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
> >>> > ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
> >>> > %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
> >>> > e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
> >>> > tEJ4xZHEiaGD4DZuvOV7HxIw%3d
> >>> >
> >>> > The Git tag is release-0.15.0-rc1
> >>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
> >>> >
> >>> >
> >>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
> >>> >
> >>> > MD5: c210138b0415c316bae5e1f779ba62e2
> >>> > SHA:
> >>> >
> >>> >
> >>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
> >>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
> >>> >
> >>> > Release artifacts are signed with a key found in the KEYS file
> >>> available
> >>> > here:
> >>> >
> >>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
> >>> > ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
> >>> > %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
> >>> > 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
> >>> > dSOzPBrFR%2bft6jpre%2fFmQ%3d
> >>> >
> >>> >
> >>> > Issues resolved in this release:
> >>> >
> >>> >
> >>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
> >>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
> >>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
> >>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
> >>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
> >>> >
> >>> >
> >>> >
> >>> > The vote will be open for 72 hours. Please download the release
> >>> > candidate, check the hashes/signature, build it and test it, and
> >>> > then please vote:
> >>> >
> >>> > [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
> >>> > opinion [ ] -1 Do not release this package because ...
> >>> >
> >>> > Thanks!
> >>> >
> >>>
> >>
> >>
> >
>
RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
I didn't encounter this issue, however, I had some issues that was not obviously visible from windows :(
-----Original Message-----
From: Mariia Mykhailova [mailto:mamykhai@microsoft.com]
Sent: Friday, May 20, 2016 4:48 PM
To: dev@reef.apache.org
Subject: RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
I did everything in release 0.13 from a Windows box and didn't have this issue (or it went unnoticed?)
-Mariia
-----Original Message-----
From: Boris Shulman [mailto:shulmanb@gmail.com]
Sent: Friday, May 20, 2016 4:42 PM
To: dev@reef.apache.org
Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Does it mean that we need to release from linux boxes? It doesn't make sense to me.
On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <sh...@gmail.com> wrote:
> Can someone with linux box check that and fix it?
>
> On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <sh...@gmail.com> wrote:
>
>> I do that from windows so I don't see how can I change that.
>>
>> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org>
>> wrote:
>>
>>> Hi, thank you for all these efforts!
>>>
>>> But, -1. All bash script permissions are different (644) from our
>>> git repository.
>>>
>>> For the other things,
>>> - Signing: OK
>>> - MD5/SHA: OK
>>> - Maven clean build with tests: Passed.
>>>
>>> Warmly,
>>> Dongjoon.
>>>
>>>
>>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com>
>>> wrote:
>>>
>>> > This is to call for a new vote for the source release of Apache
>>> > REEF
>>> 0.15.0
>>> > (rc1).
>>> >
>>> > The source tar ball, including signatures, digests, etc can be
>>> > found
>>> at:
>>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>> > ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
>>> > %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
>>> > e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
>>> > tEJ4xZHEiaGD4DZuvOV7HxIw%3d
>>> >
>>> > The Git tag is release-0.15.0-rc1
>>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>>> >
>>> >
>>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
>>> >
>>> > MD5: c210138b0415c316bae5e1f779ba62e2
>>> > SHA:
>>> >
>>> >
>>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
>>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>>> >
>>> > Release artifacts are signed with a key found in the KEYS file
>>> available
>>> > here:
>>> >
>>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>> > ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
>>> > %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
>>> > 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
>>> > dSOzPBrFR%2bft6jpre%2fFmQ%3d
>>> >
>>> >
>>> > Issues resolved in this release:
>>> >
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
>>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
>>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
>>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
>>> >
>>> >
>>> >
>>> > The vote will be open for 72 hours. Please download the release
>>> > candidate, check the hashes/signature, build it and test it, and
>>> > then please vote:
>>> >
>>> > [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
>>> > opinion [ ] -1 Do not release this package because ...
>>> >
>>> > Thanks!
>>> >
>>>
>>
>>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
I am pretty sure we cannot change it on windows. If we can let me know how
and to what files.
On Fri, May 20, 2016 at 4:48 PM, Mariia Mykhailova <ma...@microsoft.com>
wrote:
> I did everything in release 0.13 from a Windows box and didn't have this
> issue (or it went unnoticed?)
>
> -Mariia
>
> -----Original Message-----
> From: Boris Shulman [mailto:shulmanb@gmail.com]
> Sent: Friday, May 20, 2016 4:42 PM
> To: dev@reef.apache.org
> Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
>
> Does it mean that we need to release from linux boxes? It doesn't make
> sense to me.
>
> On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > Can someone with linux box check that and fix it?
> >
> > On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <sh...@gmail.com>
> wrote:
> >
> >> I do that from windows so I don't see how can I change that.
> >>
> >> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org>
> >> wrote:
> >>
> >>> Hi, thank you for all these efforts!
> >>>
> >>> But, -1. All bash script permissions are different (644) from our
> >>> git repository.
> >>>
> >>> For the other things,
> >>> - Signing: OK
> >>> - MD5/SHA: OK
> >>> - Maven clean build with tests: Passed.
> >>>
> >>> Warmly,
> >>> Dongjoon.
> >>>
> >>>
> >>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com>
> >>> wrote:
> >>>
> >>> > This is to call for a new vote for the source release of Apache
> >>> > REEF
> >>> 0.15.0
> >>> > (rc1).
> >>> >
> >>> > The source tar ball, including signatures, digests, etc can be
> >>> > found
> >>> at:
> >>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
> >>> > ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
> >>> > %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
> >>> > e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
> >>> > tEJ4xZHEiaGD4DZuvOV7HxIw%3d
> >>> >
> >>> > The Git tag is release-0.15.0-rc1
> >>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
> >>> >
> >>> >
> >>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
> >>> >
> >>> > MD5: c210138b0415c316bae5e1f779ba62e2
> >>> > SHA:
> >>> >
> >>> >
> >>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
> >>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
> >>> >
> >>> > Release artifacts are signed with a key found in the KEYS file
> >>> available
> >>> > here:
> >>> >
> >>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
> >>> > ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
> >>> > %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
> >>> > 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
> >>> > dSOzPBrFR%2bft6jpre%2fFmQ%3d
> >>> >
> >>> >
> >>> > Issues resolved in this release:
> >>> >
> >>> >
> >>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
> >>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
> >>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
> >>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
> >>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
> >>> >
> >>> >
> >>> >
> >>> > The vote will be open for 72 hours. Please download the release
> >>> > candidate, check the hashes/signature, build it and test it, and
> >>> > then please vote:
> >>> >
> >>> > [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
> >>> > opinion [ ] -1 Do not release this package because ...
> >>> >
> >>> > Thanks!
> >>> >
> >>>
> >>
> >>
> >
>
RE: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Mariia Mykhailova <ma...@microsoft.com>.
I did everything in release 0.13 from a Windows box and didn't have this issue (or it went unnoticed?)
-Mariia
-----Original Message-----
From: Boris Shulman [mailto:shulmanb@gmail.com]
Sent: Friday, May 20, 2016 4:42 PM
To: dev@reef.apache.org
Subject: Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Does it mean that we need to release from linux boxes? It doesn't make sense to me.
On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <sh...@gmail.com> wrote:
> Can someone with linux box check that and fix it?
>
> On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <sh...@gmail.com> wrote:
>
>> I do that from windows so I don't see how can I change that.
>>
>> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org>
>> wrote:
>>
>>> Hi, thank you for all these efforts!
>>>
>>> But, -1. All bash script permissions are different (644) from our
>>> git repository.
>>>
>>> For the other things,
>>> - Signing: OK
>>> - MD5/SHA: OK
>>> - Maven clean build with tests: Passed.
>>>
>>> Warmly,
>>> Dongjoon.
>>>
>>>
>>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com>
>>> wrote:
>>>
>>> > This is to call for a new vote for the source release of Apache
>>> > REEF
>>> 0.15.0
>>> > (rc1).
>>> >
>>> > The source tar ball, including signatures, digests, etc can be
>>> > found
>>> at:
>>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>> > ist.apache.org%2frepos%2fdist%2fdev%2freef%2f0.15.0-rc1%2f&data=01
>>> > %7c01%7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866f
>>> > e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=axKFtd1xGyFJLthtiKJ
>>> > tEJ4xZHEiaGD4DZuvOV7HxIw%3d
>>> >
>>> > The Git tag is release-0.15.0-rc1
>>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>>> >
>>> >
>>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
>>> >
>>> > MD5: c210138b0415c316bae5e1f779ba62e2
>>> > SHA:
>>> >
>>> >
>>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe256
>>> 84054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>>> >
>>> > Release artifacts are signed with a key found in the KEYS file
>>> available
>>> > here:
>>> >
>>> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fd
>>> > ist.apache.org%2frepos%2fdist%2frelease%2freef%2fKEYS&data=01%7c01
>>> > %7cmamykhai%40microsoft.com%7cea0f7888cd7c4f866c9f08d3810866fe%7c7
>>> > 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=AeEWbffbn77EWxtoMkZr%2fV
>>> > dSOzPBrFR%2bft6jpre%2fFmQ%3d
>>> >
>>> >
>>> > Issues resolved in this release:
>>> >
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>> ues.apache.org%2fjira%2fsecure%2fReleaseNote.jspa%3fprojectId%3d1231
>>> 5820%26version%3d12334912&data=01%7c01%7cmamykhai%40microsoft.com%7c
>>> ea0f7888cd7c4f866c9f08d3810866fe%7c72f988bf86f141af91ab2d7cd011db47%
>>> 7c1&sdata=2GvPG8Boe%2bwvVkeFK0gvkWm02uCCbflMALXbML%2fg1Rw%3d
>>> >
>>> >
>>> >
>>> > The vote will be open for 72 hours. Please download the release
>>> > candidate, check the hashes/signature, build it and test it, and
>>> > then please vote:
>>> >
>>> > [ ] +1 Release this package as Apache REEF 0.15.0 [ ] +0 no
>>> > opinion [ ] -1 Do not release this package because ...
>>> >
>>> > Thanks!
>>> >
>>>
>>
>>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Does it mean that we need to release from linux boxes? It doesn't make
sense to me.
On Fri, May 20, 2016 at 4:26 PM, Boris Shulman <sh...@gmail.com> wrote:
> Can someone with linux box check that and fix it?
>
> On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <sh...@gmail.com> wrote:
>
>> I do that from windows so I don't see how can I change that.
>>
>> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org>
>> wrote:
>>
>>> Hi, thank you for all these efforts!
>>>
>>> But, -1. All bash script permissions are different (644) from our git
>>> repository.
>>>
>>> For the other things,
>>> - Signing: OK
>>> - MD5/SHA: OK
>>> - Maven clean build with tests: Passed.
>>>
>>> Warmly,
>>> Dongjoon.
>>>
>>>
>>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com>
>>> wrote:
>>>
>>> > This is to call for a new vote for the source release of Apache REEF
>>> 0.15.0
>>> > (rc1).
>>> >
>>> > The source tar ball, including signatures, digests, etc can be found
>>> at:
>>> > https://dist.apache.org/repos/dist/dev/reef/0.15.0-rc1/
>>> >
>>> > The Git tag is release-0.15.0-rc1
>>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>>> >
>>> >
>>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
>>> >
>>> > MD5: c210138b0415c316bae5e1f779ba62e2
>>> > SHA:
>>> >
>>> >
>>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe25684054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>>> >
>>> > Release artifacts are signed with a key found in the KEYS file
>>> available
>>> > here:
>>> >
>>> > https://dist.apache.org/repos/dist/release/reef/KEYS
>>> >
>>> >
>>> > Issues resolved in this release:
>>> >
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12334912
>>> >
>>> >
>>> >
>>> > The vote will be open for 72 hours. Please download the release
>>> > candidate, check the hashes/signature, build it and test it, and then
>>> > please vote:
>>> >
>>> > [ ] +1 Release this package as Apache REEF 0.15.0
>>> > [ ] +0 no opinion
>>> > [ ] -1 Do not release this package because ...
>>> >
>>> > Thanks!
>>> >
>>>
>>
>>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
Can someone with linux box check that and fix it?
On Fri, May 20, 2016 at 4:25 PM, Boris Shulman <sh...@gmail.com> wrote:
> I do that from windows so I don't see how can I change that.
>
> On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org>
> wrote:
>
>> Hi, thank you for all these efforts!
>>
>> But, -1. All bash script permissions are different (644) from our git
>> repository.
>>
>> For the other things,
>> - Signing: OK
>> - MD5/SHA: OK
>> - Maven clean build with tests: Passed.
>>
>> Warmly,
>> Dongjoon.
>>
>>
>> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com>
>> wrote:
>>
>> > This is to call for a new vote for the source release of Apache REEF
>> 0.15.0
>> > (rc1).
>> >
>> > The source tar ball, including signatures, digests, etc can be found at:
>> > https://dist.apache.org/repos/dist/dev/reef/0.15.0-rc1/
>> >
>> > The Git tag is release-0.15.0-rc1
>> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>> >
>> >
>> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
>> >
>> > MD5: c210138b0415c316bae5e1f779ba62e2
>> > SHA:
>> >
>> >
>> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe25684054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>> >
>> > Release artifacts are signed with a key found in the KEYS file available
>> > here:
>> >
>> > https://dist.apache.org/repos/dist/release/reef/KEYS
>> >
>> >
>> > Issues resolved in this release:
>> >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12334912
>> >
>> >
>> >
>> > The vote will be open for 72 hours. Please download the release
>> > candidate, check the hashes/signature, build it and test it, and then
>> > please vote:
>> >
>> > [ ] +1 Release this package as Apache REEF 0.15.0
>> > [ ] +0 no opinion
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thanks!
>> >
>>
>
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Boris Shulman <sh...@gmail.com>.
I do that from windows so I don't see how can I change that.
On Fri, May 20, 2016 at 4:08 PM, Dongjoon Hyun <do...@apache.org> wrote:
> Hi, thank you for all these efforts!
>
> But, -1. All bash script permissions are different (644) from our git
> repository.
>
> For the other things,
> - Signing: OK
> - MD5/SHA: OK
> - Maven clean build with tests: Passed.
>
> Warmly,
> Dongjoon.
>
>
> On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com> wrote:
>
> > This is to call for a new vote for the source release of Apache REEF
> 0.15.0
> > (rc1).
> >
> > The source tar ball, including signatures, digests, etc can be found at:
> > https://dist.apache.org/repos/dist/dev/reef/0.15.0-rc1/
> >
> > The Git tag is release-0.15.0-rc1
> > The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
> >
> >
> > Checksums of apache-reef-0.15.0-rc1.tar.gz:
> >
> > MD5: c210138b0415c316bae5e1f779ba62e2
> > SHA:
> >
> >
> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe25684054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
> >
> > Release artifacts are signed with a key found in the KEYS file available
> > here:
> >
> > https://dist.apache.org/repos/dist/release/reef/KEYS
> >
> >
> > Issues resolved in this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12334912
> >
> >
> >
> > The vote will be open for 72 hours. Please download the release
> > candidate, check the hashes/signature, build it and test it, and then
> > please vote:
> >
> > [ ] +1 Release this package as Apache REEF 0.15.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks!
> >
>
Re: [VOTE] Release Apache REEF 0.15.0 (rc1)
Posted by Dongjoon Hyun <do...@apache.org>.
Hi, thank you for all these efforts!
But, -1. All bash script permissions are different (644) from our git
repository.
For the other things,
- Signing: OK
- MD5/SHA: OK
- Maven clean build with tests: Passed.
Warmly,
Dongjoon.
On Fri, May 20, 2016 at 3:41 PM, Boris Shulman <sh...@gmail.com> wrote:
> This is to call for a new vote for the source release of Apache REEF 0.15.0
> (rc1).
>
> The source tar ball, including signatures, digests, etc can be found at:
> https://dist.apache.org/repos/dist/dev/reef/0.15.0-rc1/
>
> The Git tag is release-0.15.0-rc1
> The Git commit ID is a45dd5a1b64270f9f04c5d0a6bcb5f6f9193bd65
>
>
> Checksums of apache-reef-0.15.0-rc1.tar.gz:
>
> MD5: c210138b0415c316bae5e1f779ba62e2
> SHA:
>
> 845b668dbdc18ce1549a5fbc29a940c2bb7ee5ea7fd435fb798694f2a7d92dffe25684054e3424efe92a911445f9d502b7f653c0c815aeccdac2a403e72ecbf7
>
> Release artifacts are signed with a key found in the KEYS file available
> here:
>
> https://dist.apache.org/repos/dist/release/reef/KEYS
>
>
> Issues resolved in this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12334912
>
>
>
> The vote will be open for 72 hours. Please download the release
> candidate, check the hashes/signature, build it and test it, and then
> please vote:
>
> [ ] +1 Release this package as Apache REEF 0.15.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks!
>