-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a mechanism to create release notes for a data release from logged changes #77
Labels
documentation
Improvements or additions to documentation
keep alive
exempt issue from staleness checks
Comments
reece
changed the title
Provide a mechanism to create release notes for a data release
Provide a mechanism to create release notes for a data release from logged changes
Jun 9, 2020
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
github-actions
bot
added
the
stale
Issue is stale and subject to automatic closing
label
Sep 21, 2023
This issue was closed because it has been stalled for 7 days with no activity. |
reece
added
stale closed
Issue was closed automatically due to inactivity
and removed
stale closed
Issue was closed automatically due to inactivity
labels
Nov 27, 2023
github-actions
bot
removed
the
stale
Issue is stale and subject to automatic closing
label
Dec 9, 2023
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
github-actions
bot
added
the
stale
Issue is stale and subject to automatic closing
label
Mar 9, 2024
jsstevenson
added
documentation
Improvements or additions to documentation
keep alive
exempt issue from staleness checks
and removed
stale
Issue is stale and subject to automatic closing
labels
Mar 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
keep alive
exempt issue from staleness checks
Each release should have release notes or release log.
An easy solution: Store logs in dated directories/files in top-level directory (for fastadir backend).
The text was updated successfully, but these errors were encountered: