Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Determine release schedule #14

Closed
Mark2000 opened this issue Jul 25, 2023 · 0 comments · Fixed by #140
Closed

Determine release schedule #14

Mark2000 opened this issue Jul 25, 2023 · 0 comments · Fixed by #140
Labels
infrastructure Testing, documentation, and CI system question Further information is requested
Milestone
v1.0.0 Release

Comments

@Mark2000
Copy link
Contributor

Mark2000 commented Jul 25, 2023 •
edited
Loading

Discussed paradigm is contribute to develop, then occasionally pull changes on develop into main (once they've been vetted through use). What should this process/schedule look like? Does using github's release features add value?

Should also update version in setup accordingly (https://semver.org).
@Mark2000 Mark2000 added the question Further information is requested label Jul 25, 2023
@Mark2000 Mark2000 added the infrastructure Testing, documentation, and CI system label Oct 31, 2023
@Mark2000 Mark2000 mentioned this issue Nov 6, 2023
Closed
7 tasks
@Mark2000 Mark2000 mentioned this issue Dec 1, 2023
Closed
@Mark2000 Mark2000 added this to the v1.0.0 Release milestone Mar 7, 2024
@Mark2000 Mark2000 mentioned this issue Jun 1, 2024
Merged
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure Testing, documentation, and CI system question Further information is requested
Projects
None yet
Milestone
v1.0.0 Release
Development

Successfully merging a pull request may close this issue.

Refactor/v1 0 0 AVSLab/bsk_rl
1 participant
@Mark2000