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

deprecate OneHundredBackground and OneThousandBackground #416

Open
goldingn opened this issue Mar 6, 2018 · 5 comments
Open

deprecate OneHundredBackground and OneThousandBackground #416

goldingn opened this issue Mar 6, 2018 · 5 comments
Labels

Comments

@goldingn
Copy link
Member

goldingn commented Mar 6, 2018

We really need to get rid of these duplicates of Background - Ie. just delete them from the modules repo

@goldingn goldingn added the module label Mar 6, 2018
@timcdlucas
Copy link
Contributor

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 GetModuleList (ideally with an argument for adding the back in i.e showDepreciatedModules = FALSE), and remove from all documentation. Then just let them sit quietly on the repo.

@goldingn
Copy link
Member Author

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...

@goldingn
Copy link
Member Author

See this on installing past versions: #297
and this on the lookup table: #291

Happy to go down other routes, though one option would be to use travis or some other webhook-type-thing to automatically update that lookup table

@timcdlucas
Copy link
Contributor

Commit plans etc. sounds good. I guess just to be careful that if

process = OneHundredBackground worked before, I'm not sure it's ok if I need to change it to process = OneHundredBackground(commit = 1nwefej2) for it to work after depreciation. Bearing in mind that I have no idea where in the syntax the commit would be.

If the default is process = OneHundredBackground(commit = 'latest') then think that should work fine.

@goldingn
Copy link
Member Author

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 RerunWorkflow() always works, but we probably don't need to ensure that OneThousandBackground can always be used to create a new workflow, even after it has been deprecated.

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

No branches or pull requests

2 participants