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

CODES develop integration #160

Closed
gonsie opened this issue Aug 22, 2019 · 2 comments
Closed

CODES develop integration #160

gonsie opened this issue Aug 22, 2019 · 2 comments

Comments

@gonsie
Copy link
Member

gonsie commented Aug 22, 2019

The CODES master branch currently doesn't work with ROSS develop branch. Is there an "official" way we want to updates CODES? I'm unfamiliar with CODES, do they have a particular git workflow in place?

Details should be added to the git workflow blog post

ping @caitlinross

@nmcglo
Copy link
Member

nmcglo commented Aug 22, 2019

CODES is in a kind of transitional period at the moment. Following the recent migration to GitHub this summer, creating an actual git workflow is something I'll be tackling this fall. We'll probably move to something like what ROSS has, though, with a Master/Release branch and a develop branch that accepts feature merges.

I can help ensure that CODES master works with ROSS master but ensuring that CODES master works with some latest ROSS develop branch feels like it might result in a lot of intermediate CODES releases. When CODES has a develop branch, that could be made to work with the latest ROSS develop branch. I can work on that in the coming week.

@gonsie
Copy link
Member Author

gonsie commented Aug 22, 2019

Everything seems to working now with CODES master and ROSS develop, I must have mucked something up on my end 😐 . That said, we should set some standard of how we name CODES branches for ROSS releases (where API changes happen).

@gonsie gonsie closed this as completed Sep 29, 2020
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