Feb 2025 meeting stub

[Kelvinrr]

This is mostly concerned with figuring out a better way to perform ISIS releases. As the policy currently exists, I have determined that ISIS releases:

1. Take a non trivial amount of time to complete, 1-2 weeks for 1-2 people, 4 times a year, this time can be used more effectively to solve more support issues.
2. Releases happen too frequently, I wonder if people really need such a fast cadence to releases?
3. The current release model does not let us get new features tested by users fast enough, I do not think RCs are adequate.
   • This is especially relevant with significant changes coming to ISIS
4. Major release policy means great work sits in a PR for a year because they are breaking

We have already moved to solve some of these using automation, despite the challenges with CI/CD with ISIS. But to go the extra mile, I think we should consider making changes to how ISIS is released. I have ideas on how to fix these problems while also keeping a good release cadence. But I would want to include the TC ins those conversations.

Additionally, the LTP has been reviewed internally. So, time permitting, we can move on to a community review. Most likely meet regularly again after this to keep it going.