nasa-pds / lasso-issues Goto Github PK

💡 Description

The number of open.* labels is going to get excessive. We should just tag it the first time, and that will give us an indication of how many versions it has been open.

⚔️ Parent Epic / Related Tickets

No response

Motivation

...so that I know how the implementation is progressing.
As a development manager, this will also be useful to produce the metrics

Additional Details

The page https://nasa-pds.github.io/releases/12.0/plan.html will be augmented with progress indicator, next to the list of epics.

For example:

• green done,
• orange in progress
• red: to be started

Acceptance Criteria

Given
When I perform
Then I expect

Engineering Details

Since the status are updated after the generation of the plan page, the indicators will have to be coded in javascript. They can be ajax requests getting the status from the github api.

List of upgrade that should be done before the release of the documentation (RDD, software summary, TRR) for next build 13.0:

• have the histogram plot of the bug severity show in each column the proportion of open and closed bugs in the TRR slides
  To Be completed

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

RDD fails when a theme issue is not a zenhub issue.

🕵️ Expected behavior

We expect the generation to finish without failure.

📜 To Reproduce

See action https://github.com/NASA-PDS/nasa-pds.github.io/actions/runs/6329387432/job/17189559877

It happens for ticket NASA-PDS/software-issues-repo#78

🖥 Environment Info

As used in github actions.

📚 Version of Software Used

• Version of this software 1.0.0

🩺 Test Data / Additional context

No response

🦄 Related requirements

No response

⚙️ Engineering Details

No response

💡 Description

Add closing date to issues in RDD and order the issues by this date.

⚔️ Parent Epic / Related Tickets

No response

• - have the number of new bugs raised during the build cycle on the released software
• - do not present addressed bugs (those raised during dev, I&T) but only the one that users see (ie on stable releases)
• - SLOC have the number of lines added and removed in addition to percentages, meet with MGSS people to get their updated template.
• publish the metrics chart on the web
• add security incident analysis section to TRR report

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

Trying to run the rdd report, I get an unsupported operation error.

🕵️ Expected behavior

I expected to generate the RDD

📜 To Reproduce

$ pds-issues --format rst --issue_state closed --build B14.0

...
INFO Create file pdsen_issues.rst
INFO  exists. ignoring.
Traceback (most recent call last):
  File "/Users/jpadams/.virtualenvs/lasso-issues/bin/pds-issues", line 8, in <module>
    sys.exit(main())
  File "/Users/jpadams/proj/pds/pdsen/workspace/lasso-issues/src/lasso/issues/issues/issues.py", line 142, in main
    rst_rdd_report.create(args.github_repos, "pdsen_issues.rst")
  File "/Users/jpadams/proj/pds/pdsen/workspace/lasso-issues/src/lasso/issues/issues/RstRddReport.py", line 844, in create
    self.write(filename)
  File "/Users/jpadams/proj/pds/pdsen/workspace/lasso-issues/src/lasso/issues/issues/RstRddReport.py", line 857, in write
    self._rst_doc.write(filename)
  File "/Users/jpadams/proj/pds/pdsen/workspace/lasso-issues/src/lasso/issues/issues/RstRddReport.py", line 110, in write
    f.write(self.data)
  File "/Users/jpadams/.virtualenvs/lasso-issues/lib/python3.9/site-packages/rstcloth/rstcloth.py", line 87, in data
    return self._stream.read()
io.UnsupportedOperation: not readable

🖥 Environment Info

Mac OSX

📚 Version of Software Used

v1.2.0

🩺 Test Data / Additional context

No response

🦄 Related requirements

No response

⚙️ Engineering Details

No response

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

When I did launch 2 times the same command, for example add-version-label-to-open-bugs --github-repo deep-archive --labelled-version v1.1.5
The second time the command fails because the label has already been created.

This happens sometime in the CICD and it is blocking it, see https://github.com/NASA-PDS/data-upload-manager/actions/runs/8191626427/job/22401254906

🕵️ Expected behavior

I expected to work, doing nothing, and return the lines to be added in the release notes.

📜 To Reproduce

No response

🖥 Environment Info

No response

📚 Version of Software Used

• 1.3.0

🩺 Test Data / Additional context

No response

🦄 Related requirements

No response

⚙️ Engineering Details

No response