SPIKE: decide on frequency of releases
Description
Environment
Potential Workaround
relates to
Checklist
hideTestRail: Results
Activity
Jakub Skoczen June 7, 2019 at 12:17 PM
Frequency for releases for Q2 and onwards has been established.
John Malconian January 28, 2019 at 5:43 PM
Given that the goal of this is to be able to build a core environment from formally released versions, does this also apply to all of the modules that the core relies upon as well, e.g. mod-feesfines, mod-source-record-storage?
Yes, it would have to.
Marc Johnson January 28, 2019 at 5:38 PMEdited
@Jakub Skoczen I think we can try it.
I think we need careful planning between the core functional, core platform and other teams contributing to core modules to decide what goes in.
Are we thinking these are released prior to the end of the sprint, or at the beginning of the next one?
I think we also need to review who / which teams are responsible for these releases, since the teams have been re-organised.
If it will mostly be the core functional team, I think that needs factoring in to the teams capacity.
Given that the goal of this is to be able to build a core environment from formally released versions, does this also apply to all of the modules that the core relies upon as well, e.g. mod-feesfines, mod-source-record-storage?
John Malconian January 28, 2019 at 5:36 PM
Seems logical to me, Jakub. Worth a try to see how it goes.
Jakub Skoczen January 28, 2019 at 5:34 PM
@Marc Johnson [@Adam Dickmeiss @John Malconian @Zak Burke Guys, we discussed that it makes more sense to release both front-end and back-end modules close to each other. I would propose we try to release them once per sprint, is that acceptable?
Details
Details
Assignee
Reporter
Labels
Priority
P2
To keep FOLIO "release" distribution fresh we need more frequent releases of backend and front-end modules. Currently there's usually no need to make releases more frequent than once per quarter (when they are required for the quarterly release management). Doing them more frequently throughout the quarter and rebuilding "release" environment will decrease the time needed to prepare the quarterly release. Eventually the "release" environment can take over from folio-snapshot-stable for demo and integration of modules across FOLIO.