-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitrotted released langs/pairs #23
Comments
Both |
I was checking just today apertium-arg and confirm that looks and work better than the previous release. I see you just released it several minutes ago; so, great! |
It's important to also check dependencies. E.g., spa-arg needs a release of spa and/or arg - or to build and run correctly with previous release of spa and/or arg. If existing spa Same goes for all the pairs on the list. It's a lot of work. |
And just to clarify my workflow for the releases I make as part of this: I don't check quality, because I don't know these languages. If a given language or pair needs build system updates and only has what looks like harmless or beneficial commits, I'll just cut through and call that a new release. So the ones remaining on the list are ones that to me look like a linguist needs to sign off on the current state. |
I think updates to |
I think |
Huh, kaz-tat does in fact build from the existing release. I'll remove that from the list. |
On 4 January 2021 00:50:08 GMT+03:00, Jonathan Washington ***@***.***> wrote:
I think updates to `apertium-kaz` make `apertium-kaz-tat` less stable
than it used to be.
That's correct. Kaz-tat is yet to be accommodated for the changes in apertium-kaz.
Ilnar
So forcing a new release seems not ideal as things
…currently stand. @IlnarSelimcan, thoughts?
--
Простите за краткость, создано в K-9 Mail.
|
I've been checking these days both Not only they compile, but testvocs are also ok, and the translators have improved since the last release. So, my preference would be: |
With the way releases are done now by bundling the exact version of dependencies, nobody else really has to agree on releasing |
Then, that would be great (and also to have a new version of apertium-arg tagged). Tell me if I need to do anything else. Thanks! |
Could you also update both pairs in apertium.org? Thanks! |
It'll have to wait a while. The whole release site setup needs to be redone, but it's not currently possible because the broken pairs won't build with latest versions - and conversely, the new pairs use new features. So it rather has to be done at a point where every released pair works, which isn't quite yet. But hey, only 8 pairs need fixing. |
apertium-srd, apertium-ita and apertium-srd-ita are ready to be packed. They are indeed a new release on which we have work in the last 3+ months with quite a lot of corrections in the dictionaries, several thousands of new words, tons of new lexical rules and a few tens of new transfer rules. |
apertium-cat-srd is ready to be packed. It needs two new releases of apertium-srd and apertium-cat (with minor changes). |
I've been taking a look to apertium-spa-ita with the lastest version of apertium/lttoolbox/apertium-spa and apertium-ita. It compiles and it works. It is basically as it was some years ago. I introduced some fixes in the dixes, but it is still far from being testvoc clean. I'm not sure if it deserves a new release, if just for organisational purposes, then OK. I don't know how to make a release though. |
Good enough for me. I just need people to sign off on that current state isn't worse. |
Similar to #14 but focused on bitrot and other issues with released languages and pairs. Some just need a person to sign off that current state is releasable, but some need hands-on fixing.
Needs work
(checkbox denotes fixed or not)
Fixed
(checkbox denotes uploaded to Debian or not)
Existing release is usable
(checkbox denotes uploaded to Debian or not)
Even if an existing release is usable, it should be republished in Debian with new version requirements. I will do this when I push everything onwards.
The text was updated successfully, but these errors were encountered: