-
Notifications
You must be signed in to change notification settings - Fork 33
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
Should there be separate release and development branches? #204
Comments
+1 especially when a PR timeline gets stretched out by lots of comments |
I would agree that to further encourage contribution to SWEET, we probably need a more explicit branch structure. The other structure to consider might be a "pending" type structure similar to what schema.org uses that creates something of an intermediate release of new terms. Adopters have the freedom to start using the terms with the caveat that things may change in the final release. It also gives the opportunity to catch bugs with a term before it is "fully released". |
SWEET currently uses main as a stable, or release, branch (assuming release is stable) as well as PRs for what are effectively development branches. Is there a need to make this explicit for potentially new users and/or contributors?
For example, having #203 in a dev branch to signify technical stability (e.g. it doesn't break in an ontology editor) without semantic verification may be useful, particularly for the larger scale changes and additions.
The text was updated successfully, but these errors were encountered: