On 26 December 2013 19:07, Mikel Forcada <[email protected]> wrote:
>
>
> - Maintain the following machine translation systems up to date, at
> least quarterly, to the last stable version:
> - The systems available through the Apertium.org web interface
> - The systems (.tar.gz releases) available through SourceForge
> - The systems available through the web API to e.g. OmegaT
> - The language pairs available for use with Apertium-OmegaT,
> Apertium-Caffeine and Apertium for Android
> - An Ubuntu-style PPA repository.
> - Test and release twice a year stable versions of Apertium language
> pairs from suitable subversion copies when there are changes.
>
> All of those tasks can be scripted and automated and run on a nightly
basis (except Android publishing). The heavier work involved would be to
set up some good regression tests so that the automation will report back
when something is failing the nightly packaging.
I am certainly interested in doing that. It's something I've wanted to do,
but haven't been able to justify spending time on since there were paid
tasks elsewhere.
>
> - Make sure that Debian (and therefore Ubuntu) releases of Apertium
> are up to date at least once a year
>
> Isn't Francis maintaining Debian packages?
http://qa.debian.org/developer.php?login=ftyers%40prompsit.com still lists
him as maintainer for lots of Apertium packages.
-- Tino Didriksen
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
