El dt 08 de 02 de 2011 a les 18:12 +0100, en/na Gema Ramírez-Sánchez va escriure: > So, correct if wrong... > > TRUNK: would contain pairs in "release" and "[alpha|pre]-release" > status an no pair without a release.
Example: apertium-br-fr > STAGING: would contain pairs that builds and have an advanced status > of all modules (dictionaries with closed cathegories and a decent > coverage, an "ad hoc" PoS tagset and .prob, good coverage of main > contrastive phenomena, testvoc clean, and a post-generator if needed). > There should be a "PROBLEMS" file saying, IMO, status and major > problems found while reading translations done with this pair (so, not > a complete evaluation but a general compilation of big problems > detected at the output). That could be a middle solution between Fran > and Jim point of view. Would [Alpha|Pre]-releases also be allowed for > pairs in staging? Example: apertium-af-nl > NURSERY: would contain pairs that build but that have not been > developed deeply or maybe data copied from other pairs that needs work > or very poor data on some modules, etc. Example: apertium-no-en > INCUBATOR: would contain pairs with pieces of translators Example: apertium-br-cy > I like the idea in general, how should we go ahead? making a proposal > and submitting it to the PMC? +1 Fran ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
