DISCLAIMER and some "(incubating)" references are still around after graduation

Abierto
#895 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 2 días

@sasmith-14 ya está trabajando en esto.

Desde el 20/11/2026.

  • #896 de @sasmith-14 — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
66/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, scala

Línea de trabajo

Start with DISCLAIMER, pom.xml's apache-release profile, build/check-release.sh, build/rollback_release.sh, and .licenserc.yaml; then review the listed comments and README references in wayang-benchmark, wayang-ml, guides/develop-in-Wayang.md, and python/README.md. Check the release packaging and license check described in the issue. Done means the obsolete incubation references and archive names are updated, the source release no longer includes DISCLAIMER, and old release notes and test data remain untouched.

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

Descripción

The DISCLAIMER file still says Wayang is "undergoing incubation", and the apache-release profile in pom.xml still packages it, so it ended up in apache-wayang-1.1.1-source-release.zip (the NOTICE in the same zip already says "Apache Wayang"). Looks like it was missed in #650. Probably worth fixing before 1.2.0.

A few smaller leftovers:

  • build/check-release.sh, build/rollback_release.sh (a commented-out line) and .licenserc.yaml still reference DISCLAIMER
  • 12 files in wayang-benchmark and wayang-ml say "Apache Wayang (incubating)" in their doc comments, plus a few lines in wayang-benchmark/README.md (one of them links to an old incubator-wayang path that no longer exists)
  • guides/develop-in-Wayang.md and python/README.md use the old -incubating-dist.tar.gz names

I have a small branch that fixes all of this (license check passes, and the source-release zip no longer contains DISCLAIMER). Old release notes and test data stay untouched. Should I open a PR, or would you rather handle DISCLAIMER during the release prep?

Lenguaje dominante
Java
Estrellas
284
Forks
147
Merge medio
2 d 13 h
PR fusionados (30 d)
13

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 apache/wayang

Todos los issues de apache/wayang

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.