You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original card was: Start using releases and milestones in according with GitHub and open source guidelines.
At this point, we have made a couple of nice releases using the github system, but I don't believe we have fully documented the process in CONTRIBUTING.md or any other relevant place. Both as an open source project and simply to maintain consistency between releases, we need to establish a clearcut process.
We want to work in a more standard way when it comes to releasing code versions. We will manage our versions in accordance to https://semver.org/. Each release will already have a set of features that are expected in it. When those features get merged in, we will create a new release with automatically generated, then human curated changelogs.
Implementation Considerations
Don't think of this from scratch; just use what other open source projects use
Deliverable
A working release system that the team abides by
Dependencies
No response
The text was updated successfully, but these errors were encountered:
CarsonDavis
changed the title
Start using releases and milestones in according with GitHub and open source guidelines
Clearly Document Release and Milestone System for COSMOS
Jan 9, 2025
Note
The original card was: Start using releases and milestones in according with GitHub and open source guidelines.
At this point, we have made a couple of nice releases using the github system, but I don't believe we have fully documented the process in CONTRIBUTING.md or any other relevant place. Both as an open source project and simply to maintain consistency between releases, we need to establish a clearcut process.
Use release v3.0.0 as a guide. https://github.com/NASA-IMPACT/COSMOS/releases
Original Card Details Below
Description
We want to work in a more standard way when it comes to releasing code versions. We will manage our versions in accordance to https://semver.org/. Each release will already have a set of features that are expected in it. When those features get merged in, we will create a new release with automatically generated, then human curated changelogs.
Implementation Considerations
Deliverable
Dependencies
No response
The text was updated successfully, but these errors were encountered: