Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
arm4b opened this issue Dec 29, 2021 · 1 comment
Closed
Labels
TSC:meeting StackStorm Technical Steering Committee Meetings related topics

Comments

@arm4b
Copy link
Member

arm4b commented Dec 29, 2021

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.

TSC Meeting Host: @armab

Meeting Agenda

New StackStorm-Exchange demo by @cognifloyd

StackStorm v3.7.0 release planning

Brainstorming: StackStorm Maintenance & Security

@arm4b arm4b added the TSC:meeting StackStorm Technical Steering Committee Meetings related topics label Dec 29, 2021
@arm4b arm4b changed the title TSC Meeting (04 Jan 2021): New StackStorm-Exchange, v3.7.0 Planning TSC Meeting (04 Jan 2022): New StackStorm-Exchange, v3.7.0 Planning Jan 4, 2022
@arm4b
Copy link
Member Author

arm4b commented Jan 4, 2022

Participants

Attendees:

Meeting Minutes

Demo: StackStorm-Exchange refactoring by @cognifloyd

  • Original RFC Discussion: [RFC] Use Github Actions for StackStorm-Exchange CI and Maintenance #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:

StackStorm v3.7.0 release planning

  • 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 CentOS 8 EOL end 2021 #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

Brainstorming: StackStorm Maintenance & Security (Out of time)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TSC:meeting StackStorm Technical Steering Committee Meetings related topics
Projects
None yet
Development

No branches or pull requests

2 participants