-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Shipping a new release
The steps for building a new distributable package change a lot depending on the target operating system. That's why we've split this document into the different platforms:
Only core w3af developers and package maintainers (like Debian, Fedora, FreeBSD package maintainers) will find this section useful, these are the main steps that we'll go through:
- Create the release branch
- Set release version
- Update the CHANGELOG file
- Create the source code documentation using Sphinx
- Create distributable package
- Upload the files to w3af.org
- Run final
git flowcommands - Community tasks related to a release
Choose a version number and then run the following command:
git flow release start <version-number>
Setting the version for the next release is trivial, just change the core/data/constants/version.txt file to the required version.
Each release is associated with a milestone, when updating the readme/CHANGELOG use the issues in the milestone as a source for the CHANGELOG.
(15 Feb 2013) Version 1.5
============================
Github tag: https://github.com/andresriancho/w3af/tree/1.5
Github milestone: https://github.com/andresriancho/w3af/issues?milestone=2
* Change A
* Change B
...
* Change N
- Run Sphinx
- Upload the generated code to w3af.org
scp w3af-v1.5.bz2 [email protected]:/var/www/...
scp w3af-v1.5.bz2.md5sum [email protected]:/var/www/...And update the downloads page in w3af.org.
Run these commands to merge the release branch into master and tag it.
git flow release finish
git flow release publish <version-number> - "Tagging the 1.5 release of the w3af project."
Let the community know about this new release!
- Send an email to w3af-users and w3af-develop
- Create a new blog entry to http://www.w3af.org/
- Send an email to full-disclosure
- Tweet about it