You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just need to clarify something before making a proposal: at some point we discussed the idea of encoding the year cycle number in #9 but in this issue we decided that these can be encoded as eras (to which we can give codes). Now, in a meeting (can't remember which one but it was the one where the issues I brought up were discussed, a few months ago), we decided something else: that there should be a new integer field named "year cycle number". I'm not really sure where to find the meeting notes, and I think both solutions are ok (although I have a preference for the second one which is more flexible), but I just want to make sure I'm not doing something against the decision rules if I propose a change. @ronaldtse wdyt?
The text was updated successfully, but these errors were encountered:
I just need to clarify something before making a proposal: at some point we discussed the idea of encoding the year cycle number in #9 but in this issue we decided that these can be encoded as eras (to which we can give codes). Now, in a meeting (can't remember which one but it was the one where the issues I brought up were discussed, a few months ago), we decided something else: that there should be a new integer field named "year cycle number". I'm not really sure where to find the meeting notes, and I think both solutions are ok (although I have a preference for the second one which is more flexible), but I just want to make sure I'm not doing something against the decision rules if I propose a change. @ronaldtse wdyt?
The text was updated successfully, but these errors were encountered: