Next target versions (0.12.0)
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
调研方向
Start by reviewing the CI configuration and the configure requirements described in the issue, then inspect the outstanding pull requests and the proposed master/develop branch plan. Done means the agreed minimum versions are reflected in CI and configure, compatibility fixes are integrated, and the branch is thoroughly tested for a 0.12.0 release.
由索引模型根据 Issue 内容生成。
描述
| OS/Component | Linux - Ubuntu LTS (24.04/Noble) | Linux - Debian | Linux - Arch | Linux - Gentoo | BSD | OS X | Windows -MinGW | Windows - ? |
|---|---|---|---|---|---|---|---|---|
| C++ - g++ | 13.2.0 | 14.3.0 | ||||||
| C++ - clang | 18 | 20.1.7 | ||||||
| Protobuf | 3.21.12 | 30.2 | ||||||
| Libmicrohttpd | 1.0.0 | 1.0.1 | ||||||
| Python | 3.12 | 3.13.3 | ||||||
| Java | openjdk21 | openjdk21 |
Assumptions:
- Python 3 only - min version 3.??
- Protobuf 3 only
- Min C++??
- Min Java ??
Proposal, from the above:
- Fork master to develop
- Drop any CI versions that are too old
- Add new CI versions to match minimum and above - Expect these new ones to fail
- Alter configure to require these new minimums - New ones will continue to fail due to outstanding bugs
- Redirect existing PRs that fix these issues at develop, ideally merged into some sort of super PR that just fixes things in one big bang, but see how we go there
- Get people to thoroughly test the now-working develop branch
- Pre-release pull in any remaining work that got merged into master having fixed up as required.
- When happy release as 0.12.0 (possibly release master as 0.11.0 as a legacy release at the same time)
I think this gives a manageable way to get off our current target whilst still allowing some parallel work around doing that, whilst also resolving the large number of (mostly mine) unmerged PRs (and worse uncommitted code) for stuff like E1.33, which I think just plowing ahead on the master branch would provide a nightmare of merge conflicts and possibly a broken branch.
- 主要语言
- C++
- 星标
- 773
- 派生
- 233
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
OpenLightingProject/ola 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
OpenLightingProject/ola#2075 ·
-
Digital Enlightenment / FX5 not recognized可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭question Type-DeviceSupport
难度 4/5 3-5 天 新手友好度 35/100
OpenLightingProject/ola#2056 · 2 条评论 ·
-
难度 3/5 1-2 天 新手友好度 55/100
OpenLightingProject/ola#2055 ·
-
Difficulty-Medium Language-C++ Maintainability OpSys-All
难度 4/5 3-5 天 新手友好度 45/100
OpenLightingProject/ola#2053 · 1 条评论 ·
-
v0.11.0可能重新可做 @peternewman 于 227 天前认领,目前没有进行中的 PR。 未关闭
OpenLightingProject/ola#2038 · 18 条评论 · 已指派 2 人 ·
查看 OpenLightingProject/ola 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
deepseek-ai/DeepEP#830 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
google-ai-edge/LiteRT-LM#4701 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
HarperFast/rocksdb-js#1131 ·
维护者通常 1 天内回复
-
Swapped cache lookups in ScanModelAndDecideAllDiffExpansion可能已有人在做 @Lian292213 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
area/daemon bug good first issue platform/linux priority/p2
难度 2/5 1-3 小时 新手友好度 72/100
ToshiNamura/Deimos#5 ·