1 Adding or modifying code:
2 =========================
3 - If you add new code, best practice is to write a test for it.
4 - If you're modifying code that doesn't have a test and you can write a test
6 - Before committing your changes to a python file, please make sure it passes
8 pylint --rcfile=pylintrc yourfile.py
9 - If pylint raises a warning or error that you don't agree with, it's probably
10 better to just change your code. If you're sure you have a good reason for
11 doing what you're doing, you can add an exception to our pylintrc.
15 Note: We are using VERSION="0.3.0" simply as an example.
17 - Run Gentoolkit's test suite, make sure it passes:
18 Note: requires dev-python/snakeoil
21 - Create a tag for the release
22 svn copy svn+ssh://<dev>@svn.gentoo.org/var/svnroot/gentoolkit/trunk/gentoolkit \
23 svn+ssh://<dev>@svn.gentoo.org/var/svnroot/gentoolkit/tags/gentoolkit-0.3.0 \
24 -m "Tagging the <VERSION> release of gentoolkit."
25 svn update to pull the tag from subversion
26 cd to the local tags/gentoolkit-0.3.0 directory
28 - Create a source distribution (you need to add VERSION here):
29 VERSION="0.3.0" ./setup.py sdist
30 Transfer dist/gentoolkit-0.3.0.tar.gz to dev.gentoo.org:/space/distfiles-local
32 - Clean up temporary files: