-
Notifications
You must be signed in to change notification settings - Fork 6
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
breaking change: deprecate cnb_classification
dataset
#329
Comments
@jdhoffa do we have a rough timeframe (on a calendar) when we expect to fully deprecate? |
Nope, but I think if we do my quarterly release schedule, then next release is end of Q1 (end of March). That will mark beginning of deprecation. Following release is end of Q2 (so end of June?) I guess end of June would be when they are hard deprecated? I will update the warning message and add an ADO ticket |
Maybe have something along the lines of " So users know have some idea of when they would need to transition by? |
Deprecation warning is already there. Following the I just need to update the "date" |
@AlexAxthelm do you think "expected in 2024Q2 release" would be too vague actually? I would tend to prefer that... especially given that the proposed "quarterly release" cadence is really just quarterly and has no specific date or month focus yet... Gives us a bit of flexibility while still giving the user an idea of when things will change. |
ADO ticket in proposal of next quarter's KRs involving completing the deprecation process: |
I think I shouldn't write user-facing messages. But that's reasonable enough from my side. cc @hodie |
As per a discussion with @jacobvjk, we are going to add the ISIC classification bridge revision 5. So rather than a "deprecation" the dataset will just be updated. See here: https://unstats.un.org/unsd/classifications/Econ
|
cnb_classification
and isic_classification
cnb_classification
dataset
Relates to #327
FYI @jacobvjk, I plan to deprecate these datasets properly, which means including a release where we just warn that they will be deprecated.
AB#10173
The text was updated successfully, but these errors were encountered: