Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Wiki
  • Pre Release checklist

Pre Release checklist · Changes

Page history
Updated Pre Release checklist (markdown) authored Nov 04, 2012 by Zapotek's avatar Zapotek
Show whitespace changes
Inline Side-by-side
Pre-Release-checklist.md
View page @ f3feb69b
This page serves as a pre-release check-list in order to make sure that there are no mishaps or left-over development-related code. This page serves as a pre-release check-list in order to make sure that there are no mishaps or left-over development-related code.
1. Bump version number: 1. Make sure there are no development dependencies in the ```Gemfile```.
2. ```rake``` -- To make sure all tests pass.
3. ```git flow release start v<version>```
4. Bump version number:
1. ```lib/version``` 1. ```lib/version```
2. ```README.md``` 2. ```README.md```
3. ```CHANGELOG.md``` 3. ```CHANGELOG.md```
2. Make sure there are no development dependencies in the ```Gemfile```. 5. Remove any dev-only, debugging, whatever code.
6. ```rake``` -- Make sure we didn't break anything.
7. ```git flow release finish -n v<version>``` -- ```-n``` tells git-flow not to tag.
6. ```rake``` -- Make sure the merge back to ```master``` didn't break anything.
9. ```rake release``` -- To tag, push the code and push the Gem.
Clone repository

Pages [all]


  • Home
  • Installation instructions
  • For users
    • Executables
    • Command Line Interface
    • Web User Interface
    • RPC Client
    • RPC Server (Dispatcher)
  • For developers
    • Coding guidelines
    • Core API documentation
    • RPC API
  • Technology
    • The Brains
    • Distributed components (Dispatchers and Instances)
    • High Performance Grid

Can't find what you're looking for? Why not have a look at the support portal?