-
Notifications
You must be signed in to change notification settings - Fork 13
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
deprecate OneHundredBackground and OneThousandBackground #416
Comments
Thinking about this, and bearing in mind our remit for reproducible workflows, we probably need something a bit more considered (certainly might for the future, if not so vital for these modules). I think the easiest is to remove modules from |
There was a plan to make it possible to load modules by specific version by maintaining on the repo a list of previous module versions, and the commit at which that version was last available. That would have the same effect, since it would enable us to deprecate modules by deleting them, but still have them accessible. The plan was to wait until we had all modules being uploaded via a website, so that that list could be automatically maintained. Though efforts on that front have stalled... |
Commit plans etc. sounds good. I guess just to be careful that if
If the default is |
Hmmm, good point. That raises the question whether we want the call to workflow to be reproducible, or the workflow itself. Ie. I think we should ensure that doing |
We really need to get rid of these duplicates of
Background
- Ie. just delete them from the modules repoThe text was updated successfully, but these errors were encountered: