You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
StackStorm/st2#6223. A tentative time frame for python 3.10 support is 1-2 months, if no significant blockers
are encountered. FileMagic is adding Redis as a backend coordinator for unit tests to avoid false positives due to race conditions.
Ravi confirmed Redis 6.2.3 + TLS works correctly and suggests using this version for testing.
MongoDB >4.4 update
guzzijones and Robert from Orquestral have been working on the MongoDB code base and may be available to work in parallel on the MongoDB module upgrade support.
Pack testing against multiple St2 version
#140. Ravi has expressed interest to help with testing multiple versions of StackStorm against packs in the Exchange and will have an engineer get in touch with Dan Stealthii through the GitHub issue.
Ravi has questioned how to improve response times to PRs opened against packs repositories. This is a recurring request and not obviously solved as each pack is maintained by independent developers. This is even more difficult to address where packs can only be tested against pay-for-access APIs and services.
It was suggested that packs be segmented by some sort of categorisation, such as free vs paid service, active maintainer vs no maintainer, St2 version etc..
A future brainstorm session will need to be held to think of a way to better support pack development and fixes in a timely fashion.
Eventlet Retirement
StackStorm/st2#6128. Community express to work on this issue has been seen in the issue, but a clear decision needs to be taken on the path forward. nzlosh expressed the view of making incremental steps, by moving to gevent, being the least disruptive to the code base. Once transitioned to gevent, look at how to progressively migrate to asyncio.
The text was updated successfully, but these errors were encountered:
nzlosh
changed the title
TSC Meeting (18 Auguest 2024)
TSC Meeting (18 August 2024)
Aug 16, 2024
TSC Meeting (18 August 2024)
August 2024 @StackStorm/tsc 1 hour meeting:
Attendees
Present
FileMagic
nzlosh
jk464
Absent
guzzijones
amanda11
rush-skills
bishopbm1
Stealthii
dzimine
cognifloyd
khushboobhatia01
winem
mamercad
mickmcgrath13
Kami
m4dcoder
Agenda
Meeting Minutes
Python 3.10 support
StackStorm/st2#6223. A tentative time frame for python 3.10 support is 1-2 months, if no significant blockers
are encountered.
FileMagic
is adding Redis as a backend coordinator for unit tests to avoid false positives due to race conditions.Ravi
confirmed Redis 6.2.3 + TLS works correctly and suggests using this version for testing.MongoDB >4.4 update
guzzijones
andRobert
from Orquestral have been working on the MongoDB code base and may be available to work in parallel on the MongoDB module upgrade support.Pack testing against multiple St2 version
#140.
Ravi
has expressed interest to help with testing multiple versions of StackStorm against packs in the Exchange and will have an engineer get in touch with DanStealthii
through the GitHub issue.Ravi
has questioned how to improve response times to PRs opened against packs repositories. This is a recurring request and not obviously solved as each pack is maintained by independent developers. This is even more difficult to address where packs can only be tested against pay-for-access APIs and services.It was suggested that packs be segmented by some sort of categorisation, such as free vs paid service, active maintainer vs no maintainer, St2 version etc..
A future brainstorm session will need to be held to think of a way to better support pack development and fixes in a timely fashion.
Eventlet Retirement
StackStorm/st2#6128. Community express to work on this issue has been seen in the issue, but a clear decision needs to be taken on the path forward.
nzlosh
expressed the view of making incremental steps, by moving to gevent, being the least disruptive to the code base. Once transitioned to gevent, look at how to progressively migrate to asyncio.The text was updated successfully, but these errors were encountered: