Skip to content

Latest commit

 

History

History
41 lines (31 loc) · 1.73 KB

release-process.md

File metadata and controls

41 lines (31 loc) · 1.73 KB

Release process

The web document is always the latest version that has been accepted via the pull request process.

If major or significant minor changes are made then it is good to tag this with a semantic version, such as 4.1.8.

To do this:

  1. Ensure that all pull-requests are up to date
  2. navigate to the release area
  3. Click on the 'Draft a new release' button to create a new release
  4. Choose a tag, for example v4.1.8 and select target branch to be 'main'
  5. Provide the release title, such as 'Version 4.1.8'
  6. Describe the release in the Description, consider including the text below
  7. Obtain the latest PDF file form the latest (successful) commit action
  8. Upload this PDF file to the draft release
  9. Ensure 'Set as the latest release' is selected
  10. Apply 'Publish release'
  11. Announce on the #project-developer-guide Slack channel
  12. Announce on the Blue Sky channel
Contact the current [leaders][leaders] for any queries about this version.

The [PDF][pdf-guide] version of the [web document][devguide] can be downloaded for version 4.1.8 .

[devguide]: devguide.owasp.org
[leaders]: https://github.com/OWASP/www-project-developer-guide/blob/main/leaders.md
[pdf-guide]: https://github.com/OWASP/DevGuide/releases/download/vx.x.x/OWASP_Developer_Guide-Vx.x.x.pdf

OWASP DevGuide: accessible security for developers