Next target versions (0.12.0)

未关闭
#2,005 12 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
冷清
技术栈
cpp, java, python

调研方向

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 内容生成。

描述

Maintainability OpSys-*BSD OpSys-All OpSys-Linux OpSys-OSX OpSys-Windows Priority-High Type-Task
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:

  1. Python 3 only - min version 3.??
  2. Protobuf 3 only
  3. Min C++??
  4. Min Java ??

Proposal, from the above:

  1. Fork master to develop
  2. Drop any CI versions that are too old
  3. Add new CI versions to match minimum and above - Expect these new ones to fail
  4. Alter configure to require these new minimums - New ones will continue to fail due to outstanding bugs
  5. 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
  6. Get people to thoroughly test the now-working develop branch
  7. Pre-release pull in any remaining work that got merged into master having fixed up as required.
  8. 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 模板
  • 阅读贡献指南

从这里开始

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

OpenLightingProject/ola 的其他 Issue

查看 OpenLightingProject/ola 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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