Create a fixed version from an older collection version's references

Abierto
#3,007 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo

Línea de trabajo

The issue names Collection.seed_references and TBv3's fixed-version flow across oclapi2 and oclweb3. First read the dependent issue OpenConceptLab/ocl_issues#3006 and the version creation and expansion entry points in those repositories. Done means a version can copy references from a selected older version, evaluate expansion under its lock, leave both source and HEAD unchanged, offer the choice in TBv3, and pass unit and integration tests including a retired release lock.

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

Descripción

component/api component/web decision/blocked signal/has-dependencies signal/large-scope signal/well-specified stage/triaged type/feature

Repos: oclapi2, oclweb3 · Depends on: OpenConceptLab/ocl_issues#3006

Part of OpenConceptLab/ocl_issues#2942. New versions always take HEAD's references (Collection.seed_references) and HEAD's snapshot, so OpenConceptLab/ocl_issues#3006 can't reproduce an older version when HEAD has moved on. This adds that choice. It comes after Dec 1 (Jon, Nov 3), and OpenConceptLab/ocl_issues#3006 counts as done for the epic until then.

ACs

  • Creating a collection version can name another version whose references it copies.
  • Its expansion is evaluated under the chosen lock, not copied from HEAD.
  • Neither the named version nor HEAD changes.
  • TBv3's fixed-version flow offers the choice when HEAD's references differ.
  • Unit and integration tests, including a lock on a retired release.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
4
Forks
2
Merge medio
2 h 12 min
PR fusionados (30 d)
1

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 OpenConceptLab/ocl_issues

Todos los issues de OpenConceptLab/ocl_issues

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.