| Warning |
|---|
draft for discussion |
- Any JIRA issues that relate to this feature change.
- What the project feature aims to accomplish and who should benefit from it - explained in clear, simple language.
- Any JIRA issues that relate to this feature change.
- Verification that the change functions as intended, it is complete and does not introduce blocker bugs in its functionality.
- Which institutions and individuals are committed to support and fix it, and for how long. If it's already running in production somewhere, it would be helpful if that were also noted.
- Stepwise documentation of what this functionality does, in enough unambiguous detail that testers can confirm it behaves as intended.
- Technical Other technical considerations, e.g.
- What other dependencies are assumed, if any, and potential implications for other tools/functionality. e.g. does it include any API changes, or will a helper have a new workflow?
- Are properties leveraged for this functionality? If so, what are they?
- What are the DDL and DML needs of this change? Is any data conversion required for this feature? If so how long will that conversion take?
- What factors influence non-UX performance? E.g. Do calculations depend on the total number of users, or the number of users in a site, or the number of entries in a forum? Is performance linear or non-linear in those factors?
- Are there any security implications of the change?
- Does / will the code conform to Sakai best practices? What implications does this change have for other tools? E.g. Will a helper have a new workflow?(To be realistic this is meant to apply to changes in the code base rather than to preexisting code. It isn't practical for a small change to trigger a re-examination of an entire tool.) (But what are these best practices? How can this be known? CDF)