Draft a release process

未关闭
  • 哪里不对？
#603 14 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
活跃
领域
release

调研方向

没有指定任何文件、测试或入口点；先阅读此 Issue 中的讨论以及 6 月 17 日工作组的笔记。明确发布节奏、beta 或 release-candidate 测试、本地化时间安排、用户测试和公司通知。完成的标准是：已记录约定的发布流程，并且对未决问题作出了决定。

由索引模型根据 Issue 内容生成。

描述

discussion

We need to find a good solution/process for new releases of MathCAT. We will use this issue to discuss and to start drafting a release process. Below are the key points from the discussion in the working group meeting on June 17.

Questions for discussion:

  • How often should we do a release?
  • What should be the process around a release? A beta version for AT to test? User testing?

A few points from the discussion:

  • Ask the companies using MathCAT what they would like. This could be part of the "outreach to companies" work. Develop a list of what companies to notify.
  • A release candidate and period where people can test, catch up with localizations etc. Companies using MathCAT could have a short period where they can test a new release, to make sure nothing breaks. Companies are depending on things to work, and they often do extensive testing before implementing something.
  • How many big releases should we have during a year? Testing with real users takes time. User testing is important, but we don’t want it to slow things down. With a fast cadence, if there's a problem, we can fix it right away. The tests in MathCAT make sure the translations don’t break.

@NSoiffer , @ways2read , @avneeshsingh

主要语言
Rust
星标
130
派生
96
平均合并
1 天 1 小时
30 天内合并 PR
84

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

daisy/MathCAT 的其他 Issue

查看 daisy/MathCAT 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。