[VOTE] Release Apache Traffic Server 7.1.0 (RC0)

[Leif Hedstrom]

I've prepared a release for 7.1.0 (RC0) which is the next major version of Apache Traffic Server. As per our new release schedule and process, v7.1.x is an Long-Term Support (LTS) release. This is detailed in our Release Management document:

https://cwiki.apache.org/confluence/display/TS/Release+Management


Release notes for 7.1.0:

https://github.com/apache/trafficserver/milestone/2?closed=1


This release of v7.1.0 is backwards compatible with v7.0.0, for some details as to what’s in v.7.1.x see

https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+v7.1.x


Information about upgrading to this release from previous major versions is available at:

https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v7.0

The artifacts are available for download at:

http://people.apache.org/~zwoop/rel-candidates/


Checksums:

MD5: e91212248af3ef6da9519025fc8b39a5 *trafficserver-7.1.0-rc0.tar.bz2
SHA1: d98907215a2ccae59882d9c2d65543505268ee18 *trafficserver-7.1.0-rc0.tar.bz2


This corresponds to git:

Hash: bbfd439ee6cd7f5cc3abf8daafe447b61df91481
Tag: 7.1.0-rc0


Which can be verified with the following command:

$ git tag -v 7.1.0-rc0


All code signing keys are available here:

https://dist.apache.org/repos/dist/dev/trafficserver/KEYS

Make sure you refresh from a key server to get all relevant signatures. This vote is open until July 20th..

Cheers,

— Leif

[Phillip Moore]

+1

We have found 7.1.0 to be tremendously better at handling SSL/POST
(uploads). There are fewer failures and the speed of uploads has improved
30-40% over 6.2.1.

Post by Leif Hedstrom
I've prepared a release for 7.1.0 (RC0) which is the next major version of
Apache Traffic Server. As per our new release schedule and process, v7.1.x
is an Long-Term Support (LTS) release. This is detailed in our Release
https://cwiki.apache.org/confluence/display/TS/Release+Management
https://github.com/apache/trafficserver/milestone/2?closed=1
This release of v7.1.0 is backwards compatible with v7.0.0, for some
details as to what’s in v.7.1.x see
https://cwiki.apache.org/confluence/display/TS/What%
27s+New+in+v7.1.x
https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v7.0
http://people.apache.org/~zwoop/rel-candidates/
MD5: e91212248af3ef6da9519025fc8b39a5
*trafficserver-7.1.0-rc0.tar.bz2
SHA1: d98907215a2ccae59882d9c2d65543505268ee18
*trafficserver-7.1.0-rc0.tar.bz2
Hash: bbfd439ee6cd7f5cc3abf8daafe447b61df91481
Tag: 7.1.0-rc0
$ git tag -v 7.1.0-rc0
https://dist.apache.org/repos/dist/dev/trafficserver/KEYS
Make sure you refresh from a key server to get all relevant signatures.
This vote is open until July 20th..
Cheers,
— Leif

[Susan Hinrichs]

+1    I have run this on two machines over the weekend successfully.

On Thursday, July 13, 2017, 9:44:34 PM CDT, Leif Hedstrom <***@apache.org> wrote:

I've prepared a release for 7.1.0 (RC0) which is the next major version of Apache Traffic Server. As per our new release schedule and process, v7.1.x is an Long-Term Support (LTS) release.  This is detailed in our Release Management document:

    https://cwiki.apache.org/confluence/display/TS/Release+Management


Release notes for 7.1.0:

    https://github.com/apache/trafficserver/milestone/2?closed=1


This release of v7.1.0 is backwards compatible with v7.0.0, for some details as to what’s in v.7.1.x see

    https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+v7.1.x


Information about upgrading to this release from previous major versions is available at:

    https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v7.0

The artifacts are available for download at:

    http://people.apache.org/~zwoop/rel-candidates/


Checksums:

    MD5: e91212248af3ef6da9519025fc8b39a5 *trafficserver-7.1.0-rc0.tar.bz2
    SHA1: d98907215a2ccae59882d9c2d65543505268ee18 *trafficserver-7.1.0-rc0.tar.bz2


This corresponds to git:

    Hash: bbfd439ee6cd7f5cc3abf8daafe447b61df91481
    Tag: 7.1.0-rc0


Which can be verified with the following command:

    $ git tag -v 7.1.0-rc0


All code signing keys are available here:

    https://dist.apache.org/repos/dist/dev/trafficserver/KEYS

Make sure you refresh from a key server to get all relevant signatures. This vote is open until July 20th..

Cheers,

— Leif

[Mohd Akhbar]

+1 on CentOS as forward proxy. Seems better response. No numbers to support
it though.

+1 I have run this on two machines over the weekend successfully.
On Thursday, July 13, 2017, 9:44:34 PM CDT, Leif Hedstrom <
I've prepared a release for 7.1.0 (RC0) which is the next major version of
Apache Traffic Server. As per our new release schedule and process, v7.1.x
is an Long-Term Support (LTS) release. This is detailed in our Release
https://cwiki.apache.org/confluence/display/TS/Release+Management
https://github.com/apache/trafficserver/milestone/2?closed=1
This release of v7.1.0 is backwards compatible with v7.0.0, for some
details as to what’s in v.7.1.x see
https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+v7.1.x
https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v7.0
http://people.apache.org/~zwoop/rel-candidates/
MD5: e91212248af3ef6da9519025fc8b39a5 *trafficserver-7.1.0-rc0.tar.bz2
SHA1: d98907215a2ccae59882d9c2d65543505268ee18
*trafficserver-7.1.0-rc0.tar.bz2
Hash: bbfd439ee6cd7f5cc3abf8daafe447b61df91481
Tag: 7.1.0-rc0
$ git tag -v 7.1.0-rc0
https://dist.apache.org/repos/dist/dev/trafficserver/KEYS
Make sure you refresh from a key server to get all relevant signatures.
This vote is open until July 20th..
Cheers,
— Leif

[Masaori Koshiba]

-1 - Memory leak is found around HTTP/2 Server Push API. IMO, we should
backport PR #2276, because it looks like many people are interested in
using HTTP/2 Server Push API in production.

https://github.com/apache/trafficserver/pull/2276

- Masaori

+1 I have run this on two machines over the weekend successfully.
On Thursday, July 13, 2017, 9:44:34 PM CDT, Leif Hedstrom <
I've prepared a release for 7.1.0 (RC0) which is the next major version of
Apache Traffic Server. As per our new release schedule and process, v7.1.x
is an Long-Term Support (LTS) release. This is detailed in our Release
https://cwiki.apache.org/confluence/display/TS/Release+Management
https://github.com/apache/trafficserver/milestone/2?closed=1
This release of v7.1.0 is backwards compatible with v7.0.0, for some
details as to what’s in v.7.1.x see
https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+v7.1.x
https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v7.0
http://people.apache.org/~zwoop/rel-candidates/
MD5: e91212248af3ef6da9519025fc8b39a5 *trafficserver-7.1.0-rc0.tar.bz2
SHA1: d98907215a2ccae59882d9c2d65543505268ee18
*trafficserver-7.1.0-rc0.tar.bz2
Hash: bbfd439ee6cd7f5cc3abf8daafe447b61df91481
Tag: 7.1.0-rc0
$ git tag -v 7.1.0-rc0
https://dist.apache.org/repos/dist/dev/trafficserver/KEYS
Make sure you refresh from a key server to get all relevant signatures.
This vote is open until July 20th..
Cheers,
— Leif

[Leif Hedstrom]

-1 - Memory leak is found around HTTP/2 Server Push API. IMO, we should backport PR #2276, because it looks like many people are interested in using HTTP/2 Server Push API in production.
https://github.com/apache/trafficserver/pull/2276 <https://github.com/apache/trafficserver/pull/2276>

Thanks! I’ll make a new RC today, please vote again if you already voted, and thanks to everyone for testing and voting on this RC.

Cheers,

— leif

[Leif Hedstrom]

-1 build error centos6
/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: /usr/lib64/libunwind-ptrace.a(_UPT_elf.o): undefined reference to symbol 'lzma_index_size'
/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: note: 'lzma_index_size' is defined in DSO /usr/lib64/liblzma.so.0 so try adding it to the linker command line
/usr/lib64/liblzma.so.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[2]: *** [traffic_manager] Error 1
make[2]: Leaving directory `/data/rpmbuild/BUILD/ts-7.1.0/cmd/traffic_manager'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/rpmbuild/BUILD/ts-7.1.0/cmd'
make: *** [all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.ZC36Sj (%build)

What platform is this ? It sounds like something is broken in your installation? Do you see this with RC1 as well?

— Leif

[Bryan Call]

Did configure detect zma?

This is the information from my config.log:
16:30:47 mac:~/tmp/trafficserver-7.1.0$ grep zma config.log
configure:25623: checking for lzma location
configure:25735: checking for lzma_code in -llzma
configure:25760: ccache clang -o conftest -Werror -std=gnu99 -g -pipe -Wall -Wno-deprecated-declarations -Qunused-arguments -Wextra -Wno-ignored-qualifiers -Wno-unused-parameter -O3 -fno-strict-aliasing -Ddarwin -D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -D__STDC_LIMIT_MACROS=1 -D__STDC_FORMAT_MACROS=1 -I/usr/local/Cellar/openssl/1.0.2j/include -DOPENSSL_NO_SSL_INTERN -I/usr/local/include -L/opt/local/lib -L/usr/local/Cellar/openssl/1.0.2j/lib -L/usr/local/lib conftest.c -llzma >&5
configure:25778: checking lzma.h usability
configure:25778: checking lzma.h presence
configure:25778: checking for lzma.h
ac_cv_header_lzma_h=yes
ac_cv_lib_lzma_lzma_code=yes
ats_cv_lzma_dir=/usr/local
LIBLZMA='-llzma'
lzmah='0'

-1 build error centos6
/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: /usr/lib64/libunwind-ptrace.a(_UPT_elf.o): undefined reference to symbol 'lzma_index_size'
/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: note: 'lzma_index_size' is defined in DSO /usr/lib64/liblzma.so.0 so try adding it to the linker command line
/usr/lib64/liblzma.so.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[2]: *** [traffic_manager] Error 1
make[2]: Leaving directory `/data/rpmbuild/BUILD/ts-7.1.0/cmd/traffic_manager'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/rpmbuild/BUILD/ts-7.1.0/cmd'
make: *** [all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.ZC36Sj (%build)
------------------ 原始邮件 ------------------
发送时闎: 2017幎7月18日(星期二) 䞊午8:15
䞻题: Re: [VOTE] Release Apache Traffic Server 7.1.0 (RC0)
-1 - Memory leak is found around HTTP/2 Server Push API. IMO, we should backport PR #2276, because it looks like many people are interested in using HTTP/2 Server Push API in production.
https://github.com/apache/trafficserver/pull/2276
- Masaori
+1 I have run this on two machines over the weekend successfully.
https://cwiki.apache.org/confluence/display/TS/Release+Management
https://github.com/apache/trafficserver/milestone/2?closed=1
This release of v7.1.0 is backwards compatible with v7.0.0, for some details as to what’s in v.7.1.x see
https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+v7.1.x
https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v7.0
http://people.apache.org/~zwoop/rel-candidates/
MD5: e91212248af3ef6da9519025fc8b39a5 *trafficserver-7.1.0-rc0.tar.bz2
SHA1: d98907215a2ccae59882d9c2d65543505268ee18 *trafficserver-7.1.0-rc0.tar.bz2
Hash: bbfd439ee6cd7f5cc3abf8daafe447b61df91481
Tag: 7.1.0-rc0
$ git tag -v 7.1.0-rc0
https://dist.apache.org/repos/dist/dev/trafficserver/KEYS
Make sure you refresh from a key server to get all relevant signatures. This vote is open until July 20th..
Cheers,
— Leif

[Leif Hedstrom]

Post by Leif Hedstrom
https://cwiki.apache.org/confluence/display/TS/Release+Management

This vote fails, with a valid -1, will do a new vote momentarily.

— Leif