There is an open bug on the release right now that has to deal with dealing 
header before caching the response from the origin:

https://issues.apache.org/jira/browse/TS-2564

We had 2 core dumps on it on one of the two severs I had it on in production.  
I have been in meetings a lot of the day today...

-Bryan



On Feb 4, 2014, at 2:00 PM, Phil Sorber <sor...@apache.org> wrote:

> Hello All,
> 
> I've prepared a release for v4.2.0 (RC0) which is the last stable release in 
> the 4.x series. This will serve as our Long Term Support (LTS) version as 
> detailed in our Release Management document:
> 
> https://cwiki.apache.org/confluence/display/TS/Release+Management
> 
> Changes since 4.1.0:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310963&version=12324892
> 
> A summary of the new features are here:
> 
> https://cwiki.apache.org/confluence/display/TS/What%27s+new+in+v4.2.x
> 
> Information about upgrading to this release from v3.2.x is available at:
> 
> https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v4.0
> 
> The cache in this release is compatible with the previous 4.0.x releases.
> 
> The artifacts are available for download at:
> 
> http://people.apache.org/~sorber/releases/trafficserver/4.2.0-rc0/
> 
> -rw-rw-r--  1 sorber  sorber  6380420 Feb  4 19:51 
> trafficserver-4.2.0-rc0.tar.bz2
> -rw-rw-r--  1 sorber  sorber      819 Feb  4 19:51 
> trafficserver-4.2.0-rc0.tar.bz2.asc
> -rw-rw-r--  1 sorber  sorber       66 Feb  4 19:51 
> trafficserver-4.2.0-rc0.tar.bz2.md5
> -rw-rw-r--  1 sorber  sorber       74 Feb  4 19:51 
> trafficserver-4.2.0-rc0.tar.bz2.sha1
> 
> MD5: 55f11f83155578fafe0911142f9a3e71
> SHA1: 1610669586161d37f75a72d05a92830a109a50ed
> 
> This corresponds to git:
> 
> Hash: d26cb39205ffc27e81a02c21c6e5a8c69a2bc09d
> Tag: 4.2.0-rc0
> 
> Which can be verified with the following:
> 
> git tag -v 4.2.0-rc0
> 
> My code signing key is available here:
> 
> http://people.apache.org/~sorber/gpg-code-signing-key.asc
> 
> Make sure you refresh from a key server to get all relevant signatures.
> 
> The vote is open until Feb 11th 2014 which is one week from today. This 
> release is going to be around for a long time, so make sure we test this 
> thoroughly!
> 
> Thanks All!

Reply via email to