GitHub user xintongsong edited a discussion: Time Plan for the first MVP 
version of Flink Agents

We are targeting a MVP version of Flink Agents (0.1.0) in around end of 
September. That is 16 weeks from now, and here is a rough time plan.

# Phase 1: Week 1-3 (Jun 12 - Jul 2)
- [ ] Preparation
  - [x] Build
  - [x] CI (GHA)
  - [ ] Contribution Guidelines
- [ ] Build a simplest workflow: (x) -> (x+1)
  - [ ] [plan] Workflow, Event, Action & Callable
  - [ ] [api] Workflow, Event & Action
  - [ ] [api] Flink datastream / table as input & output
  - [ ] [runtime] Implement a Flink operator that executes the given workflow 
plan
  - [ ] [runtime] Deploy workflow as a Flink job into a Flink cluster
# Phase 2: Week 4-5 (Jul 3 - Jul 16)
- [ ] Build a simple ReAct agent
  - [ ] [plan] Resource & Resource Provider
  - [ ] [api] State (Short-Term Memory)
  - [ ] [api] ChatModel, Prompt, Tool
  - [ ] [api] ReAct workflow
  - [ ] [runtime] State supports
# Phase 3: Week 6-9 (Jul 17 - Aug 13)
- Developing
  - [ ] MCP Server (Tools, Prompts), EmbedModel, VectorStore
  - [ ] Hierarchy Agent & Workflow
  - [ ] Long-term memory
  - [ ] Provide more built-in implementations for ChatModel, EmbedModel and 
VectorStore
- Execution
  - [ ] Per-action state consistency
  - [ ] Async execution
  - [ ] Cross-language invocation
- Operation
  - [ ] Configuration, log & metrics
  - [ ] Event-log & event-listener
  - [ ] Local python runtime
# Phase 4: Week 10-13 (Aug 14 - Sep 10)
TBD. This is the time buffer for delays and additional works discovered during 
the development.
# Phase 5: Week 14-16 (Sep 11 - Oct 1)
- [ ] Documentation
- [ ] Website
- [ ] Release Process

GitHub link: https://github.com/apache/flink-agents/discussions/8

----
This is an automatically sent email for issues@flink.apache.org.
To unsubscribe, please send an email to: issues-unsubscr...@flink.apache.org

Reply via email to