Your Bug title

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Área
documentation

Línea de trabajo

Start with gd_guidl__change_change_request and the referenced Change Management Plan, then review the named issue templates in eclipse-score/.github and the linked example issue #629. The work spans repository labels, templates, process guidance, and the example across multiple repositories. Done when the acceptance criteria are met and all references agree on the templates and how modification types are identified.

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

Descripción

bug
Description

Description

The Change Management Plan (doc__platform_change_management_plan) has been aligned with the new
GitHub issue templates, which replaced the former "Change Request" issue template:

Reference process: process_description – change management

The following points cannot be resolved in the plan itself. They need changes to the repository
settings, the issue templates or the process description.

Open points

1. Missing labels in eclipse-score/score

The plan marks the Change Request types (gd_req__change_attr_types) with an issue type plus a label:

Change Request type Issue type Label
Feature Feature Request feature_request
Feature Modification Feature Request feature_modification
Component Component Request component_request
Component Modification Component Request component_modification
  • Create the labels component_request and component_modification in eclipse-score/score.
    Only feature_request and feature_modification exist today.
2. Issue templates in eclipse-score/.github
  • The description fields of both issue templates tell users to put the
    Change Management Decision Record Template in the linked PR. The process_description guideline
    (gd_guidl__change_change_request, sections "Templates" and "Create Change Request") requires
    gd_temp__change_feature_request or gd_temp__change_component_request. Decision Records
    (gd_temp__change_decision_record) record the decision (e.g. a FEP outcome), not the request.
    Link the Feature/Component Request Template instead.
  • Rename 1b_ComponentenRequest.yml to 1b_ComponentRequest.yml and update all links to it
    (e.g. in process_description change_management_guideline.rst).
  • Fix the spacing in "Component Request /Modification" so it reads "Component Request / Modification".
  • Optional: record the modification variant in the issue itself, either with a
    "Request / Modification" dropdown or by applying the *_modification labels automatically.
3. Mapping of types in eclipse-score/process_description
  • gd_req__change_attr_types defines four types (Feature, Feature Modification, Component,
    Component Modification). The GitHub issue templates provide two issue types (Feature Request,
    Component Request), each covering both request and modification. Add a note to
    gd_guidl__change_change_request explaining how the modification variant is identified
    (e.g. by label).
  • Update the Change Request example (eclipse-score/process_description#629), which is referenced
    in the guideline, to use the new issue templates.

Acceptance criteria

  • The labels used in the Change Management Plan exist in eclipse-score/score.
  • The issue templates, process_description and the Change Management Plan reference the same
    templates and the same way of identifying Change Request types.
Problem notifications

Notification will be done in the general process community rounds

Analysis results

No response

Solution

No response

Error Occurrence Rate

Single Event

How to reproduce

No response

Supporting Information

No response

Classification

Minor

First Affected Release

0.9

Last Affected Release

not released (main)

Expected Fixed Release

1.0

Category
  • Safety Relevant
  • Security Relevant
Lenguaje dominante
HTML
Estrellas
6
Forks
25
Merge medio
14 h 47 min
PR fusionados (30 d)
35

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 eclipse-score/process_description

Todos los issues de eclipse-score/process_description

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.