ACP agent and automations are in to main, so I think maybe we have all the features we wanted to get in? So we could potentially feature-freeze a branch if we want to? cc: @wooden-umbrella-84098 @elegant-branch-54423 But, I’d love to make it possible to specify different language model profiles for automations and I have a PR open but not tested, I could try to hustle on that if people think it’s worth it.

@hundreds-twilight-32833 @ancient-car-4311 WDYT? Should we wait 1 more day for the LLM profiles integrated w/ Automations? Or are you already in the process of building the release?

Are automations stable now? I'd like to re-test a bit and get some others to test as well first

@quick-window-91705 is working on the npm/docker flows, and I believe part of that is making sure we're pinned to the right version of automations (although could have these details wrong)

@hundreds-twilight-32833 I just tried creating a CRON automation that simply echos hello world That worked for me (off the latest commit on main) If you can check it out and let me know what issue you're seeing I can see if we simply need to bump the package version

🫡 On it

we’re not waiting for things to be stable, just going to do a feature freeze. so we can always make things more stable

good point! It might be good to give ourselves the next few days to test. WOuld it be possible to get the LLM profiles for automations in tonight? That way we give ourselves the next 3 days for testing / hardening

we’re not waiting for things to be stable, just going to do a feature freeze. so we can always make things more stable

Oh I understand now. Call it frozen, fix anything on the branch but don't merge new things in. (right?)

yeah, that’s correct. btw: if our launch is June 3rd or so, what are the next steps before launch? do we start sharing this with potential launch partners?

I think we are going to move this to Beta (out of incubator status) and then work on getting more input from the community first. Then next week a bug bash. I'm not sure on anything more specific at the moment leading up to the full MVP ready release

We are working on a launch plan with marketing, however we do need to get more feedback on a stable release once we are ready. We should share it with the community. This needs to be managed, so we should be more explicit about what actions we're goign to take to 1) get it out there, 2) get people to try it, 3) how we collect feedback

yeah, agreed. so maybe we can try to do a feature freeze tomorrow morning, stabilize for a couple days and then cut a beta release on Friday or something?

How are we feeling about a feature freeze today? It sounds like we might have some outstanding PRs to merge first, but maybe we can determine which need to get in and when we can freeze?

Yeah, I need to get the canvas PR in, which I think is blocked by version bumps on sdk and automations. i got a little distracted on those, will take a look what else needs to be done to get them in