Yes, the documentation needs updating before the release is finalized. -Bryan
> On Sep 15, 2015, at 8:14 AM, Igor Galić <i.ga...@brainsware.org> wrote: > > > > Bryan, > > ----- On 15 Sep, 2015, at 00:53, Bryan Call bc...@apache.org wrote: > >> I've prepared a release for 6.0.0 (RC3) which is the next major version of >> Apache Traffic Server. This version breaks binary compatibility and plugins >> will need to be recompiled. This is detailed in our Release Management >> document: > > it's not clear from any of the links below how / why / where we're breaking > binary compatiblity. > > -- i > >> https://cwiki.apache.org/confluence/display/TS/Release+Management >> >> Release notes for 6.0.0: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324897&styleName=&projectId=12310963 >> >> A summary of the new features in 6.0.0 are here: >> >> https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+6.0.x >> >> Information about upgrading to this release from previous ones is available >> at: >> >> https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v6.0 >> >> The cache in this release is compatible with the previous 5.x and 4.x >> releases. >> >> The artifacts are available for download at: >> >> https://people.apache.org/~bcall/6.0.0-rc3/ >> >> MD5: 4713f41adea06521078aefda77686c6e >> SHA1: ca4316f4fb08986099e5e878ae2f035f963b8212 >> >> This corresponds to git: >> >> Hash: 27f8e2cda9133864e6ffae0224c799fde5f10290 >> Tag: 6.0.0-rc3 >> >> Which can be verified with the following: >> >> git tag -v 6.0.0-rc3 >> >> My code signing key is available here: >> >> http://people.apache.org/~bcall/gpg-code-signing-key.asc >> >> Make sure you refresh from a key server to get all relevant signatures. >> >> The vote is open until Wednesday Sept 16th, 2015. >> >> Thank you >> >> -Bryan > > -- > Igor Galić > > Tel: +43 (0) 664 886 22 883 > Mail: i.ga...@brainsware.org > URL: https://brainsware.org/ > GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641
