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...@apache.org> on 2020/11/02 21:26:09 UTC
[VOTE] Apache Yetus 0.13.0-RC2
Let's try this release again...
*** NOTE ***
This release is huge, potentially the biggest one we've done since project launch. There are a lot of changes, many incompatible. There is a lot of new/reworked documentation. Please plan on spending some time with it, as this one will almost certainly not be a drop-in replacement.
Thanks.
=================================
Artifacts are available:
https://dist.apache.org/repos/dist/dev/yetus/0.13.0-RC2/
As of this vote the relevant sha512 hashes are:
SHA512 (apache-yetus-0.13.0-bin.tar.gz) = 6dd20a904c9926d82cd2913931e8c052e31211643fac2f786ae1d90d3213275b226bca226ae49a3e5502458d267bff3bfc3bd1f880c8f60bdea1f1b4a7175298
SHA512 (apache-yetus-0.13.0-site.tar.gz) = 36ceb4ba0e25a6d5ad4ccb02b710b139e03080d72b557bcf26a6075f5d0247bf1537610ac93822ad6c34e7ba53d553cd8fb0dad5c6e4dc60efc7a9872d6d18bd
SHA512 (apache-yetus-0.13.0-src.tar.gz) = 090e8748a871b371212cc6c2aa5bbf5c78269d87fd36d3719f2470e94c7fdb6183908fded3426643e52d9e9067351dd4ceb708e490005627e63be827d19005ee
SHA512 (CHANGELOG.md) = eb1e372e87a30708407de93a0295872e9d1054c82e54b2a89dada9cacd49fd6921cbd567b1b09784fda644dbf353ff9106e59937a40a9ce6111d428d743bc3a5
SHA512 (RELEASENOTES.md) = 916370e07803a5b7e0748ed587afe097f0cb02d11b852aad2a6c942a588d38e355825cc55c26349d63b6f8278782b008f9b853f11417a76be03cd17faf6c673c
Source repository commit: 05fa92948d73d10aac07ed5c11b35c50d4aee4f3
Maven staging repository: https://repository.apache.org/content/repositories/orgapacheyetus-1026
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.13.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.13.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...
The vote will be subject to Majority Approval[2] and will close minimally at 20:00
UTC on Saturday, November 7th, 2020[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/apache-yetus-0.13.0-rc2-close
Re: [VOTE] Apache Yetus 0.13.0-RC2
Posted by Allen Wittenauer <aw...@apache.org>.
> On Nov 3, 2020, at 3:25 PM, Allen Wittenauer <aw...@apache.org> wrote:
>
>
>
>> On Nov 3, 2020, at 8:41 AM, Allen Wittenauer <aw...@apache.org> wrote:
>> Luckily, these are all relatively easy fixes so I should have a patch later today.
>
> A little harder than expected, but nonetheless:
>
> https://github.com/apache/yetus/pull/193/
I'm going to merge this in so main and the release branch works properly for my edge case test bed. If someone has an issue with that, let me know and I'll revert it.
Re: [VOTE] Apache Yetus 0.13.0-RC2
Posted by Allen Wittenauer <aw...@apache.org>.
> On Nov 3, 2020, at 8:41 AM, Allen Wittenauer <aw...@apache.org> wrote:
> Luckily, these are all relatively easy fixes so I should have a patch later today.
A little harder than expected, but nonetheless:
https://github.com/apache/yetus/pull/193/
Re: [VOTE] Apache Yetus 0.13.0-RC2
Posted by Allen Wittenauer <aw...@apache.org>.
-1
In addition to some harmless curl output that was inadvertently left in, at $DAYJOB we hit three issues on a particularly complicated build (multiple repos checked out, multiple GitHub credentials involved, Jenkins shared libraries, ... basically all the things):
* if GITHUB_REPO isn't properly defined or auto-discovered but the GitHub plug-in is enabled, all hell breaks loose and the user has no idea why.
* For source trees with thousands of problems, performance just dies in the GitHub Checks Annotations REST calls that makes you think everything fell apart. I clearly need to enforce a limit here. Sending them all is not viable.
* Non-GitHub Actions annotations don't have the plug-in where they came from. Users found that very confusing in some circumstances because the context was helpful, especially for systems like golangci-lint vs. revive.
On the plus side, using Docker's BuildKit has definitely been noticeable for our multi-stage Dockerfiles.
Luckily, these are all relatively easy fixes so I should have a patch later today. It'd be great if someone who still works on ASF builds could still go ahead and test this RC sooner rather than later.
Thanks.