Re: [VOTE] Apache Yetus 0.15.0-RC1

[Kengo Seki]

+1 (binding)

Done all checks listed in
https://yetus.apache.org/contribute/releases/#asf-required-checks.
Thank you so much for making this release happen as always, Allen!

Kengo Seki 

On Tue, Nov 14, 2023 at 3:14 PM Allen Wittenauer  wrote:
>
>  Artifacts are available:
>
>  https://dist.apache.org/repos/dist/dev/yetus/0.15.0-RC1/
>
>  As of this vote the relevant sha512 hashes are:
>
> SHA512 (apache-yetus-0.15.0-bin.tar.gz) = 
> a990bd5a73ef062c6fcc20b8e4c1d13a18065496fa23bbdf7a50de94c5898f591b9b8542f948443223b133380ad34492ab7a913c5d739e6dc95e36c3a9e3bafb
> SHA512 (apache-yetus-0.15.0-site.tar.gz) = 
> 7dbc548d428d0575b94aeac489741b68ee1b4397a1e3b3733467e7c750060c516c8acc258070522a319d20f80be5869d85837a50acd84a6b9dca2b0fda7939ab
> SHA512 (apache-yetus-0.15.0-src.tar.gz) = 
> eb7078ccb78dafd76d132a5fd4886658aad4819ee6d318bb175ebc6e89a24a398cb6066b465616b73729a75ee1b3a5176bfe9207f7fd1af1c78dd6c533c0a3fa
> SHA512 (CHANGELOG.md) = 
> 756fdcc316cc13a0e54fdd6c1803e8a2543051191a6a4f44918d6c2d0dabe43f370883d5f0ada50cb61546afb5abdf8d8558010c23e85424b83daeeac98d1c48
> SHA512 (RELEASENOTES.md) = 
> 49b785e8e9186485273dd7cefc14ee977ef134c6a766bae89716811a6d040054ee3cfb00c95e400f3dba3679654e3205ee78385b388bffc6f2658929c35d09f1
>
> Source repository commit: 1ac6b79602b2609aecd72fcb52a6cd9e02314102
> Maven staging repository: 
> https://repository.apache.org/content/repositories/orgapacheyetus-1033
>
>
>
>  Our KEYS file is at: https://downloads.apache.org/yetus/KEYS
>  All artifacts are signed with my key (E846DF38)
>
>  JIRA version: https://s.apache.org/yetus-0.15.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.15.0
>  [ ] +0 no opinion
>  [ ] -1 Do not release this package because...
>
>  The vote will be subject to Majority Approval[2] and will close at 16:00
>  UTC on Wednesday, Nov 22nd, 2023[3].
>
>  [1]: https://www.apache.org/info/verification.html
>  [2]: https://www.apache.org/foundation/glossary.html#MajorityApproval
>  [3]: to find this in your local timezone see:
> https://s.apache.org/yetus-0.15.0-rc1-close

Re: [VOTE] Apache Yetus 0.14.1

[Kengo Seki]

+1 (binding), ensured that it passed all checks described in
https://yetus.apache.org/contribute/releases/#asf-required-checks.

Kengo Seki 

2022年10月20日(木) 11:45 张铎(Duo Zhang) :
>
> +1
>
> Tried in hbase locally, it could fix the problem when building javadoc
> with jdk11.
>
> Thanks!
>
> Allen Wittenauer  于2022年10月18日周二 01:35写道：
> >
> >
> >
> > > On Oct 17, 2022, at 10:34 AM, Allen Wittenauer  wrote:
> > >
> > > Maven staging repository: 
> > > https://repository.apache.org/content/repositories/orgapacheyetus-1031
> >
> > Minor correction: 
> > https://repository.apache.org/content/repositories/orgapacheyetus-1032
> >

Re: [VOTE] Apache Yetus 0.11.1 RC1

[Kengo Seki]

+1 (binding)

I checked all items described in the "ASF required checks" and
"Community recommended checks" documents,
and found no problem (besides trivial inconsistency between the source
tarball and the git checkout that Nick pointed out).

Kengo Seki 

On Fri, Nov 1, 2019 at 2:50 AM Nick Dimiduk  wrote:
>
> +1
>
> I followed the "ASF Required checks" outlined in [0]. Note that the
> contents of the source tarball and the git checkout are not identical.
> However, their divergence seems unrelated to the code itself, nor to one's
> available to build from the provided sources. Also note the discrepancy in
> directory names.
>
> Thanks,
> Nick
>
> [0]: http://yetus.apache.org/contribute/releases/#verification
>
>
>  ✓ verify artifact gpg signatures
>
>  ✓ verify artifact mds signatures
>
>  ✓ verify artifact sha512 signatures
>
>  ✓ verify CHANGELOG.md contains the license header
>
>  ✓ verify RELEASENOTES.md contains the license header
>
>  ✓ verify apache-yetus-0.11.1-bin.tar.gz contains non-empty LICENSE and
> NOTICE files
>
>  ✓ verify apache-yetus-0.11.1-site.tar.gz contains non-empty LICENSE and
> NOTICE files
>
>  ✓ verify apache-yetus-0.11.1-src.tar.gz contains non-empty LICENSE and
> NOTICE files
>
>- note this archive extracts to a directory that doesn’t match the
> others, called ‘yetus-project-0.11.1’. I was expecting something like
> ‘apache-yetus-0.11.1-src’.
>
>  x verify src tarball matches git commit.
>
> $ git remote update --prune
>
>
>
> Fetching origin
>
>
>
> $ git checkout 11add70671de39cd96b56e86e40c64c872b9282f
>
>
>
> HEAD is now at 11add706 YETUS-920. Stage version 0.11.1.
>
>
>
> $ git clean -xdf
>
> $ diff -r ~/repos/apache/yetus yetus-project-0.11.1
>
> Only in /Users/ndimiduk/repos/apache/yetus: .git
>
> Only in /Users/ndimiduk/repos/apache/yetus: .gitattributes
>
> Only in /Users/ndimiduk/repos/apache/yetus: .gitignore
>
> Only in yetus-project-0.11.1: DEPENDENCIES
>
> Only in
> /Users/ndimiduk/repos/apache/yetus/asf-site-src/source/documentation/in-progress:
> precommit-apidocs
>
>  ✓ verify src tarball builds
>
> $ mvn clean install
>
> …
>
> [INFO]
> 
>
> [INFO] Reactor Summary for Apache Yetus Project 0.11.1:
>
> [INFO]
>
> [INFO] Apache Yetus Project ... SUCCESS [
> 2.655 s]
>
> [INFO] Apache Yetus - Audience Annotations  SUCCESS [
> 1.005 s]
>
> [INFO] Apache Yetus - MiniMaven Plugin  SUCCESS [
> 0.828 s]
>
> [INFO] Apache Yetus - Assemblies .. SUCCESS [
> 0.032 s]
>
> [INFO] Apache Yetus - Audience Annotations JDiff Doclet ... SUCCESS [
> 0.060 s]
>
> [INFO] Apache Yetus - Audience Annotations Component .. SUCCESS [
> 0.014 s]
>
> [INFO] Apache Yetus - Precommit ... SUCCESS [
> 0.492 s]
>
> [INFO] Apache Yetus - releasedocmaker . SUCCESS [
> 18.991 s]
>
> [INFO] Apache Yetus - shelldocs ... SUCCESS [
> 8.360 s]
>
> [INFO] Apache Yetus - Website/Documentation ... SUCCESS [
> 0.019 s]
>
> [INFO] Apache Yetus - Distribution  SUCCESS [
> 1.393 s]
>
> [INFO] Apache Yetus - Maven Plugin  SUCCESS [
> 3.330 s]
>
> [INFO]
> 
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> 
>
>  ✓ verify source files are RAT approved
>
> $ mvn apache-rat:check
>
> …
>
> [INFO]
> 
>
> [INFO] Reactor Summary for Apache Yetus Project 0.11.1:
>
> [INFO]
>
> [INFO] Apache Yetus Project ... SUCCESS [
> 0.875 s]
>
> [INFO] Apache Yetus - Audience Annotations  SUCCESS [
> 0.022 s]
>
> [INFO] Apache Yetus - MiniMaven Plugin  SUCCESS [
> 0.018 s]
>
> [INFO] Apache Yetus - Assemblies .. SUCCESS [
> 0.016 s]
>
> [INFO] Apache Yetus - Audience Annotations JDiff Doclet ... SUCCESS [
> 0.015 s]
>
> [INFO] Apache Yetus - Audience Annotations Component .. SUCCESS [
> 0.016 s]
>
> [INFO] Apache Yetus - Precommit ... SUCCESS [
> 0.051 s]
>
> [INFO] Apache Yetus - releasedocmaker . SUCCESS [
> 0.212 s]
>
> [INFO] Apache Yetus - shelldocs ..

Re: [VOTE] Apache Yetus 0.10.0-RC1

[Kengo Seki]

+1 (binding)

All checks described in
http://yetus.apache.org/contribute/releases/#verification passed.
I found a trivial documentation issue and filed it as YETUS-863, but
it doesn't block this release itself.
Thanks a lot Allen, as always!

Kengo Seki 

On Mon, Apr 22, 2019 at 1:54 AM Allen Wittenauer  wrote:
>
>  Artifacts are available:
>
>  https://dist.apache.org/repos/dist/dev/yetus/0.10.0-RC1/
>
>  As of this vote the relevant sha512 hashes are:
>
> SHA512 (CHANGELOG.md) = 
> bd28a21c36226f7526bf0fb9788275dd5a22a78610fcae09159dff04e6d9d42997d39c5289bc1d186a80e7e18518666ddfbea0a90f39878a0c3592b574174a5a
> SHA512 (RELEASENOTES.md) = 
> a4841d04c154e738cee4fa7e4b8c9f47ac57d498aa502d08304c3be659025cabd5116e1baf362f03c0640f466e442b52fc56a38c5e6b22a17728c745f060bc45
> SHA512 (apache-yetus-0.10.0-bin.tar.gz) = 
> 42f89909d63588488fa8ca4005984e5d32f91e0c9fb363db46c25cdad1f294cfdef023c2b9fba70007ae5dfb09b2effacc18d3c7469b2abbb42c098d9dd78e93
> SHA512 (apache-yetus-0.10.0-site.tar.gz) = 
> 84f81976a368accf50de869826dd3ae57f9158a7ed592e764405ba00f4bc45b13d8795622efbe806f4a145b1a48fe09a884aafc584e6a37bd0d63cd7837a3195
> SHA512 (apache-yetus-0.10.0-src.tar.gz) = 
> 57b15f3c53af50b4efed4951992cb7ccfa3b9103af0dadc60f8dcf4f94f95849edf6997fb799a0fd29024404fbf480ba4d5c98fc07752c833a8c44013cfe3924
>
>  Source repository commit: 9fcd657decbd96131afdcaf545f29a6273fa2fe4
>  Maven staging repository: 
> https://repository.apache.org/content/repositories/orgapacheyetus-1016
>
>  Our KEYS file is at: https://www.apache.org/dist/yetus/KEYS
>  All artifacts are signed with my key (E846DF38)
>
>  JIRA version: https://s.apache.org/yetus-0.10.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.10.0
>  [ ] +0 no opinion
>  [ ] -1 Do not release this package because...
>
>  The vote will be subject to Majority Approval[2] and will close at 7:00 PM
>  UTC on Wednesday, April 24tth, 2019[3] or until a majority has been reached.
>
>  [1]: https://www.apache.org/info/verification.html
>  [2]: https://www.apache.org/foundation/glossary.html#MajorityApproval
>  [3]: to find this in your local timezone see:
> https://s.apache.org/yetus-0.10.0-rc1-close

Re: [VOTE] Apache Yetus 0.9.0-RC1

[Kengo Seki]

Thanks a lot for driving the release again, Allen!

+1 (binding)

All checks described in
http://yetus.apache.org/contribute/releases/#verification passed.
I found a few minor issues which don't block this release (I think), so I
just filed them as YETUS-772 and YETUS-773.

Kengo Seki apache.org>

On Thu, Jan 10, 2019 at 10:39 AM Sean Busbey  wrote:
>
> On Thu, Jan 10, 2019 at 12:26 PM Allen Wittenauer
>  wrote:
> >
> >
> >
> > > On Jan 10, 2019, at 10:12 AM, Sean Busbey  wrote:
> > >
> > > Excellent. Thanks for putting together this RC. So far I've just been
> > > reading RN and looking at the shape of the artifacts.
> > >
> > > Given:
> > >
> > >> releasedocmaker and shelldocs are now available as Jython-built jars.
> > >
> > > why don't these show up in the staged maven repo?
> >
> > Yeah, I noticed that too, but didn’t think it was enough to stop the
release.  They *do* show up in the local repo. The other new bit
(yetus-maven-plugin) does. I suspect my pom skullduggery is the reason.
Now that things are starting to approach stable, I’m hoping those better
versed in maven can step in and tell me how badly I screwed it up with a
patch. :)
>
> That woks for me. I'm a big fan of roll-forward for us here in Yetus.
> I'll include a jira when I vote.

Re: YETUS-15 has become a blocker for me

[Kengo Seki]

Hi Allen,

I couldn't see all your changes yet, but with YETUS-15.008.patch, `mvn
site` failed due to the leading blank line in
releasedocmaker/src/main/python/releasedocmaker.py.
I think I can make some time to review other changes within this week :)

Kengo Seki 

On Tue, Oct 16, 2018 at 6:03 PM Allen Wittenauer
 wrote:
>
>
> Hey gang.
>
> This is just a heads up that YETUS-15 has effectively become a 
> blocker for me. It’d be great to get more eyes on it for all  the large patch 
> reasons as well as it being a fundamental shift in how Yetus is developed.
>
> If you’d like to see it in action (along with a good portion of 
> everything that I have is sitting on top of it), you can check out 
> https://gitlab.com/_a__w_/buretoolbox or 
> https://github.com/aw-was-here/buretoolbox .
>
> Thanks.

Re: 0.8.0 release and items awaiting review

[Kengo Seki]

Thanks for driving the release Sean! I think I can take a look at them
this weekend.

Kengo Seki <sek...@apache.org>


2018-05-18 0:15 GMT+09:00 Sean Busbey <bus...@apache.org>:
> Hi folks!
>
> I'd like to get a 0.8.0 release out soon so that YETUS-622
> "docker-cleanup removes non-Yetus docker images even if not in
> sentinel mode" is available in a release.
>
> I'm happy to RM that release. Prior to doing so, I'm hoping to get in
> a few changes that impact plans in the Apache HBase project.
>
> Some are simple fixes related to our existing project use:
>
> * YETUS-634 "maven plugin dropping '--batch-mode' maven argument"
> * YETUS-635 "Maven plugin should fail when partially enabled"
>
> One is more involved and adds a new test plugin that I'm trying to get
> added to our nightly test runs:
>
> * YETUS-441 "Add a precommit check for known CVEs from dependencies"
>
> I'm looking for feedback on any of the above. Reminder that in Apache
> Yetus we encourage reviews from all contributors; your review vote is
> binding even if you have not yet been recognized as a committer (and
> reviews are a fast track to becoming one).

Re: [VOTE] Apache Yetus 0.7.0-RC1

[Kengo Seki]

+1 (binding). Sorry for the late vote.

* checked signatures
* checked checksums
* skimmed licensing
* source corresponds to given repo commit
* ran build on source

Kengo Seki <sek...@apache.org>


2018-01-18 1:51 GMT+09:00 Allen Wittenauer <a...@effectivemachines.com>:
>
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.7.0-RC1/
>
> As of this vote the relevant md5 hashes are:
> MD5 (CHANGELOG.md) = 54b6a11b8218b8b153e1302c41b20715
> MD5 (RELEASENOTES.md) = adecafd29ef7872cfcf5deadaacf2921
> MD5 (yetus-0.7.0-bin.tar.gz) = 8617cb0b49aadd0254200b192e4e984d
> MD5 (yetus-0.7.0-src.tar.gz) = f46ef9a1c922fd2fd40deb01c2ae1613
>
> Source repository commit: 39a14ba39589321ff6a62834d6ea27ba62b4a4ac
>
> 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.7.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.7.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Vote will be subject to Majority Approval[2] and will close at 00:00 (12:00 
> AM Midnight)
> UTC on Sunday, Jan 21st, 2018[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:
> https://s.apache.org/yetus-0.7.0-rc1-close
>
> P.S.:
> Thanks to Sean for already starting the work on 0.7.0 last month. :)
>

Re: [VOTE] Apache Yetus 0.6.0-RC1

[Kengo Seki]

+1 Thanks Sean!

* checked signatures
* checked checksums
* skimmed licensing
* source corresponds to given repo commit
* ran build on source
* ran test-patch and confirmed that it worked and its result included
build tool version (YETUS-510).
* ran releasedocmaker and confirmed that it worked on Ubuntu (YETUS-544).
* read release notes and changes

Kengo Seki <sek...@apache.org>


2017-10-30 15:02 GMT+09:00 Sean Busbey <bus...@apache.org>:
> Those are from the source. They're a workaround for a limitation in
> Middleman 3 (what we use for our website generation) that got added in
> YETUS-192.
>
> You can see them on github here:
> https://github.com/apache/yetus/blob/master/asf-site-src/source/documentation/in-progress/precommit-apidocs
> https://github.com/apache/yetus/blob/master/asf-site-src/source/documentation/0.4.0
> https://github.com/apache/yetus/blob/master/asf-site-src/source/documentation/0.4.0.html.md
> https://github.com/apache/yetus/blob/master/asf-site-src/source/documentation/0.5.0
> https://github.com/apache/yetus/blob/master/asf-site-src/source/documentation/0.5.0.html.md
>
> If you follow the instructions for building the website:
>
> http://yetus.apache.org/contribute/website/
>
> then those target directories will all be filled in.
>
> On Sun, Oct 29, 2017 at 1:41 PM, suraj acharya <suraj@gmail.com> wrote:
>> Hi Sean,
>> Thanks for driving this release.
>> -1 There seems to be an issue with an invalid symlink in the tarball
>> created :
>> /tmp/yetus-06/dist.apache.org/repos/dist/dev/yetus/0.6.0-RC1$  ls -la
>> yetus-0.6.0_src_unpack/yetus-0.6.0/asf-site-src/source/documentation/in-progress/precommit-apidocs
>> lrwxr-xr-x  1 sacharya  wheel  48 Mar 19  2016
>> yetus-0.6.0_src_unpack/yetus-0.6.0/asf-site-src/source/documentation/in-progress/precommit-apidocs
>> -> ../../../../target/in-progress/precommit-apidocs
>> There is no target directory present.
>> The only place where the file is present is :
>> /tmp/yetus-06/dist.apache.org/repos/dist/dev/yetus/0.6.0-RC1$  find . -name
>> precommit-apidocs
>> ./yetus-0.6.0_src_unpack/yetus-0.6.0/asf-site-src/source/documentation/in-progress/precommit-apidocs
>> There doesn't seem to be any issue with the release bits itself. The build
>> runs perfectly fine.
>>
>> My vote is non-binding.
>>
>> Thanks
>>
>> -Suraj Acharya
>>
>> On Thu, Oct 26, 2017 at 11:20 PM, Sean Busbey <bus...@apache.org> wrote:
>>
>>> Hi folks!
>>>
>>> Artifacts are available:
>>>
>>> https://dist.apache.org/repos/dist/dev/yetus/0.6.0-RC1/
>>>
>>> As of this vote the relevant md5 hashes are:
>>>
>>> fac98675fd631d4ddedce50935938000  CHANGES.md
>>> 96b3fd3de50cb41717d5f20a7a432de8  RELEASENOTES.md
>>> 93ed47909c5f0ea71b40ff52a45dd221  yetus-0.6.0-bin.tar.gz
>>> 5fcf51ba246cd86fd401cc072f67b469  yetus-0.6.0-src.tar.gz
>>>
>>> Source repository commit: e5114ff24225c829b54bfb0eac70e2de41d33053
>>>
>>>
>>> Our KEYS file is at: https://dist.apache.org/repos/dist/release/yetus/KEYS
>>> All artifacts are signed with my key (0D80DB7C)
>>>
>>> JIRA version: http://s.apache.org/yetus-0.6.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.6.0
>>> [ ] +0 no opinion
>>> [ ] -1 Do not release this package because...
>>>
>>> Vote will be subject to Majority Approval[2] and will be open for at
>>> least 72 hours.
>>> I would like to close it at 1:00PM UTC on Monday, Oct 30th, 2017[3].
>>>
>>> [1]:
>>> http://yetus.apache.org/contribute/releases/#verification
>>> 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.6.0-rc1-close
>>>

Re: [VOTE] Apache Yetus 0.4.0-RC1

[Kengo Seki]

+1 binding. Sorry for the late response.

- Verified signatures and checksums for both source and binary distributions.
- Reviewed LICENSE and NOTICE.
- Confirmed the source release artifact matches the referenced hash in
the [VOTE] thread (at step 4 in
https://yetus.apache.org/contribute/releases/#asf-required-checks, I
used 'YETUS-468' branch instead of '0.4.0-RC1' and there was no
difference except for CHANGES.md/RELEASENOTES.md for 0.4.0 and
symlinks).
- Built from source.
- Manually tested pre-commit on Hadoop.
- Manually tested audience annotations.

Kengo Seki <sek...@apache.org>


2016-12-27 15:29 GMT+09:00 Ajay Yadava <ajayyad...@apache.org>:
> Thank you for your consideration to take time out during the holidays. Will
> keep the vote open for as long as required.
>
> Cheers
> Ajay Yadava
>
> On Tue, Dec 27, 2016 at 12:28 AM Sean Busbey <bus...@apache.org> wrote:
>
> Sorry, with the holiday in the US I wasn't able to find time to evaluate
> this RC.
>
> I should have time this week if you're willing to hold the RC open.
>
> On Dec 19, 2016 16:47, "Ajay Yadava" <ajayyad...@apache.org> wrote:
>
>> Hello everyone,
>>
>>
>> Artifacts are available:
>>
>> https://dist.apache.org/repos/dist/dev/yetus/0.4.0-RC1/
>>
>> As of this vote the relevant md5 hashes are:
>>
>> MD5 (CHANGES.md) = 9aa44f874ad9e7d7e942c81d10ea7018
>>
>> MD5 (RELEASENOTES.md) = 781721f410eb3c3467f186745e196044
>>
>> MD5 (yetus-0.4.0-bin.tar.gz) = aba1ef9209c4e2a5033e389590928054
>>
>> MD5 (yetus-0.4.0-src.tar.gz) = f9d2e13708c42a021c865e5e61e5e564
>>
>>
>> Source repository commit: c52226201a1ee88ea463d7ed15f0ec80499109ea
>>
>>
>> Our KEYS file is at: https://dist.apache.org/repos/dist/release/yetus/KEYS
>> All artifacts are signed with my key (61CD1D5F)
>>
>>
>> JIRA version: http://s.apache.org/yetus-0.4.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.4.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...
>>
>> Vote will be subject to Majority Approval[2] and will close at 0:00 AM UTC
>> on Monday, December 26, 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.4.0-rc1-close
>>
>> --
>> Regards
>> Ajay Yadava
>>
>
> --
> Regards
> Ajay Yadava

Re: Jira privilegies

[Kengo Seki]

Hi,

Thanks for your contribution! I've just added you to JIRA contributor
list so that you can become an assignee.

Kengo Seki <sek...@apache.org>


2016-12-01 19:50 GMT+09:00 Peter Vary <pv...@cloudera.com>:
> Hi,
>
> I would like to assign a Yetus jira to myself, but it seems to me that I do 
> not have the appropriate rights.
>
> Who could help me with this? Who should I ask?
>
> Username: pvary
> Jira: YETUS-471 <https://issues.apache.org/jira/browse/YETUS-471>
>
> Thanks,
> Peter

Re: [ANNOUNCE] New Apache Yetus Committer: Andrew Wang

[Kengo Seki]

Congratulations Andrew!

Kengo Seki <sek...@apache.org>


2016-09-22 6:26 GMT+09:00 Marco Zühlke <mzueh...@gmail.com>:
> Congratulations, Andrew.
>
> Marco
>
> 2016-09-21 20:16 GMT+02:00 Karen Clark <kclark@gmail.com>:
>
>> Congratulations, Andrew!
>>
>> On Sep 21, 2016 3:15 AM, "Ajay Yadava" <ajayyad...@apache.org> wrote:
>>
>> > Congratulations Andrew! My twin committer :P
>> >
>> > Regards
>> > Ajay Yadava
>> >
>> > On Tue, Sep 20, 2016, 4:39 PM Andrew Wang <andrew.w...@cloudera.com>
>> > wrote:
>> >
>> > > Thanks folks! Looking forward to working with all y'all on this
>> project.
>> > >
>> > > On Tue, Sep 20, 2016 at 9:18 AM, Chris Nauroth <
>> cnaur...@hortonworks.com
>> > >
>> > > wrote:
>> > >
>> > > > Congratulations, Andrew!
>> > > >
>> > > > --Chris Nauroth
>> > > >
>> > > > On 9/20/16, 7:59 AM, "Sean Busbey" <bus...@apache.org> wrote:
>> > > >
>> > > > Hi folks!
>> > > >
>> > > > On behalf of the Apache Yetus PMC, I'm pleased to announce Andrew
>> > > Wang
>> > > > as a committer. Andrew has been contributing to the project since
>> > > > shortly after the project's formation. Since March, Andrew has
>> > done a
>> > > > great job of improving our Release Doc Maker component and
>> > generally
>> > > > improving our handling of Python within the project. We're
>> pleased
>> > at
>> > > > the chance to recognize what Andrew has done and hope to see
>> more.
>> > > >
>> > > > Please join me in congratulating Andrew!
>> > > >
>> > > > --
>> > > > busbey
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> >
>>

Re: Need help with patches

[Kengo Seki]

Hi Ajay,

Thank you for your active contribution! It's really helpful.
I think I have some time to review your patches today. Just wait for a
while.

Kengo Seki <sekikn@ <sek...@gmail.com>apache.org>

2016-07-29 16:08 GMT+09:00 Ajay Yadava <ajayyad...@apache.org>:

> Hello everyone,
>
> I know I am probably overloading the community with a barrage of JIRAs/
> patches. However, I have hit sort of blocker because of conflicting patches
> and I just wanted to reach out to the community to seek some help with
> review / commit of following patches. This will unblock me to work on my
> next set of tasks and I will really appreciate the help.
>
>
> [image: pasted1]
>
> Regards
> Ajay Yadava
>

Re: Apache Yetus Report Card

[Kengo Seki]

+1 too!

2016-06-24 6:19 GMT+09:00 Sean Busbey :
> I generally like the idea of us dog fooding as much as possible, so I'd be +1.
>
> On Thu, Jun 23, 2016 at 12:11 PM, Allen Wittenauer  wrote:
>> I still have this running.  I wonder if I should start sending them here?
>>
>>
>>> Begin forwarded message:
>>>
>>> From: Apache Jenkins Server 
>>> Subject: Apache Yetus Report Card
>>> Date: June 22, 2016 at 11:01:24 PM PDT
>>> To: a...@apache.org
>>>
>>> For more details, see https://builds.apache.org/job/yetus-qbt/104/
>>>
>>> [Jun 22, 2016 9:27:07 AM] (sekikn) YETUS-407. DOAP is broken
>>>
>>>
>>>
>>>
>>> -1 overall
>>>
>>>
>>> The following subsystems voted -1:
>>>rubocop shelldocs
>>>
>>>
>>> The following subsystems voted -1 but
>>> were configured to be filtered/ignored:
>>>ruby-lint
>>>
>>>
>>>   rubocop:
>>>
>>>   
>>> https://builds.apache.org/job/yetus-qbt/104/artifact/out/diff-patch-rubocop.txt
>>>   [4.0K]
>>>
>>>   ruby-lint:
>>>
>>>   
>>> https://builds.apache.org/job/yetus-qbt/104/artifact/out/diff-patch-ruby-lint.txt
>>>   [4.0K]
>>>
>>>   shelldocs:
>>>
>>>   
>>> https://builds.apache.org/job/yetus-qbt/104/artifact/out/diff-patch-shelldocs.txt
>>>   [28K]
>>>
>>> Powered by Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org
>>>
>>>
>>

[ANNOUNCE] Apache Yetus 0.3.0 release

[Kengo Seki]

Apache Yetus 0.3.0 Released!

The Apache Software Foundation and the Apache Yetus Project are pleased to
announce the release of version 0.3.0 of Apache Yetus.

Apache Yetus is a collection of libraries and tools that enable contribution
and release processes for software projects. It provides a robust system
for automatically checking new contributions against a variety of community
accepted requirements, the means to document a well defined supported
interface for downstream projects, and tooling to help release managers
generate release documentation based on the information provided by
community issue trackers and source repositories.

This version marks the latest minor release representing the community's
work over the last 2 months.

To download please choose a mirror by visiting:

https://yetus.apache.org/downloads/

The relevant checksums files are available at:

https://www.apache.org/dist/yetus/0.3.0/yetus-0.3.0-src.tar.gz.mds
https://www.apache.org/dist/yetus/0.3.0/yetus-0.3.0-bin.tar.gz.mds

Project member signature keys can be found at

   https://www.apache.org/dist/yetus/KEYS

PGP signatures are available at:

https://www.apache.org/dist/yetus/0.3.0/yetus-0.3.0-src.tar.gz.asc
https://www.apache.org/dist/yetus/0.3.0/yetus-0.3.0-bin.tar.gz.asc

The list of changes included in this release and release notes can be
browsed at:

https://yetus.apache.org/documentation/0.3.0/CHANGES/
https://yetus.apache.org/documentation/0.3.0/RELEASENOTES/

Documentation for this release is at:

https://yetus.apache.org/documentation/0.3.0/

On behalf of the Apache Yetus team, thanks to everyone who helped with this
release!

Questions, comments, and bug reports are always welcome on

dev@yetus.apache.org

--
Kengo Seki
Apache Yetus PMC

[RESULT] [VOTE] Apache Yetus 0.3.0-RC1

[Kengo Seki]

With the following votes, the vote passes. Thanks everyone!

+1 (binding) : 3
+1 (non-binding) : 3

I'll push a release tag and move the release artifacts to the
distribution area later today.

Kengo Seki <sek...@apache.org>

Re: [VOTE] Apache Yetus 0.3.0-RC1

[Kengo Seki]

Thanks everyone for reviewing, voting and pointing out issues we've missed!
I think the issues that Justin and Aldrin found doesn't block this
release and will be fixed in the next release,
so I'm going to judge the result based on the "Majority Approval" rule
as usual after the vote is closed.
Just let me know if any problem.

Kengo Seki <sek...@apache.org>


2016-05-20 13:21 GMT+09:00 Aldrin Piri <aldrinp...@gmail.com>:
> +1, non-binding
>
> Verified signatures for all artifacts with the specified key
> Verified hashes.
> Release notes and changelog look good
>
> Minor
> Had some troubles building as my Python environment is the one that ships
> with OS X and did not have the python-dateutil module for the imported
> dateutil.parser.  Opened an issue, YETUS-404 (I feel like there's a joke in
> there somewhere) [1] and provided a patch to provide similar checking as
> the other dependencies.
>
> [1] https://issues.apache.org/jira/browse/YETUS-404
>
>
> On Wed, May 18, 2016 at 5:22 PM, Chris Nauroth <cnaur...@hortonworks.com>
> wrote:
>
>> Justin, thank you for your review.  I really appreciate the effort you've
>> put into thorough license reviews on multiple ASF projects.  Yes, please
>> do file a JIRA.
>>
>>
>> --Chris Nauroth
>>
>>
>>
>>
>> On 5/18/16, 1:48 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>>
>> >Hi,
>> >
>> >+1 (non-binding) Be nice to fix the couple very minor issues for the next
>> >release. Want me to raise a JIRA?
>> >
>> >I checked:
>> >- signatures and hashes good
>> >- LICENSE OK, but the short form of licenses are generally preferred
>> >- LICENSE missing MIT normalize.css [1]
>> >- NOTICE OK, but included a few extra items that are not required.
>> >Normally no need to list permissive licensed software's copyright in
>> >NOTICE  [2]
>> >- no unexpected binaries in source
>> >- all source files have Apache headers
>> >- can compile from source
>> >
>> >Also checked the convienance binary  the LICENSE and NOTICE are correct
>> >for what is bundled (as the site is not included).
>> >
>> >Thanks,
>> >Justin
>> >
>> >1. contained inside ./asf-site-src/source/assets/css/bootstrap.css
>> >2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>>
>>

Re: 0.3.0 RC status

[Kengo Seki]

Thanks for the comment, I'm going to try qbt!

By the way, when I did some JIRA work in accordance with the release
management document, I noticed I couldn't create a new version.
(I accessed 
https://issues.apache.org/jira/plugins/servlet/project-config/YETUS/versions,
but encountered "You cannot edit the configuration of this project"
error)
It seemed that I also couldn't set a start date for a version.
Did I miss something, or do we need some INFRA work?

2016-04-13 14:52 GMT+09:00 Allen Wittenauer <allenwittena...@yahoo.com.invalid>:
>
>> On Apr 11, 2016, at 9:56 AM, Kengo Seki <sek...@apache.org> wrote:
>> * determine which JIRAs should be included in this release. I'll go
>> through unresolved issues later, but just let me know if you have ones
>> that you'd like to include. Especially, can we merge YETUS-156?
>
> I think YETUS-156 is close enough that folks should probably start 
> pouring through it. The core code is there and at this point it should just 
> be polishing. I’ve been running tests against Hadoop here:   
> https://builds.apache.org/job/hadoop-qbt-test  (altho I just wiped the 
> workspaces and I think the Hadoop compile itself is broken due to 35f0770 
> missing files.  So probably want to look at the output later haha.)



-- 
Kengo Seki <sek...@apache.org>

0.3.0 RC status

[Kengo Seki]

Hi folks,

I'm preparing 0.3.0 release now, but I'm running late because of my
busyness and lack of experience as RM.
Let me share the current status.

Finished:

* added my public key into KEYS file
* registered my public key with public key servers and my fingerprint
with ASF LDAP server

Remaining:

* create a JIRA issue and a new git branch. I'll do it soon.
* determine which JIRAs should be included in this release. I'll go
through unresolved issues later, but just let me know if you have ones
that you'd like to include. Especially, can we merge YETUS-156?
* check those JIRAs and update some fields for release-doc-making, if needed
* build release artifacts, update them to the staging area, and call a vote

This is my first work as RM, so please let me know if I missed
something. Thanks!

-- 
Kengo Seki <sek...@apache.org>

Re: [VOTE] Apache Yetus 0.2.1-RC1

[Kengo Seki]

> could you start a new thread that summarizes what we still need to do for 
> that release?

Sure, I'll post it today!


2016-04-09 0:24 GMT+09:00 Chris Nauroth <cnaur...@hortonworks.com>:
> Thanks for the summary, Sean.
>
> My apologies, but it appears I missed the past several days of emails to
> the dev list.  I definitely see the [RESULT] thread now when I look in the
> mail archives, so it must be a problem on my end.
>
> I'll watch out for the next RC and participate on that one if I'm here.
>
> --Chris Nauroth
>
>
>
>
> On 4/7/16, 8:21 PM, "Sean Busbey" <bus...@apache.org> wrote:
>
>>Yep!
>>
>>Kengo and I agreed to not worry about the prior release information
>>for the 0.2.1 release and he's going to file a follow-on jira for us
>>to copy all of the release info from master (without maintaining
>>specific commits) as a part of our release process in the future.
>>
>>After that, he changed his vote to +1. Later I voted +1 and yesterday
>>evening Allen did as well. The vote has now closed, with just enough
>>votes to pass.
>>
>>I'm not sure where Kengo is on 0.3.0 RCs. Kengo, could you start a new
>>thread that summarizes what we still need to do for that release?
>>
>>On Thu, Apr 7, 2016 at 3:49 PM, Chris Nauroth <cnaur...@hortonworks.com>
>>wrote:
>>> Sean and Kengo, did the two of you reach agreement on how to proceed
>>>with
>>> this RC?  I had been holding off my own verification and voting due to
>>>the
>>> open question.
>>>
>>> I'm available to verify an RC tonight and tomorrow.  After Friday, 4/8
>>>at
>>> 3 PM PST, I'll be unavailable through at least 4/18.
>>>
>>> --Chris Nauroth
>>>
>>>
>>>
>>>
>>> On 4/5/16, 4:36 AM, "Kengo Seki" <sek...@apache.org> wrote:
>>>
>>>>> For example, Say 0.2.2 is made after we've had a 0.3.0 release.
>>>>> Would I backport both the change for 0.2.1's release and 0.3.0's?
>>>>> When 0.3.1 comes out do I backport the notice for 0.2.2?
>>>>
>>>>Sorry for not explaining enough, I didn't intend to backport 0.3.x
>>>>into 0.2.x. I simply thought it might be natural that 0.2.1 contains
>>>>documents for 0.1.0, 0.2.0 and 0.2.1 because 0.2.1 is based on 0.2.0.
>>>>
>>>>But in this case, the difference between 0.2.0 and 0.2.1 is very small
>>>>and obvious from the changelog. In addition, users can check online
>>>>document for 0.2.0 and 0.2.1 after release. So I approve #1 and +1 for
>>>>this RC now.
>>>>
>>>>> On the other hand, we could just have a step of copying the files that
>>>>> change with a successful release directly from then-current master.
>>>>> That would get all of the changes without needing to go searching for
>>>>> the individual commits. HBase does this for docs and it works okay.
>>>>
>>>>That sounds good to me. I'll file it as a JIRA later.
>>>>
>>>>2016-04-05 6:22 GMT+09:00 Sean Busbey <bus...@apache.org>:
>>>>> On Mon, Apr 4, 2016 at 12:31 PM, Kengo Seki <sek...@apache.org> wrote:
>>>>>> I'm +0 for now.
>>>>>> My concern is that YETUS-318-website.patch seems not to be included
>>>>>> this RC. Should we merge this?
>>>>>> If it's unnecessary, I'm +1 (binding). I checked the followings:
>>>>>>
>>>>>
>>>>>
>>>>> ... interesting. This comes down to what we want in our release
>>>>> process, I think. The post-release-vote website changes always go into
>>>>> some future minor release, by virtue of our current instructions. That
>>>>> means if we want to be able to cut maintenance releases off of the
>>>>> prior minor release we have to either
>>>>>
>>>>> 1) accept that you can't build a correct website off of the
>>>>> maintenance release source
>>>>>
>>>>> 2) backport needed website changes onto the maintenance branch
>>>>>
>>>>> I lean towards #1 just as a matter of logistics. For example, Say
>>>>> 0.2.2 is made after we've had a 0.3.0 release. Would I backport both
>>>>> the change for 0.2.1's release and 0.3.0's? When 0.3.1 comes out do I
>>>>> backport the notice for 0.2.2? Do we do this for every release that's
>>>>> happened since the last maintenance release? Are we setting ourselves
>>>>> up for an ever-increasing amount of work then?
>>>>>
>>>>> On the other hand, we could just have a step of copying the files that
>>>>> change with a successful release directly from then-current master.
>>>>> That would get all of the changes without needing to go searching for
>>>>> the individual commits. HBase does this for docs and it works okay.
>>>>
>>>>
>>>>
>>>>--
>>>>Kengo Seki <sek...@apache.org>
>>>>
>>>
>>
>



-- 
Kengo Seki <sek...@apache.org>

Re: [VOTE] Apache Yetus 0.2.1-RC1

[Kengo Seki]

> For example, Say 0.2.2 is made after we've had a 0.3.0 release.
> Would I backport both the change for 0.2.1's release and 0.3.0's?
> When 0.3.1 comes out do I backport the notice for 0.2.2?

Sorry for not explaining enough, I didn't intend to backport 0.3.x
into 0.2.x. I simply thought it might be natural that 0.2.1 contains
documents for 0.1.0, 0.2.0 and 0.2.1 because 0.2.1 is based on 0.2.0.

But in this case, the difference between 0.2.0 and 0.2.1 is very small
and obvious from the changelog. In addition, users can check online
document for 0.2.0 and 0.2.1 after release. So I approve #1 and +1 for
this RC now.

> On the other hand, we could just have a step of copying the files that
> change with a successful release directly from then-current master.
> That would get all of the changes without needing to go searching for
> the individual commits. HBase does this for docs and it works okay.

That sounds good to me. I'll file it as a JIRA later.

2016-04-05 6:22 GMT+09:00 Sean Busbey <bus...@apache.org>:
> On Mon, Apr 4, 2016 at 12:31 PM, Kengo Seki <sek...@apache.org> wrote:
>> I'm +0 for now.
>> My concern is that YETUS-318-website.patch seems not to be included
>> this RC. Should we merge this?
>> If it's unnecessary, I'm +1 (binding). I checked the followings:
>>
>
>
> ... interesting. This comes down to what we want in our release
> process, I think. The post-release-vote website changes always go into
> some future minor release, by virtue of our current instructions. That
> means if we want to be able to cut maintenance releases off of the
> prior minor release we have to either
>
> 1) accept that you can't build a correct website off of the
> maintenance release source
>
> 2) backport needed website changes onto the maintenance branch
>
> I lean towards #1 just as a matter of logistics. For example, Say
> 0.2.2 is made after we've had a 0.3.0 release. Would I backport both
> the change for 0.2.1's release and 0.3.0's? When 0.3.1 comes out do I
> backport the notice for 0.2.2? Do we do this for every release that's
> happened since the last maintenance release? Are we setting ourselves
> up for an ever-increasing amount of work then?
>
> On the other hand, we could just have a step of copying the files that
> change with a successful release directly from then-current master.
> That would get all of the changes without needing to go searching for
> the individual commits. HBase does this for docs and it works okay.



-- 
Kengo Seki <sek...@apache.org>

Re: [VOTE] Apache Yetus 0.2.1-RC1

[Kengo Seki]

I'm +0 for now.
My concern is that YETUS-318-website.patch seems not to be included
this RC. Should we merge this?
If it's unnecessary, I'm +1 (binding). I checked the followings:

- Verified signatures and checksums for all distribution artifacts.
- Reviewed LICENSE and NOTICE.
- Reviewed CHANGES.md and (empty) RELEASENOTES.md.
- Built successfully from source.
- Manually tested test-patch on Hadoop and HBase.

2016-04-04 9:36 GMT+09:00 Sean Busbey <bus...@apache.org>:
>
> Hi Folks!
>
> I am pleased to announce the first release candidate for Apache Yetus 0.2.1
>
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.2.1-RC1/
>
> As of this vote the relevant md5 hashes are:
>
> 427b0e685dca43f51a43ef45f49237ae  CHANGES.md
> 17ec8e87a994b3ee86db7b62f4e827fd  RELEASENOTES.md
> 479d71d3347634c348d43dc414cdbb3d  yetus-0.2.1-bin.tar.gz
> 35a24fa81b1cdd4966d7d77e1dd767f1  yetus-0.2.1-src.tar.gz
>
> Source repository commit:
>
> 07cfe2ece72e382d2a9df258bdbaab22e6e8624b
>
>
> Our KEYS file is at: https://dist.apache.org/repos/dist/release/yetus/KEYS
> All artifacts are signed with my key (0D80DB7C)
>
> This is a maintenance release meant to fix the following errors in 0.2.0:
>
> * [YETUS-334] - mvn dependency ordering generates duplicates
>
> Please see the list of all resolved issues in the JIRA release notes:
>
> http://s.apache.org/yetus-0.2.1-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.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Vote will be subject to Majority Approval[2] and will close at 1:00AM
> UTC on Wednesday, Apr 7th, 2016[3].
>
> [1]: http://yetus.apache.org/contribute/releases/#verification
> [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.1-rc1-close

-- 
Kengo Seki <sek...@apache.org>

Re: RM volunteer for 0.3.0?

[Kengo Seki]

I'm also +1 for the 0.2.1 proposal.

2016-03-22 2:55 GMT+09:00 Chris Nauroth <cnaur...@hortonworks.com>:

> +1 for the 0.2.1 proposal.
>
> Thanks also to Kengo for volunteering to do the next one.
>
> --Chris Nauroth
>
>
>
>
> On 3/21/16, 8:20 AM, "Sean Busbey" <bus...@apache.org> wrote:
>
> >Would anyone mind if I made a 0.2.1 release while Kengo works on
> >getting 0.3.0 out at the end of the week?
> >
> >It'd just be 0.2.0 plus the fix for YETUS-334. It's severely bloating
> >HBase's precommit build times (like adding ~2 hours).
> >
> >On Sun, Mar 20, 2016 at 5:40 PM, Kengo Seki <sek...@gmail.com> wrote:
> >> Sorry for the late response, but could you let me try it?
> >> If it's OK, I'd like to create a RC by the next weekend, because I need
> >> some preparation such as reading relevant docs and some trial-and-error,
> >> and I think YETUS-329 and YETUS-338 should be committed before creating
> >>a
> >> RC (I'll review them today).
> >>
> >> 2016-03-19 0:30 GMT+09:00 Sean Busbey <bus...@apache.org>:
> >>
> >>> Now that YETUS-334 and YETUS-335 are in place, I'd like there to be a
> >>> release in short order.
> >>>
> >>> I believe I owe Andrew W a review and compatibility addendum on
> >>> YETUS-326, which I'd prefer to get in today so that it can be in a
> >>> soon-release.
> >>>
> >>> I also owe Allen a fix for YETUS-328, but that should be doable this
> >>> morning.
> >>>
> >>> Anyone willing to volunteer as RM with time late today / this weekend?
> >>> I'm told that the guide is pretty easy to follow. ;)
> >>>
> >>> -Sean
> >>>
> >>
> >>
> >>
> >> --
> >> Kengo Seki <sek...@gmail.com>
> >
>
>


-- 
Kengo Seki <sek...@gmail.com>

Re: [VOTE] Apache Yetus 0.2.0-RC1

[Kengo Seki]

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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15173852


2016-03-02 4:11 GMT+09:00 Chris Nauroth <cnaur...@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" <a...@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 <sek...@gmail.com>

Re: [DRAFT] [REPORT] Apache Yetus

[Kengo Seki]

+1

2015-12-10 15:42 GMT+09:00 Sean Busbey <bus...@apache.org>:

> Hi folks!
>
> Here's our draft report.
>
> -
>
> Attachment BP: Report from the Apache Yetus Project  [Sean Busbey]
>
> Apache Yetus provides libraries and tools that enable contribution and
> release processes for software projects.
>
> ISSUES FOR THE BOARD'S ATTENTION
>
> None at this time.
>
> RELEASES
>
> None to date.
>
> ACTIVITY
>
> No new PMC additions in the past three months.
>
> Last PMC addition was formation on September 16, 2015.
>
> Added new committer Kengo Seki on December 01, 2015.
>
> The community is closing in on our first release. We've cleared up
> several issues found during testing and are coming to consensus on a
> temporary build process for release artifacts.
>
> Mailing list traffic is very low, with most project activity on the issue
> tracker. Folks showed up on the list just fine for the announcement of our
> committer, so I presume things will shift back to the list as we need to
> discuss project direction.
>
> STATS
>
> - Currently 6 PMC members
> - Currently 7 committers
> - dev list has 23 subscribers (up 23 in the last 3 months)
> - 177 JIRA tickets created in the last 3 months
> - 109 JIRA tickets closed/resolved in the last 3 months
>



-- 
Kengo Seki <sek...@gmail.com>