search

apertium / organisation

Second point of contact for all things Apertium
https://apertium.org/
19 stars 6 forks source link

Guidelines for releases #17

Open ftyers opened 4 years ago

ftyers commented 4 years ago

We should write some general guidelines for releases.

TinoDidriksen commented 4 years ago

Some exist, but need major surgery:

flammie commented 4 years ago

I think in current ecosystem it would make sense to have ~standard ci test suite to pass prior to release. There's a whole bunch of different attempts for tests (make check style) in various languages and pairs we just need to figure out the best and most generic one. Particularly I think the current Release policy list:

  • Testvoc should be clean
  • 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 (#, @)

can be easily automated as ci test.

TinoDidriksen commented 4 years ago

Currently, I do the middle 3 (builds with release versions; builds from tarball; run make test) as part of the packaging work. I assume language devs have done testvoc and corpus to their own standards before they hand it off to me.

But yes, this can be automated. https://github.com/apertium/apertium-packaging/issues/16 is also relevant.