When I see “release management” I think of the exercise that the gap analysis team (Mark V, Cate, Harry, Holly, Jakub, I also attended today’s meeting) went through to try and lay out features, resources, and see where things fit, what makes sense together, etc, etc. So what goes into a release, not so much as how the bits are pulled and aligned. IMO we might need to decide on/document the process around what gets released too.

What you refer to as problems related to the builds, I think, is already active for us: https://wiki.folio.org/pages/viewpage.action?pageId=14453402 - Insufficient build processes

The Q2-2018 release is a tag that was done manually, by using a CI-generated build that created a folio-testingplatform environment and the yarn.lock and instal.json files that went with that build, and adding the Q2-2018 tag to it. In other words a ‘manual’ process.

The desire to get to periodic releases of modules to a non-CI-generated repository, I think is recognized. Then you could have (like in Debian) a bleeding edge repo, and a repo with a few more guarantees for teams to work from.

Zak, Jakub, Anton and Wayne Schneider, do you guys think that the item that the TC outlined, which has these objectives:
  1. Research possible changes to improve reliability of packaging and distribution of build artifacts
  2. Review existing component dependency management and recommend improvements
  3. Implement triggering of automated tests based on dependency tree

Gets us to that place?

-mdg
 

On Jul 31, 2018, at 1:53 PM, Tod Olson <tod@uchicago.edu> wrote:

TC,

The issue of release management came up in the OLE Steering Committee this morning, and I wanted to pass it along as an item for us.

Not having a stable release environment is blocking ERM. Ian Ibbotson brought this to Mike and Kristin. Ian will characterize the blockage and send something to the TC.
There is a sense of urgency around getting stable releases, and that the ERM group believes they cannot really assign work to devs without stable releases.

I was asked where the TC is on release management. It's not a specific item on our backlog, though it seems closely related to QA issues that Anton has already identified, plus several other items on the backlog. It seems no one was aware of the Q2-2018 release that Wayne put together, though I also think more regular, buildable releases are closer to what will be needed.

So it seems release management is coming to us as a new item for the backlog, it will be better defined by Ian, and there is a sense of urgency.

-Tod

To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=SeK0ArgpLZB2ijVHc1q8eivZ4CXy8J2w