adding release verification check for crypto export control
Project: http://git-wip-us.apache.org/repos/asf/incubator-pirk/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-pirk/commit/06616038 Tree: http://git-wip-us.apache.org/repos/asf/incubator-pirk/tree/06616038 Diff: http://git-wip-us.apache.org/repos/asf/incubator-pirk/diff/06616038 Branch: refs/heads/gh-pages Commit: 066160386aa62da01eb181cd047d5cbb0137ba8a Parents: 38b4cc1 Author: eawilliams <eawilli...@apache.org> Authored: Fri Aug 26 09:22:34 2016 -0400 Committer: eawilliams <eawilli...@apache.org> Committed: Fri Aug 26 09:22:34 2016 -0400 ---------------------------------------------------------------------- releasing.md | 1 + 1 file changed, 1 insertion(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-pirk/blob/06616038/releasing.md ---------------------------------------------------------------------- diff --git a/releasing.md b/releasing.md index bb92b28..12bba23 100755 --- a/releasing.md +++ b/releasing.md @@ -124,6 +124,7 @@ As per the Apache documentation, verify that the release candidate artifacts sat * [NOTICE file requirements](http://www.apache.org/dev/release.html#notice-content) * [Apache Legal](http://apache.org/legal/) * [Acceptable](http://www.apache.org/legal/resolved.html#category-a) and [Unacceptable](http://www.apache.org/legal/resolved.html#category-x) Dependency Licenses +* The Cryptographic Export Control section in the README is up-to-date * All source files have license headers where appropriate, RAT checks pass * The provenance of all source files is clear (ASF or software grants)
