Skip to content

As a PDS EN dev lead, I want a simple way of publishing the status of all the active software EN releasesΒ #80

@tloubrieu-jpl

Description

@tloubrieu-jpl

Checked for duplicates

No - I haven't checked

πŸ§‘β€πŸ”¬ User Persona(s)

I would like a more easily maintainable version of https://nasa-pds.github.io/releases/16/index.html

We could have a sphinx plugin which configuration would be 2 exclusive parameters:

  • stable: if yes only shows latest stable version, otherwise snapshop or dev versions
  • list of excluded repositories
  • list of included repositories

Question: should we keep track of past PDS builds abd all the software version associated ?

πŸ’ͺ Motivation

...so that I can have nice pages and maintain them easily.

πŸ“– Additional Details

No response

Acceptance Criteria

Given
When I perform
Then I expect

βš™οΈ Engineering Details

It would be a re-engineering of what pdsen-corral does.

πŸŽ‰ I&T

No response

Metadata

Metadata

Assignees

No fields configured for Feature.

Projects

Status

ToDo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions