Stable release channel and upgrade policy

未关闭
#430 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
go

调研方向

Read docs/release.md and site/src/content/docs/docs/guides/upgrade.mdx to map the existing release process and upgrade guidance. Define stable release status, breaking change notice, format change announcements, and route or API deprecation rules, then publish the policy and mark format-changing releases in release notes. Done when a stable tag has checksums and attestations and the upgrade policy is live.

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

描述

What

Cut the first stable CalVer release and publish an upgrade policy: which releases are stable, notice for breaking changes, how format-changing releases are announced, and route or API deprecation rules.

Acceptance criteria

  • A non-prerelease tag is published with checksums and attestations
  • The upgrade policy page is live on the docs site
  • Format-changing releases are marked in release notes

References

  • docs/release.md
  • site/src/content/docs/docs/guides/upgrade.mdx

One pull request. Use the latest stable version of any dependency added, verified against its registry and pinned exactly.

主要语言
Go
星标
11
派生
0
平均合并
7 小时 38 分钟
30 天内合并 PR
98

环境准备

从这里开始

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

labstack/fanout 的其他 Issue

查看 labstack/fanout 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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