-
Notifications
You must be signed in to change notification settings - Fork 15
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
Consider amending description of code FRG050 #338
Comments
Thanks @mrshll1001 - I take it this would need approval by the SC then to go ahead? |
Reading this through I think it may actually be a PATCH. If so, it may just require approval from a 360G team member + an SC member. |
@KDuerden What do you think about this suggested change? |
A PATCH has an approval process that involves posting on the Forum with one week notice for comments from SC or others. Potentially this could be considered a non-normative change to a normative part of the Standard, in which case we can sign off internally. However given we have a few changes of this type being bundled together, I think once everything is ready, we should do a post to cover everything, giving the necessary notice (eg if there are any MINOR updates bundled in there too, we'll need to give 2 weeks notice) |
The code FRG050 has a description of:
It's possible that this should be amended to:
This is because there may be multiple grant payments to the defined recipient.
This would be a PATCH level change
The text was updated successfully, but these errors were encountered: