Next target versions (0.12.0)

Aperta
#2,005 12 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
cpp, java, python

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C++
Stelle
771
Fork
234
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenLightingProject/ola

Tutte le issue di OpenLightingProject/ola

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.