add initial version of issues templates

[masc2023]

1-bugfix.yml as defined in Problem Resolution Plan 2-improvement
3- change.yml as defined in Change Management Plan

Resolves partly: eclipse-score/process_description#514

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: a013f1de-dc67-48b0-8f90-5b0addb3d104
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (77 packages loaded, 9 targets configured)

Analyzing: target //:license-check (84 packages loaded, 9 targets configured)

Analyzing: target //:license-check (149 packages loaded, 2900 targets configured)

Analyzing: target //:license-check (155 packages loaded, 4974 targets configured)

Analyzing: target //:license-check (155 packages loaded, 4974 targets configured)

INFO: Analyzed target //:license-check (158 packages loaded, 6990 targets configured).
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 17.591s, Critical Path: 0.35s
INFO: 13 processes: 4 disk cache hit, 9 internal.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[anmittag]

@masc2023 thank you for the initial setup of the templates.

I would rather suggest to have a template for each issue type, but do understand that you define the template based on the desired work type. Are we able to combine the two aspects?

• Bug Template
• Feature Request Template
• Product Increment Template can be used for Change or Improvement or new stuff
• Epic Template: can be used for Change or Improvement
• Task Template: any work close to code

[masc2023]

@anmittag

see proposals here, as general hint, our Change Management applied for Feature Requests/Modifications or Component Requests/Modifications, so product increment and generic epic is only for improvement or taks

[anmittag]

Question: affected version is to be maintained manually and updated after each and every release? Could not be automatically extracted from: https://eclipse-score.github.io/score/main/score_releases/score_releases/

[masc2023]

We need to find an expert, if that is possible automatically, the question here is, that only is required for official releases, not milestone releases