[FOLIO-2017] Who should review RAML Module Builder Upgrades? Created: 15/May/19 Updated: 03/Feb/21 Resolved: 03/Feb/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Marc Johnson | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | potential-decision | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
There is a need to review changes when a module is upgraded to a later version of the RAML Module Builder much like any other change. In order to review it effectively there needs to knowledge of the changes to RAML Module Builder, the module being upgraded and how it is used by clients. There are relatively few people who have sufficient knowledge in all of those areas, how can we improve the feedback on these changes? |
| Comments |
| Comment by Marc Johnson [ 03/Feb/21 ] |
|
Closing as pre-dates the new decision making process and has not progressed |