search

NASA-PDS / software-issues-repo

Issue tracking repository as a centralized entry point for general PDS software bugs and feature requests.
Apache License 2.0
0 stars 0 forks source link

As a software user, I want to see the known bugs for a component release #49

Closed tloubrieu-jpl closed 6 months ago

tloubrieu-jpl commented 1 year ago

🧑‍🔬 User Persona(s)

software user

💪 Motivation

...so that I can quickly see the known bugs and for each 'major/high' criticality bug, find a work-around.

📖 Additional Details

This is a feedback from the DDR review on 11/31/2022.

⚖️ Acceptance Criteria

Given When I perform Then I expect

⚙️ Engineering Details

Skipping I&T Rationale

i&t.skip label applied because this is an internal tracking mechanism with no affect on the software delivered.

jordanpadams commented 1 year ago

@tloubrieu-jpl as a heads up, whenever we create requirements, we should be sure to set a priority (p.must-have, p.should-have, p.could-have, p.wont-have) prior to removing the triage-needed label.

tloubrieu-jpl commented 1 year ago

ok, thanks @jordanpadams

tloubrieu-jpl commented 1 year ago

That should be added in the release notes.

tloubrieu-jpl commented 1 year ago

I tried to update the parameters of the automated release note by following instructions on https://github.com/github/docs/blob/main/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md but the only allows to select entries from the Pull Request list, it does not enable to pull entries from the issues.

So this option does not seem appropriate.

I suggest to manually add a section for open critical and high severity bugs. See example https://github.com/NASA-PDS/registry-api/releases/edit/v1.2.0

jordanpadams commented 10 months ago

@tloubrieu-jpl added this to sprint backlog since we said we were going to do it. let me know if we should defer

tloubrieu-jpl commented 8 months ago

The proposal is to add the version label to the open bugs at the time of a release (see command created by the PR https://github.com/NASA-PDS/lasso-issues/pull/4).

The command could be called automatically by roundup for stable releases. See ticket https://github.com/NASA-PDS/roundup-action/issues/128

Then the following text (for example) need to be added manually at the end of the release notes: Known Bugs and possible workarounds: v1.3.1 known bugs

tloubrieu-jpl commented 7 months ago

Re-open because one sub-ticket is not closed.

jordanpadams commented 6 months ago

All sub-tasks completed