Thanks to all who voted!
The release has PASSED with the following PMC votes:
+1 Dave Neuman (binding)
+1 Jeremy Mitchell (binding)
+1 Rob Butts (binding)
I will proceed to publish the release and send ANNOUNCE.
On behalf of Apache Traffic Control, thank you!
Regards,
Rawlin Peters raw...@apac
+1
I verified:
- the sha512 matches
- signature matches and is valid
- CiaB comes up and serves the demo file, TP UI comes up and appears to
generally work, TM UI comes up and shows polled caches as available.
- unit tests for TO,TM,ORT/atstccfg,lib pass.
- generating ATS config from CiaB seems to
Has anyone else had the change to test this release? This vote has been
open for almost a month and a half and we have only gotten two votes.
I would love you see our community make testing this release candidate (and
future release candidates) a priority so that we can get these out. I know
this
+1 on 4.0.0 RC4 based on the extensive validation we've done on it
internally at Comcast. We've validated all the changes introduced since 3.1
as well as some basic regression testing.
Jeremy
On Sat, Feb 22, 2020 at 9:15 AM Dan Kirkwood wrote:
> that file is created during creation of the tarba
that file is created during creation of the tarball. It only exists
because the build number is calculated from the git history, so can't be
calculated from the tarball
Certainly wouldn't hurt to have that noted as a file weasel should ignore..
On Fri, Feb 21, 2020 at 3:19 PM Chris Lemmons
Yup. It's _only_ a problem on the actual release tarball. You don't
need that file if you're checking out from git. That's why none of the
tools caught it, but Dave did. He was testing against the proposed
release.
On Fri, Feb 21, 2020 at 3:12 PM Rawlin Peters wrote:
>
> Oh, it's probably just an
Oh, it's probably just an artifact from building the tarball -- the
asf-ci build job checks out 4.0.x in git and builds from there.
- Rawlin
On Fri, Feb 21, 2020 at 3:08 PM Rawlin Peters wrote:
>
> That's strange, because the asf-ci build job for 4.0.x doesn't have
> any weasel issues:
> https:/
That's strange, because the asf-ci build job for 4.0.x doesn't have
any weasel issues:
https://builds.apache.org/view/S-Z/view/TrafficControl/job/trafficcontrol-4.0.x-build/18/artifact/dist/weasel.txt
- Rawlin
On Fri, Feb 21, 2020 at 3:00 PM Chris Lemmons wrote:
>
> The weasel is reporting that
The weasel is reporting that BUILD_NUMBER does not have a license
header and it's not declared with a license in the dependency_license
file. Since BUILD_NUMBER is very small and not code, it can survive
without the header. I've opened up a fix here:
https://github.com/apache/trafficcontrol/pull/44
+1
I verified that sha512sum and signature. I was able to build all of the
components, but weasel failed for some reason. Since it's not critical to
running a CDN, I won't let that hold us up.
On Tue, Feb 11, 2020 at 9:42 AM Rawlin Peters wrote:
> Hello All,
>
> I've prepared a release for v4.
Hello All,
I've prepared a release for v4.0.0-RC4
The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PMC votes are cast.
[ ] +1 Approve the release
[ ] -1 Do not release this package because ...
Changes since 3.1.0:
https://github.com/apache/trafficcontrol/compare
11 matches
Mail list logo
