Set version number for next release (2.0.9)

Change the version number *now*, before release, so that we won't
accidentally release software with a duplicate version number later.
Also, tweak the release_process.md documentation to clarify a few things.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
This commit is contained in:
David A. Wheeler 2019-01-21 18:54:01 -05:00
parent f5dac7d8d7
commit e4f4d4a34b
5 changed files with 29 additions and 9 deletions

View File

@ -55,7 +55,7 @@ import csv # To support generating CSV format
import hashlib import hashlib
# import formatter # import formatter
version = "2.0.8" version = "2.0.9"
# Program Options - these are the default values. # Program Options - these are the default values.
# TODO: Switch to boolean types where appropriate. # TODO: Switch to boolean types where appropriate.

View File

@ -1,6 +1,6 @@
Name: flawfinder Name: flawfinder
Summary: Examines C/C++ source code for security flaws Summary: Examines C/C++ source code for security flaws
Version: 2.0.8 Version: 2.0.9
Release: 1%{?dist} Release: 1%{?dist}
License: GPLv2+ License: GPLv2+
Group: Development/Tools Group: Development/Tools

View File

@ -6,7 +6,7 @@
# how to change version numbers. # how to change version numbers.
NAME=flawfinder NAME=flawfinder
VERSION=2.0.8 VERSION=2.0.9
RPM_VERSION=1 RPM_VERSION=1
VERSIONEDNAME=$(NAME)-$(VERSION) VERSIONEDNAME=$(NAME)-$(VERSION)
ARCH=noarch ARCH=noarch

View File

@ -4,7 +4,7 @@ Here's information on how to release an update to flawfinder.
## Changing version number ## Changing version number
You should really change the version number before changing anything else. Ensure that the version number is the intended final value.
Make sure every release has a unique version number. Make sure every release has a unique version number.
To change version number, edit the following files: To change version number, edit the following files:
@ -12,7 +12,7 @@ makefile
flawfinder flawfinder
flawfinder.spec flawfinder.spec
setup.py setup.py
index.html index.html # in dwheeler.com/flawfinder
Then run: Then run:
@ -32,7 +32,8 @@ Once you're sure this is the *real* version, tag it:
~~~~ ~~~~
git tag VERSION git tag VERSION
git push --tags git push --tags origin # SourceForge
git push --tags github # GitHub
~~~~ ~~~~
## Create tarball ## Create tarball
@ -52,16 +53,35 @@ the usual places:
* SourceForge "files" directory, and set it to be the default download. * SourceForge "files" directory, and set it to be the default download.
* dwheeler.com/flawfinder * dwheeler.com/flawfinder
Do this *before* creating the PyPi distribution package for pip.
## Post to pip ## Post to pip
Create a PyPi distribution package: First, install the programs to create a PyPi distribution package
if they are not already installed. On Cygwin first run:
~~~~
python -m ensurepip
pip install --upgrade pip
pip install wheel
pip install twine
~~~~
Then create a PyPi distribution package (for Python2 and Python3):
~~~~ ~~~~
make pypi make pypi
~~~~ ~~~~
And upload it: Now upload the PyPi distribution package:
~~~~ ~~~~
make upload-pypi make upload-pypi
~~~~ ~~~~
## After it's uploaded
Change the version number in the repo NOW, so that there will not
be two different released versions with the same version number.
See the list at the beginning of this document for the list of
files to change.

View File

@ -9,7 +9,7 @@ from setuptools import setup # Don't need find_packages
setup (# Distribution meta-data setup (# Distribution meta-data
name = "flawfinder", name = "flawfinder",
version = "2.0.8", version = "2.0.9",
# We install a script, not a separate package. # We install a script, not a separate package.
# packages = ["flawfinder"], # Must be same as name # packages = ["flawfinder"], # Must be same as name
# Do not need: packages=find_packages(), # Do not need: packages=find_packages(),