Skip to content
This repository was archived by the owner on May 14, 2020. It is now read-only.

Release Procedure

Walter Hop edited this page Aug 2, 2017 · 26 revisions

Step by Step Guide Through CRS release

  • Update CHANGES File
  • Add new contributors to CONTRIBUTORS.md (e.g. git shortlog -s v3.0.1..v3.0/dev)
  • Update copyright in all the files if there is a new year
  • Update CRS version in crs-setup.conf.example (tx.crs_setup_version) and rules/REQUEST-901-INITIALIZATION.conf (SecComponentSignature)
  • Update CRS version in all rules, e.g. ver:'OWASP_CRS/3.0.0'
  • Update all copyright for new versions
grep -rl "OWASP ModSecurity Core Rule Set ver\.3\.0\.0" owasp-modsecurity-crs/ | xargs sed -i s@"OWASP ModSecurity Core Rule Set ver\.3\.0\.0"@"OWASP ModSecurity Core Rule Set ver\.3\.0\.2"@g
  • Merge dev to master tree
  • Run tests. Make sure that a vanilla request does not trigger any rules due to messup (problem with 3.0.1 release)
  • Tag release
  • Finish release message
  • Send release message to crs mailinglist
  • Crosspost release message to modsec mailinglist
  • Tweet about release with ModSecurity twitter account
  • Update website with new version
  • Update OWASP project page with new version

Clone this wiki locally