Repository navigation
docs: refresh roadmap to reflect shipped, in-review, and planned work - #976
Open
elijahbenizzy wants to merge 1 commit into
Open
elijahbenizzy wants to merge 1 commit into
elijahbenizzy wants to merge 1 commit into
Conversation
jernejfrank
reviewed
Oct 19, 2026
jernejfrank
left a comment
jernejfrank
left a comment
Contributor
There was a problem hiding this comment.
Thanks for updating this.
I think the roadmap we can keep. Left a small comment about my concern that this doc will soon be out of date again.
Comment on lines
+57
to
+108
| --------- | ||
| In review | ||
| --------- | ||
|
|
||
| Open pull requests. Listing here means the code exists and is being reviewed, not that it will merge | ||
| as-is. | ||
|
|
||
| * **Exception transitions** via ``on_error`` capture and wildcard routing -- | ||
| `#796 <https://github.com/apache/burr/pull/796>`_ (tracks | ||
| `issue #30 <https://github.com/apache/burr/issues/30>`_; this supersedes the earlier | ||
| ``error(APIException)`` sketch that used to live on this page). | ||
| * **Durable execution** (suspend/resume with a durable journal on the context) -- | ||
| `#786 <https://github.com/apache/burr/pull/786>`_; see the design discussion below. | ||
| * **Visual builder and workspace mode** in the Burr UI -- | ||
| `#687 <https://github.com/apache/burr/pull/687>`_. | ||
| * **Claude Code skill** for working on Burr applications -- | ||
| `#644 <https://github.com/apache/burr/pull/644>`_. | ||
| * **Artifact/blob store** for large state values -- | ||
| `#931 <https://github.com/apache/burr/pull/931>`_. | ||
| * **Lower-level parallel streaming** -- `#836 <https://github.com/apache/burr/pull/836>`_. | ||
| * **Mermaid graph visualization** -- `#861 <https://github.com/apache/burr/pull/861>`_. | ||
| * **Aerospike persister** -- `#936 <https://github.com/apache/burr/pull/936>`_. | ||
| * **Google Sheets persister** -- `#932 <https://github.com/apache/burr/pull/932>`_. | ||
| * ``Application.get_prior_action`` -- `#943 <https://github.com/apache/burr/pull/943>`_. | ||
| * **OrcaRouter agent example** -- `#896 <https://github.com/apache/burr/pull/896>`_. | ||
| * **TypeScript implementation** of the core state machine -- | ||
| `#728 <https://github.com/apache/burr/pull/728>`_. | ||
| * **LiteLLM AI gateway integration** -- `#803 <https://github.com/apache/burr/pull/803>`_ | ||
| (closed by inactivity on 2026-10-05 after the author added the requested end-to-end example; | ||
| revivable). | ||
|
|
||
| ---------------- | ||
| Under discussion | ||
| ---------------- | ||
|
|
||
| Design threads on ``dev@burr.apache.org`` and open issues without an implementation yet. | ||
|
|
||
| * **Durable execution design** -- | ||
| `[DISCUSS] Durable execution in Burr <https://lists.apache.org/thread/v9nrtms7nq5noqj2ottw0r0tntohl8s5>`_ | ||
| (May--October 2026); the implementation proposal is `#786`_ above. | ||
| * **Builder direction** (code-picture-code round-tripping, Pyodide, roadmap) -- | ||
| `[DISCUSS] Builder direction <https://lists.apache.org/thread/l9y4nk98wtn2rhpj9xgxszpbvq4psh7c>`_ | ||
| and the earlier | ||
| `[discuss] Graph builder UI <https://lists.apache.org/thread/hst35owhcl8swv967rxlh9tpx75gwlrq>`_ | ||
| (March 2026); related to `#687`_ above. | ||
| * **Google Sheets persister design** -- | ||
| `[DISCUSS] Google Sheets Persister design <https://lists.apache.org/thread/z6rmcsqb5b8t1o80z64cmnok6r6r23yy>`_ | ||
| and `issue #213 <https://github.com/apache/burr/issues/213>`_; related to `#932`_ above. | ||
| * **Interceptor lifecycle hook** -- | ||
| `[discuss] adding interceptor lifecycle hook <https://lists.apache.org/thread/k4sq37opkmx0pywp40kqwqkc7x3yyvgn>`_ | ||
| (November 2025, no implementation yet). | ||
| * **Exception transitions** -- `issue #30`_ remains open while `#796`_ is reviewed. |
Contributor
There was a problem hiding this comment.
I can see how collecting In review and Under Discussion could be useful, but, IMO, this will drift and become stale very fast. Maybe it is enough to just point to open PRs and to search the email threads with the discussion subject?
An alternative is to automate these two blocks via CI, but then we need a discussion which PRs are notable enough to get them on this list (if we just collect all the PRs I do not see much value since they are already on github).
|
|
||
| ------- | ||
| Planned | ||
| ------- |
Contributor
There was a problem hiding this comment.
All of these look exciting to work on, but would be good to have some priorities attached to them or a community mechanism to vote on?
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The roadmap page and the README's Roadmap section listed persistence and hydration as future work, sketched exception transitions that #796 now implements, and ended with a pre-Apache "Burr Cloud" waitlist. This replaces both with a factual status view: what shipped (with doc links), what is in review (one line per open PR), what is under discussion on dev@, and what is still planned. No priorities or dates are asserted; it reports state so contributors can find the live threads.
Reviewers: please check the "Planned" list reflects what the PPMC actually intends to keep.