Page Comparison

a fairly large group, one hour call

a Slack channel "depenency problems", four people

Getting intertwined with another big topic: How do we do the release process ?

We should be able to have a release every month.

We would rather like to have a process like continuous deployment / continuous integration

Anton: We have one manual test cycle per release - how can we talk about continuous releases ? We need to build a lot more of automation. We need to run Unit Tests, then have a bug fest.  Features take precedence over quality work and technical debt work.

Releases should be so low cost to be affordable for everyone.

Brandon: Reduce the risk by making smaller changes more quickly. Pick the low hanging fruit, to make the process more sustainable.  Implement some sort of service discovery in Okapi. Brandon will reach out to DevOps like Stanislav.

Breaking changes. Petrenka keeps a ticket for every module of the system.

In Johannes Drexl part (Debian) there are a couple of inaccuracies. He hopes he can get to do this work this weekend.

Jira-Tickets have the prefixes DOCS. There are not many there, yet.

If you find a problem with the documentation, you can create a ticket.

• good to go ?
• accurate ?
• up-to date ?

Periodic Reviews

Someone from the team will get notified.

Preston Howell was using the Install Guide to set up a system

Kubernetes site looks pretty good (Jason)

https://docs.folio.org/docs/getting-started/additional-configurations/ looks good and up-to-date (Jason).

People will ask questions in Slack chat and in Jira tickets.

We have decided in the SysOps SIG that a ticket in DOCS needs to be created when something comes up. Someone from the group will create that ticket. Marcia will be notified by Jira. She will be a "Watcher" in Jira.

We should make sure that bugs like