chore: re-check the 1.0 gates against `main` and list what blocks them

Abierto
  • ¿Algo no está bien?
#351 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Jahnavi-HJ ya está trabajando en esto.

Desde el 3/11/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, scikit-learn
Área
release

Línea de trabajo

Start with the Notes list in the [1.0.0] section of CHANGELOG.md, which gives the five gates, then read docs/reference/index.md for the tier of each public symbol. Run the gates against main, and use tests/test_public_api_contract.py and tests/test_deprecations.py to find Tier 1 symbols that still emit DeprecationWarning. Done means a comment here with each command and its output, the symbol and warning lists, and one linked follow-up issue per real blocker. Design decision #110 is a dependency, so comment on this issue before starting.

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

Descripción

documentation good first issue roadmap
Goal

Know exactly what stands between main and the 1.0 API freeze described under ## [1.0.0] - TBD in CHANGELOG.md.

Acceptance criteria
  • Run each of the five gates listed in that section's Notes against current main, and post the command and its output for each here.
  • List every public symbol (from each subpackage's __all__) whose tier in docs/reference/index.md is missing, unclear, or Tier 1 while mid-deprecation.
  • List any DeprecationWarning still emitted by a Tier 1 symbol, with the version it was introduced in.
  • Open one follow-up issue per real blocker, linked from here.
Scope

A report and follow-up issues. No API changes in this issue.

Where to start
  • CHANGELOG.md [1.0.0] section
  • docs/reference/index.md
  • tests/test_public_api_contract.py, tests/test_deprecations.py
Dependencies
  • #110 needs its limitation documented before 1.0 (#361). The redesign itself can wait for a 1.x minor because the classes are Tier 2; see the status note on #110.
Status (2026-11-04)

The gate report is in the comments (2026-11-03, against 03c3c43): four gates pass, gate 2 fails on wording only, and the follow-up is #357. Once #357 rewords the gate, this issue's acceptance criteria are met.

Phase order is a release plan, not a rule against picking up independent work early. Comment on this issue before you start so two people don't build the same thing.

Lenguaje dominante
Python
Estrellas
11
Forks
23
Merge medio
1 d 11 h
PR fusionados (30 d)
30

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 PhilanthroPy-Project/PhilanthroPy

Todos los issues de PhilanthroPy-Project/PhilanthroPy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.