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

Register package #71

Closed
3 tasks done
navidcy opened this issue Nov 5, 2021 · 4 comments · Fixed by #252
Closed
3 tasks done

Register package #71

navidcy opened this issue Nov 5, 2021 · 4 comments · Fixed by #252

Comments

@navidcy
Copy link
Collaborator

navidcy commented Nov 5, 2021

What do we need to

@glwagner, @adelinehillier feel free to edit this list

@glwagner
Copy link
Member

glwagner commented Nov 5, 2021

I think we should keep projects in some fashion because it will be convenient... in some sense we do the same thing Oceananigans (a much more widely used package) via the validation folder. Otherwise we are juggling more packages which could damage our productivity a bit. But, we should still be disciplined about what gets into main versus experimental stuff that lives in branches.

@navidcy
Copy link
Collaborator Author

navidcy commented Dec 4, 2021

I think it's time to register. I feel that if we start calibrations of non-perfect models it's good to have tagged versions of the packages we use. Otherwise every time we change something things could break and we'll be in limbo.

What do you reckon @glwagner, @adelinehillier?

@glwagner
Copy link
Member

glwagner commented Dec 5, 2021

Package registration is different from tagging. Which do we need?

@navidcy
Copy link
Collaborator Author

navidcy commented Dec 5, 2021

Ok. You are right. Tagging is what I'd like!

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

Successfully merging a pull request may close this issue.

2 participants