Your Bug title

オープン
  • 何か問題がありますか？
#863 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR（30日）
35

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

eclipse-score/process_description のほかの issue

eclipse-score/process_description の issue をすべて見る

似ている issue

Documentation の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。