Difference between revisions of "Release policy"
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
* whether it compiles and runs with the latest _release_ of apertium/lttoolbox (and other required packages) |
* whether it compiles and runs with the latest _release_ of apertium/lttoolbox (and other required packages) |
||
* whether it compiles and installs correctly as a tarball created with make dist (see [[Making_a_release#Testing]]) |
|||
* if there are regression tests, check that these pass |
* if there are regression tests, check that these pass |
||
* run a corpus through it, and ensure there are no debug symbols (#, @) |
* run a corpus through it, and ensure there are no debug symbols (#, @) |
Revision as of 08:26, 6 September 2013
When the stuff is ready?
Some things that should always be checked:
- whether it compiles and runs with the latest _release_ of apertium/lttoolbox (and other required packages)
- whether it compiles and installs correctly as a tarball created with make dist (see Making_a_release#Testing)
- if there are regression tests, check that these pass
- run a corpus through it, and ensure there are no debug symbols (#, @)
- some transfer bugs can be rooted out by compiling the transfer files with either vm-for-transfer-cpp or
apertium-preprocess-transfer-bytecode-j
from Lttoolbox-java