TSC Meeting (04 Jan 2022): New StackStorm-Exchange, v3.7.0 Planning

January 2022 @StackStorm/tsc 1 hour planned meeting: Tuesday, 04 Jan 2022, 09:30 AM US Pacific. See #33 for more info about how to join.

Meeting Agenda

StackStorm-Exchange CI was refactored by migrating from CircleCI to GH Actions https://github.com/StackStorm/community/issues/63
Led by @cognifloyd, he'll show demo w benefits, changes, corner cases, security, progress, and outcomes behind the new Exchange.

Attendees:

Original RFC Discussion: https://github.com/StackStorm/community/issues/63
@cognifloyd did a demo guiding us through the StackStorm-Exchange CI/CD changes
CircleCI was replaced by GH Actions
- better model: instead of pushing to Exchange-index (before), Exchange CI is now pulling changes via cron task from all the packs and then regenerating the index
- caveat to keep in mind: index regeneration happens every ~20mins as GH Actions doesn't guarantee every 5mins cron execution/scheduling. Already in production, no complaints so far.
- enhancement: better security
- every pack CD repo doesn't have write access to the Exchange index repo
- outside pack maintainers can't do SSH debugging like it was in CircleCI
Thanks to @lm-ydubler for the assistance
Thanks @winem for the reviews
WIP: A workflow for automatic onboarding new pack into Exchange:
- instead of doing it manually, the new workflow is an automation effort based on GH Actions :+1:
- https://github.com/StackStorm-Exchange/exchange-incubator/pull/172
- Needs more :eyes: from @StackStorm/tsc and @StackStorm/maintainers

Project: https://github.com/orgs/StackStorm/projects/23
(Tentatively) Release Manager: @cognifloyd
(Tentatively) Approx Release Target date: March 2022
Still looking for a Release Assistant from @StackStorm/maintainers and @StackStorm/contributors
~Py 3.6 -> 3.8 update for EL8~ - deprecate EL8 as it reached its EOL
Discuss the https://github.com/StackStorm/community/issues/88 plan
- CentOSStream conclusion: we won't build on it as it might become incompatible with EL8 due to its nature of tracking ahead and development-focused.
- Between the RockyLinux, AlmaLinx, Oracle Linux as a replacement for CentOS8 we've decided to try RockyLinux
- Experiment with RockyLinux, build artifacts, try if they're backward-compatible with EL8, and if everything works OK - go with that distro as a CI replacement for EL8 when producing the .rpm artifacts.
- Eventually, .rpm artifact produced in the RockyLinux environment could be used by the community to install st2 on any of: CentOS8, RHEL8, OracleLinux, Almalinux.
- From https://rockylinux.org/: "Rocky Linux is an open-source enterprise operating system designed to be 100% bug-for-bug compatible with Red Hat Enterprise Linux®."
- TODO next TSC meeting: Reiterate on v3.7.0 planning, RockyLinux