pcb-rnd knowledge pool


pcb-rnd release policy: trunk, tags, tarballs

trunk_release by Tibor 'Igor2' Palinkas on 2016-12-05

Tags: insight, release, releasing, timeline, tags, source, tarball

node source



Abstract: Release policy of pcb-rnd and how to keep dual (or multiple) installations for testing.

  Imported from the mailing list archives.

pcb-rnd release policy

dual-version installs

A good strategy for dual-version is to install the last release (either from svn tags or from a tarball release) and keep trunk/ uninstalled. You can always run trunk from source:

cd trunk/src

to test the latest/greatest feature while if you start pcb-rnd from anywhere else you get the latest stable. It's also a good idea to configure the trunk/ version with --debug while keep the stable version in production settings, for speed - debug slows polygons a lot.