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) |
||
| + | * 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 [https://github.com/ggm/vm-for-transfer-cpp vm-for-transfer-cpp] or <code>apertium-preprocess-transfer-bytecode-j</code> from [[Lttoolbox-java]] |
* some transfer bugs can be rooted out by compiling the transfer files with either [https://github.com/ggm/vm-for-transfer-cpp vm-for-transfer-cpp] or <code>apertium-preprocess-transfer-bytecode-j</code> from [[Lttoolbox-java]] |
||
Revision as of 10:42, 21 October 2011
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)
- 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-jfrom Lttoolbox-java
