-
Notifications
You must be signed in to change notification settings - Fork 175
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
Document all of the changes for nudge 2.0 #574
Comments
This is something I've always wondered about: Is the right approach to start adding these new keys to the wiki now and risk confusing folks not paying attention? Or is it better to wait until after 2.0 releases, but then have the problem that not all keys are immediately documented for early adopters (or new admins starting with 2.0)? |
I'd say start documenting now and put some kind of warning. Each key is supposed to have a minimum version specified as well with the newer keys. |
FWIW I'm now keeping the changelog updated as I add these features so I don't forget. https://github.com/macadmins/nudge/blob/development/CHANGELOG.md |
I've updated the jamf json https://github.com/macadmins/nudge/blob/development/Schema/jamf/com.github.macadmins.Nudge.json It will be up to the community to update the wiki. I can only do so much. Closing as the feature sets are effectively locked now. |
The text was updated successfully, but these errors were encountered: