Releases are versioned as $major.$minor$quality,
where $major indicates a substantial functional change,
$minor indicates bugfixes and small improvements, and
$quality values of a,b,rc indicate whether
a release is alpha quality (substantial changes still in progress,
liable to break, for geeks only), beta quality (unstable, but
changes are primarily bugfixes, for geeky testers),
release candidate quality (final testing before release),
respectively. Releases without a,b,rc are stable, production quality
releases.
The primary resource for source code changes is
the Monotone repository
at mtn.i2p2.de, as described on the
download page).
Installation packages for download are built with various ant targets:
syndie-installer-$version.bin.win$bits.exeant -Di2p.src.dir=../i2p.i2p installer-windows)syndie-installer-$version.bin.linux$bits.jarant -Di2p.src.dir=../i2p.i2p installer-windows)syndie-installer-$version.bin.osx$bits.jarant -Di2p.src.dir=../i2p.i2p installer-windows)syndie-$version.bin.osx$bits.tar.bz2syndie-cli-$version.bin.tar.bz2i2p.jar)syndie-$version.src.tar.bz2Coding conventions are fairly standard for java projects, though the guideline is to follow whatever standards are in use within the particular file you are working in. Wider guidelines across the whole codebase for new code:
_private static final String T_$name
void foo() {
} not void foo()
{
}
private int getFoo() { return _foo; }