We've hashed this out a little on IRC, but I want to make the proposals more broadly visible.
1) Alpha releases We have a number of 'incubator' translators that are complete, but not fully testvoced, that could benefit from feedback. I propose that we make prerelease versions of these translators available, with a clear marking in the version to show these are not full releases. 1a) What should we use: 'pre' or 'alpha'? 1b) Should we extend this to existing translators? en-es, for example, has had a lot of vocabulary added since the last release, but there are definitely problems with that vocabulary. ----- 2) 'Staging' in SVN The incubator module in SVN has, on the whole, been quite successful, but the range of development statuses is problematic. I propose that we split incubator into 'incubator' and 'staging'[1]. Incubator would remain the place for 'sketches' -- pieces of analysers/bilingual lexicons Staging would become the place for anything that can build and run, but is still quite far from release-worthy. This could mean anything from 'Apertium is missing X' (e.g., cs-pl), or 'we've done as much as we can, but need a native speaker to fill the gaps in our knowledge', as long as the module can honestly be described as 'basically working'. 2b) To be eligible for inclusion in staging, the module must include a text file (perhaps 'PROBLEMS') that clearly explains (in brief) the status of the module. I want to make it clear that I'm thinking about different criteria for inclusion in both proposals: current incubator modules that could be made available as prereleases, that are being actively worked on, should *not* go into staging (eo-fr, es-an), and should just go straight to trunk when ready. [1] I took the name from the kernel, I'm not totally sold on it. -- <Leftmost> jimregan, that's because deep inside you, you are evil. <Leftmost> Also not-so-deep inside you. ------------------------------------------------------------------------------ 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
