[FOLIO-2196] Spike: Formalize release plan Created: 29/Jul/19 Updated: 03/Jun/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Oleksiy_Lemeshko | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | back-end, front-end | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | Core: F - Sprint 71, Core: F - Sprint 69, Core: F - Sprint 70 |
| Description |
|
The purpose of this user story is to have modules release sequence (release plan) documented for other teams to consider during releases Suggested document format / structure |
| Comments |
| Comment by Oleksiy_Lemeshko [ 01/Sep/19 ] |
|
Marc Johnson Hi Marc, did I get you right during that slack 1-1 call that you will add your "part" ? |
| Comment by Marc Johnson [ 02/Sep/19 ] |
That call was a while ago so I don’t have a clear memory of it. At a high level, it takes me about a day to release mod-circulation and mod-circulation-storage (mostly due to needing to reconcile git history and JIRA to create the chsngelog / news). If you want me to elaborate on more of the modules and/or how they fit together, in a different form to the release spreadsheet, let me know, as that will likely take me a significant amount of time. I thought we discussed on the call, how this information could be used to achieve the goal of establish a release plan. I’m happy to try to help with that in any way I can. I think I need to understand more about how this information will be used, in order to do that. I think we talked about how doing that would require significantly more information about dependencies and chains of work, from a much broader audience. For example, to know when to release mod-circulation-storage, we need knowledge of the lead time required for all of the modules downstream from it, and things like which can be done in parallel or sequence, what else do they depend upon etc. And how this information grows stale fairly quickly as dependencies and responsibilities change. I think I referred you to the release spreadsheet which contains our current best representation of some of that, and the releases channel where current coordination happens. |
| Comment by Jakub Skoczen [ 02/Sep/19 ] |
|
Cate Boerema Oleksiy_Lemeshko Can you please provide a context for this ticket? |