I’ll add to Dan’s -1 for the following reasons: From https://incubator.apache.org/guides/releasemanagement.html#check-list 1.1 Release artifacts don’t contains checksums or PGP signatures (just the git repo, which I don’t believe is a valid release artifact) 3.3 Some source files missing License Headers (see some partial RAT results here https://cwiki.apache.org/confluence/display/TC/Incubator+Release+Goals) 3.4 Provenance of some source files is not clear (i.e. they bundled dependencies and its not obvious their license or source) 3.5 I’ve got a question on our ability to bundle Perl modules (Net/IPv6.pm and JSON.pm) They are under either the GPL or Artistic License, and it doesn’t look like apache can rely on those licenses per this page: https://www.apache.org/legal/resolved#category-x 3.6 Release artifacts do not contain source code sufficient to build Traffic Control. Specifically we’re missing SRPMS for TM and Router. No release artifact for astats either. 3.6a) RPMs are a rather platform dependent form of packaging. Do we want to be providing a more generic (i.e. tgz) formatted source bundle that could be built on non Centos/RedHat Lines?
Also: - “incubating” is not in the artifact name (https://incubator.apache.org/guides/releasemanagement.html#check-list, search for Naming). - We should probably have “traffic_control” in the name too for clarity? - Release artifacts don’t contain documentation (could be fixed with a .tgz) - MySQL is a required dependency but is a prohibited license type. —Eric On Nov 3, 2016, at 1:35 PM, Dan Kirkwood <[email protected]<mailto:[email protected]>> wrote: I forgot to mention the download location for built rpm's.. They can be found here: https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC0/ And I must -1 already because of https://issues.apache.org/jira/browse/TC-23 -Dan On Thu, Nov 3, 2016 at 11:25 AM, Dan Kirkwood <[email protected]> wrote: Hello All, I've prepared a release for v1.8.0 (RC0) Changes since 1.7.0: https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC0 This corresponds to git: Hash: eca09c597ce9db2e050fc216a36aa6c816455aa6 Tag: RELEASE-1.8.0-RC0 Which can be verified with the following: git tag -v RELEASE-1.8.0-RC0 My code signing key is available here: http://keys.gnupg.net/pks/lookup?search=0x6F7762B8&op=vindex Make sure you refresh from a key server to get all relevant signatures. The vote is open until Thursday, November 10, 2016. Thanks!
