Did we make a decision about adding a date to depr...
# team-maintainers
s
Did we make a decision about adding a date to deprecation messages?
thinking about @Evangelos Karatzas’s renaming of the biozarr modules: https://github.com/nf-core/modules/pull/11207
j
Date good
m
I would say 9 month + the next spring cleaning
that way we can just batch deprecate things all at once
c
I don't want this to become a pattern, but as we briefly mentioned in the maintainers meeting - I appear to be the only one using this module - happy for the old one to be deleted so the repo is cleaner.
e
in case we want to add dates though, I would keep a separate spreadhseet somewhere for that; not directly write in the module
c
@Evangelos Karatzas why?
Isn't that just another thing to manage/maintain?
s
Yeah, just include it in the module
m
Why document what we're doing
Creating a PR so that you can create an issue is a waste of time
Unless you don't do it right away, then yeah I document to remember it
j
For configs I created a milestone to collect deprecated configs: https://github.com/nf-core/configs/milestone/1
šŸ‘€ 1
Could use a similar thing to track deprecations and then see how long they were open for
šŸ‘ 1