Re: fedora.zanata.org is now on version 4.4.5

Alex Eng <[email protected]>
Newsgroups gmane.linux.redhat.internationalization
Message-ID <CAA6Xr1SCGhoMCzQH46c+9_W73dQFH1_7j1YwBt-t1fqo+1uVPQ@mail.gmail.com>
I've done my best to summarize the release notes:

General:
- bug fixes
- UI and performance improve

Translators:
- Continue to improve on the alpha editor few more features:
https://zanata.atlassian.net/browse/ZNTA-36
- the reviewer can input the reject criteria during the review
process: https://zanata.atlassian.net/browse/ZNTA-2215

Project maintainer:
- Users can create a private project:
https://zanata.atlassian.net/browse/ZNTA-2173
- Increase the flexibility on "TM merge" to leverage more translations
in the platform: https://zanata.atlassian.net/browse/ZNTA-1865,
https://zanata.atlassian.net/browse/ZNTA-2153
- API:
  - members of a language team: https://zanata.atlassian.net/browse/ZNTA-1915
    docs: http://zanata.org/zanata-platform/rest-api-docs/resource_LocalesResource.html#resource_LocalesResource_getMembers_GET
 - translation statistics for project version:
https://zanata.atlassian.net/browse/ZNTA-1954
    docs: http://zanata.org/zanata-platform/rest-api-docs/resource_StatisticsResource.html#resource_StatisticsResource_getProjectStatisticsMatrix_GET

Infra/admin:
- Webhooks for different events: https://zanata.atlassian.net/browse/ZNTA-1166
  docs: http://docs.zanata.org/en/release/user-guide/projects/project-settings/#webhooks
- New file extension support
  - JSON - https://zanata.atlassian.net/browse/ZNTA-667
  - QT TS - https://zanata.atlassian.net/browse/ZNTA-689
- Admin can control if allow anonymous user to access resources in
Zanata: https://zanata.atlassian.net/browse/ZNTA-1527


> Copy Trans will no longer run by default

That was already disabled prior to this upgrade. There are no changes
to any of the current setup/config that interacts with Zanata (e.g.
push/pull).

>
> I look forward to seeing your infra ticket as you drive this to completion. 3


https://github.com/fedora-infra/zanata2fedmsg/issues/1

> What kind of update cadence should be expected? How much notice? Who is coordinating this relative to the rest of the project’s schedule?


We aim to have releases every 3 months. However, we might have
releases outside of the schedule if it is required (e.g. critical
security patch).
We will inform the mailing list 2 weeks prior the packaging process
before releasing to prod.

> Who is coordinating this relative to the rest of the project’s schedule

You can contact me directly or email to [email protected]

Alex Eng
Zanata Platform
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]/message/AACS4POTKWE2NNRZMDJOKFDQZPT2H7OB/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.