ATE: proofread changelog and publish it on Tarantool website
Open
Nobody has claimed this yet.
ate
release-notes
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Related dev. issue(s): https://jira.vk.team/browse/TNTP-2071 https://jira.vk.team/browse/TNTP-1108
Product: ATE
Audience/target:
Root document: https://www.tarantool.io/en/devops/latest/
SME: @ opomuc @ lastoCHka42 @ RetardedRedhaired @ RunsFor
Details
Клиенты хотят видеть ченджлоги АТЕ на сайте.
Нужно определить:
- в каком режиме их будем публиковать (автоматически или вручную, как в TDG). Если автоматически, то от команды ATE требуется настройка соотв пайплайна
- на каком языке публикуем. Если на русском, то нужен перевод ченжлогов.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Tarantool DevOps root document and review the related Jira issues TNTP-2071 and TNTP-1108. Compare the proposed process with how TDG changelogs are published, then confirm the publishing mode and language with the listed ATE SMEs. Done means the agreed workflow is implemented and ATE changelogs are available on the Tarantool website.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100