OVAL-Community
|
@OVAL-Community/oval-board-members Due to the limited timeframe to complete all of the OVAL updates, this discussion will end on 10-01-2024, and vote will occur on 10-02-2004 and end on 10-04-2024. |
Replies: 2 comments 2 replies
|
Vote for the same repository, different branches. Leave the master/main branch clean and use different branches for different language versions. Tag the releases and noteworthy development commits and use the github release mechanism. |
|
After some more thought on the topic I'm in agreement with this as well, I spent the last day getting more familiar with the github release process, and I'm wondering if we should move some of our OVAL board based documentation to a different repository? Create an OVAL Board Artifacts Repo or something? When you do the github build, the 'source code.zip' file contains the entire repository, I may start another discussion on Repo maintenance. |
|
Well, there is the option to create a pipeline script which cleans/processes the artifacts and send them to the release. |
|
Closing discussion, OVAL 6 will remain within the OVAL repository. OVAL 5.12 will be a branch, and OVAL6 will get it's own develop branch |
Vote for the same repository, different branches. Leave the master/main branch clean and use different branches for different language versions. Tag the releases and noteworthy development commits and use the github release mechanism.