Next target versions (0.12.0)

Abierto
#2,005 12 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
cpp, java, python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C++
Estrellas
771
Forks
234
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenLightingProject/ola

Todos los issues de OpenLightingProject/ola

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.