Your Bug title

未关闭
  • 哪里不对？
#863 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
领域
documentation

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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
主要语言
HTML
星标
6
派生
25
平均合并
14 小时 47 分钟
30 天内合并 PR
35

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

eclipse-score/process_description 的其他 Issue

查看 eclipse-score/process_description 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。