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.

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

Switch to Oneflow #53

Open
MillironX opened this issue Oct 8, 2022 · 3 comments
Open

Switch to Oneflow #53

MillironX opened this issue Oct 8, 2022 · 3 comments

Comments

@MillironX
Copy link
Member

I would contend that Oneflow is a better branching model than Git Flow for Julia packages. BioAlignments made the transition (albeit, a rocky one). What do others think?

@kescobo
Copy link
Member

kescobo commented Oct 11, 2022

I prefer it too, but main vs master - it's largely symbolic, and maybe only people in the US are sensitive to it but it's an easy change to make

@MillironX
Copy link
Member Author

I'm referring to branch model not branch name. Basically, does it make sense to have an "unstable" branch, a "stable" branch, and stable tags (Git Flow), or just keep an "unstable" branch and stable tags (OneFlow)?

@MillironX MillironX mentioned this issue Oct 13, 2022
@kescobo
Copy link
Member

kescobo commented Oct 14, 2022

Oh, yeah I understand that. BioAlignments still seems to have the working branch called "master", that's all I was commenting on. I definitely prefer OneFlow for a repo of this level of complexity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants