You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yetus.apache.org by Allen Wittenauer <aw...@altiscale.com> on 2016/03/01 16:06:17 UTC
[VOTE] Apache Yetus 0.2.0-RC1
Artifacts are available:
https://dist.apache.org/repos/dist/dev/yetus/0.2.0-RC1/
As of this vote the relevant md5 hashes are:
MD5 (CHANGES.md) = 49dd63df40a3ea9a098daab449ef1bb1
MD5 (RELEASENOTES.md) = 0eda8dfdbe43599084ab83c65174d634
MD5 (yetus-0.2.0-bin.tar.gz) = d3a2436e7daf8a6ad0330b0932eb247c
MD5 (yetus-0.2.0-src.tar.gz) = 07129903b80db3c5cd922a9467af1f5d
Source repository commit: 17cf9761002ea4769601933577800f57e8b513ca
Our KEYS file is at: https://dist.apache.org/repos/dist/release/yetus/KEYS
All artifacts are signed with my key (E846DF38)
JIRA version: http://s.apache.org/yetus-0.2.0-jira
Please take a few minutes to verify the release[1] and vote on releasing it:
[ ] +1 Release this package as Apache Yetus 0.2.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...
Vote will be subject to Majority Approval[2] and will close at 8:00PM
UTC on Friday, March 4th, 2016[3].
[1]: http://www.apache.org/info/verification.html
[2]: https://www.apache.org/foundation/glossary.html#MajorityApproval
[3]: to find this in your local timezone see:
http://s.apache.org/yetus-0.2.0-rc1-close
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Kengo Seki <se...@gmail.com>.
> What you’re seeing is diff blowing up on symlinks that are in the source
tree. So these should be OK.
I understand. Thanks!
2016-03-04 9:46 GMT+09:00 Allen Wittenauer <
allenwittenauer@yahoo.com.invalid>:
>
> > On Mar 3, 2016, at 8:14 AM, Kengo Seki <se...@gmail.com> wrote:
> >
> > diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0: No
> such
> > file or directory
> > diff:
> >
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/0.1.0:
> > No such file or directory
> > diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/
> 0.1.0.html.md:
> > No such file or directory
> > diff:
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/
> > 0.1.0.html.md: No such file or directory
> > diff:
> >
> yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/in-progress/precommit-apidocs:
> > No such file or directory
> > diff:
> >
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/in-progress/precommit-apidocs:
> > No such file or directory
>
>
> FYI
>
> What you’re seeing is diff blowing up on symlinks that are in the source
> tree. So these should be OK.
>
>
>
--
Kengo Seki <se...@gmail.com>
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Mar 3, 2016, at 8:14 AM, Kengo Seki <se...@gmail.com> wrote:
>
> diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0: No such
> file or directory
> diff:
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/0.1.0:
> No such file or directory
> diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0.html.md:
> No such file or directory
> diff: yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/
> 0.1.0.html.md: No such file or directory
> diff:
> yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/in-progress/precommit-apidocs:
> No such file or directory
> diff:
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/in-progress/precommit-apidocs:
> No such file or directory
FYI
What you’re seeing is diff blowing up on symlinks that are in the source tree. So these should be OK.
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Sean Busbey <bu...@apache.org>.
On Thu, Mar 3, 2016 at 10:14 AM, Kengo Seki <se...@gmail.com> wrote:
> [sekikn@mobile 0.2.0-RC1]$ diff -r yetus-0.2.0-RC1-tag
> yetus-0.2.0-src_unpack/yetus-0.2.0
> Only in yetus-0.2.0-RC1-tag: .git
> Only in yetus-0.2.0-src_unpack/yetus-0.2.0: CHANGES.md
> Only in yetus-0.2.0-src_unpack/yetus-0.2.0: RELEASENOTES.md
> diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0: No such
> file or directory
> diff:
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/0.1.0:
> No such file or directory
> diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0.html.md:
> No such file or directory
> diff: yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/
> 0.1.0.html.md: No such file or directory
> diff:
> yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/in-progress/precommit-apidocs:
> No such file or directory
> diff:
> yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/in-progress/precommit-apidocs:
> No such file or directory
> [sekikn@mobile 0.2.0-RC1]$ echo $?
> 2
>
> The first three lines seems to be ignorable. And I don't know why the
> remaining lines are printed because all of them exist in reality.
> Am I doing something wrong?
>
Those are all symlinks that point to nothing when you do a fresh
checkout, due to our workarounds for Middleman 3.x.
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
Cancelling this RC.
I’ll be posting another vote thread later tonight.
Thanks all!
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Sean Busbey <bu...@apache.org>.
On Thu, Mar 3, 2016 at 12:26 PM, Sean Busbey <bu...@apache.org> wrote:
> On Thu, Mar 3, 2016 at 10:44 AM, Allen Wittenauer
> <al...@yahoo.com.invalid> wrote:
>>
>>> On Mar 3, 2016, at 8:14 AM, Kengo Seki <se...@gmail.com> wrote:
>>>
>>> * I found some "2015"s in LICENSE and NOTICE. Should we update them with
>>> "2016" before release?
>>
>> The one in NOTICE is definitely wrong. The only entries in LICENSE I see are for copyrights related to 3rd party works which I don’t think have been updated this year. I’d hate to have to cancel this RC based upon this, but it’s probably the correct thing to do. :(
>>
>
> Did we change any of our dependency versions such that we'd have a
> more recent copyright for them even if they had updated this year?
>
> The date range on our notice is def wrong though. If we get a fix in
> now we could start a 72hr window today and have a release sunday. On
> the plus side, not a problem we'll hit again for 9 months! ;)
>
>
I've posted a fix on YETUS-323. FWIW, I'll likely vote -1 due to this
error but I totally understand if folks vote the other way.
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Sean Busbey <bu...@apache.org>.
On Thu, Mar 3, 2016 at 10:44 AM, Allen Wittenauer
<al...@yahoo.com.invalid> wrote:
>
>> On Mar 3, 2016, at 8:14 AM, Kengo Seki <se...@gmail.com> wrote:
>>
>> * I found some "2015"s in LICENSE and NOTICE. Should we update them with
>> "2016" before release?
>
> The one in NOTICE is definitely wrong. The only entries in LICENSE I see are for copyrights related to 3rd party works which I don’t think have been updated this year. I’d hate to have to cancel this RC based upon this, but it’s probably the correct thing to do. :(
>
Did we change any of our dependency versions such that we'd have a
more recent copyright for them even if they had updated this year?
The date range on our notice is def wrong though. If we get a fix in
now we could start a 72hr window today and have a release sunday. On
the plus side, not a problem we'll hit again for 9 months! ;)
>> * I tried "ASF required checks" No.4, but I couldn't find the 0.2.0-RC1
>> branch (does Allen's comment[2] mean it?).
>
> I'd consider this is a bug in the documentation. The “how to release” docs create the branch based upon the issue #, doesn't set a temporary tag either, and only shares the git commit hash. The paragraph before step 4 says:
>
> "You SHOULD make sure the source release artifact corresponds to the referenced commit hash in the [VOTE] thread. […] Our eventual release tag is how we’ll provide long term provinence information for our downstream users.”
>
> It acknowledges that we’ll eventually have a release tag, but we don’t yet. So I think the branch checkout should probably be replaced with a hash checkout.
Yeah, sounds like a docs bug. Git tags are mutable, so I prefer not
referencing them in the RC and just sticking with a commit hash.
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Allen Wittenauer <al...@yahoo.com.INVALID>.
> On Mar 3, 2016, at 8:14 AM, Kengo Seki <se...@gmail.com> wrote:
>
> * I found some "2015"s in LICENSE and NOTICE. Should we update them with
> "2016" before release?
The one in NOTICE is definitely wrong. The only entries in LICENSE I see are for copyrights related to 3rd party works which I don’t think have been updated this year. I’d hate to have to cancel this RC based upon this, but it’s probably the correct thing to do. :(
> * I tried "ASF required checks" No.4, but I couldn't find the 0.2.0-RC1
> branch (does Allen's comment[2] mean it?).
I'd consider this is a bug in the documentation. The “how to release” docs create the branch based upon the issue #, doesn't set a temporary tag either, and only shares the git commit hash. The paragraph before step 4 says:
"You SHOULD make sure the source release artifact corresponds to the referenced commit hash in the [VOTE] thread. […] Our eventual release tag is how we’ll provide long term provinence information for our downstream users.”
It acknowledges that we’ll eventually have a release tag, but we don’t yet. So I think the branch checkout should probably be replaced with a hash checkout.
> I used the YETUS-318 branch
> instead, but I got an unexpected result:
FWIW, the YETUS-318 branch should definitely correspond to the given git hash in the vote thread.
> [sekikn@mobile 0.2.0-RC1]$ diff -r yetus-0.2.0-RC1-tag
> yetus-0.2.0-src_unpack/yetus-0.2.0
> Only in yetus-0.2.0-RC1-tag: .git
Understandable.
> Only in yetus-0.2.0-src_unpack/yetus-0.2.0: CHANGES.md
> Only in yetus-0.2.0-src_unpack/yetus-0.2.0: RELEASENOTES.md
IMO, I think this is a good thing to have in the source tar ball.
I’ll need to dig deeper into the rest.
> diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0: No such
> file or directory
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Kengo Seki <se...@gmail.com>.
For now, I'm +0.
I'm checking the RC in accordance with the "Verification" section in the
"Managing a Release" document[1].
I have two questions:
* I found some "2015"s in LICENSE and NOTICE. Should we update them with
"2016" before release?
* I tried "ASF required checks" No.4, but I couldn't find the 0.2.0-RC1
branch (does Allen's comment[2] mean it?). I used the YETUS-318 branch
instead, but I got an unexpected result:
[sekikn@mobile 0.2.0-RC1]$ mkdir yetus-0.2.0-src_unpack
[sekikn@mobile 0.2.0-RC1]$ tar -C yetus-0.2.0-src_unpack -xzf
yetus-0.2.0-src.tar.gz
[sekikn@mobile 0.2.0-RC1]$ git clone --single-branch --depth=1 --branch
YETUS-318 'https://git1-us-west.apache.org/repos/asf/yetus.git'
yetus-0.2.0-RC1-tag
Cloning into 'yetus-0.2.0-RC1-tag'...
remote: Counting objects: 173, done.
remote: Compressing objects: 100% (151/151), done.
remote: Total 173 (delta 37), reused 2 (delta 0)
Receiving objects: 100% (173/173), 974.18 KiB | 328.00 KiB/s, done.
Resolving deltas: 100% (37/37), done.
Checking connectivity... done.
[sekikn@mobile 0.2.0-RC1]$ diff -r yetus-0.2.0-RC1-tag
yetus-0.2.0-src_unpack/yetus-0.2.0
Only in yetus-0.2.0-RC1-tag: .git
Only in yetus-0.2.0-src_unpack/yetus-0.2.0: CHANGES.md
Only in yetus-0.2.0-src_unpack/yetus-0.2.0: RELEASENOTES.md
diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0: No such
file or directory
diff:
yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/0.1.0:
No such file or directory
diff: yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/0.1.0.html.md:
No such file or directory
diff: yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/
0.1.0.html.md: No such file or directory
diff:
yetus-0.2.0-RC1-tag/asf-site-src/source/documentation/in-progress/precommit-apidocs:
No such file or directory
diff:
yetus-0.2.0-src_unpack/yetus-0.2.0/asf-site-src/source/documentation/in-progress/precommit-apidocs:
No such file or directory
[sekikn@mobile 0.2.0-RC1]$ echo $?
2
The first three lines seems to be ignorable. And I don't know why the
remaining lines are printed because all of them exist in reality.
Am I doing something wrong?
[1] http://yetus.apache.org/contribute/releases/
[2]
https://issues.apache.org/jira/browse/YETUS-318?focusedCommentId=15173852&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15173852
2016-03-02 4:11 GMT+09:00 Chris Nauroth <cn...@hortonworks.com>:
> +1 (binding)
>
> - Verified signatures and checksums for all distribution artifacts.
> - Reviewed LICENSE and NOTICE.
> - Quick scan of RELEASENOTES.md looks right.
> - Built successfully from source.
> - Manually tested pre-commit on Hadoop.
>
>
> --Chris Nauroth
>
>
>
>
> On 3/1/16, 7:06 AM, "Allen Wittenauer" <aw...@altiscale.com> wrote:
>
> >
> >Artifacts are available:
> >
> >https://dist.apache.org/repos/dist/dev/yetus/0.2.0-RC1/
> >
> >As of this vote the relevant md5 hashes are:
> >MD5 (CHANGES.md) = 49dd63df40a3ea9a098daab449ef1bb1
> >MD5 (RELEASENOTES.md) = 0eda8dfdbe43599084ab83c65174d634
> >MD5 (yetus-0.2.0-bin.tar.gz) = d3a2436e7daf8a6ad0330b0932eb247c
> >MD5 (yetus-0.2.0-src.tar.gz) = 07129903b80db3c5cd922a9467af1f5d
> >
> >Source repository commit: 17cf9761002ea4769601933577800f57e8b513ca
> >
> >Our KEYS file is at:
> https://dist.apache.org/repos/dist/release/yetus/KEYS
> >All artifacts are signed with my key (E846DF38)
> >
> >JIRA version: http://s.apache.org/yetus-0.2.0-jira
> >
> >Please take a few minutes to verify the release[1] and vote on releasing
> >it:
> >
> >[ ] +1 Release this package as Apache Yetus 0.2.0
> >[ ] +0 no opinion
> >[ ] -1 Do not release this package because...
> >
> >Vote will be subject to Majority Approval[2] and will close at 8:00PM
> >UTC on Friday, March 4th, 2016[3].
> >
> >[1]: http://www.apache.org/info/verification.html
> >[2]: https://www.apache.org/foundation/glossary.html#MajorityApproval
> >[3]: to find this in your local timezone see:
> >http://s.apache.org/yetus-0.2.0-rc1-close
> >
>
>
--
Kengo Seki <se...@gmail.com>
Re: [VOTE] Apache Yetus 0.2.0-RC1
Posted by Chris Nauroth <cn...@hortonworks.com>.
+1 (binding)
- Verified signatures and checksums for all distribution artifacts.
- Reviewed LICENSE and NOTICE.
- Quick scan of RELEASENOTES.md looks right.
- Built successfully from source.
- Manually tested pre-commit on Hadoop.
--Chris Nauroth
On 3/1/16, 7:06 AM, "Allen Wittenauer" <aw...@altiscale.com> wrote:
>
>Artifacts are available:
>
>https://dist.apache.org/repos/dist/dev/yetus/0.2.0-RC1/
>
>As of this vote the relevant md5 hashes are:
>MD5 (CHANGES.md) = 49dd63df40a3ea9a098daab449ef1bb1
>MD5 (RELEASENOTES.md) = 0eda8dfdbe43599084ab83c65174d634
>MD5 (yetus-0.2.0-bin.tar.gz) = d3a2436e7daf8a6ad0330b0932eb247c
>MD5 (yetus-0.2.0-src.tar.gz) = 07129903b80db3c5cd922a9467af1f5d
>
>Source repository commit: 17cf9761002ea4769601933577800f57e8b513ca
>
>Our KEYS file is at: https://dist.apache.org/repos/dist/release/yetus/KEYS
>All artifacts are signed with my key (E846DF38)
>
>JIRA version: http://s.apache.org/yetus-0.2.0-jira
>
>Please take a few minutes to verify the release[1] and vote on releasing
>it:
>
>[ ] +1 Release this package as Apache Yetus 0.2.0
>[ ] +0 no opinion
>[ ] -1 Do not release this package because...
>
>Vote will be subject to Majority Approval[2] and will close at 8:00PM
>UTC on Friday, March 4th, 2016[3].
>
>[1]: http://www.apache.org/info/verification.html
>[2]: https://www.apache.org/foundation/glossary.html#MajorityApproval
>[3]: to find this in your local timezone see:
>http://s.apache.org/yetus-0.2.0-rc1-close
>