Looks good (sorry for being late)
[X] +1 Release this package as Apache burr 0.41.0-incubating
[ ] +0 No opinion
[ ] -1 Do not release this package because... (reason required)
Checklist for reference:
[X] Download links are valid
[X] Checksums and signatures are valid
[x] LICENSE/NOTICE files exist
[X] No unexpected binary files in source
[X] All source files have ASF headers
[X] Can compile from source
I installed burr locally and managed to run it - and saw examples.
Few comments (none of them blocking):
General: very nice tooling for building and verification :)
1) Standalone "tool" installation
While installation with `pip install works`, the installation as standalone
tool (`pipx install` or `uv tool install`) - this is what I usually use to
install tools to not clutter my local environment (those are installing
tooling in their own - dedicated venv and add the entrypoints to the PATH).
The error is:
The issue is that when you run `uv tool
install "dist/apache_burr-0.41.0-py3-none-any.whl[start]"` (for example),
it will install uvicorn, but will not install it's entrypoint - this is
what `pipx` and `uv tool` do - they install only entrypoints that are
defined in the main package:
...
+ tavily-python==0.7.19
+ tenacity==9.1.2
+ tiktoken==0.12.0
+ toml==0.10.2
+ tornado==6.5.4
+ tqdm==4.67.1
+ typing-extensions==4.15.0
+ typing-inspect==0.9.0
+ typing-inspection==0.4.2
+ tzdata==2025.3
+ urllib3==2.6.3
+ uvicorn==0.40.0
+ watchdog==6.0.0
+ wrapt==1.17.3
+ zipp==3.23.0
Installed 7 executables: burr, burr-admin-build-ui,
burr-admin-generate-demo-data, burr-admin-publish, burr-admin-server,
burr-demo, burr-test-case
But then burr tries to call "uvicorn" as an executable. This is also a bit
problematic - because if someone has uvicorn installed elsewhere, it might
be first in the path - so you might get different uvicorn . I suggest smth
like this instead:
subprocess.run(
[sys.executable, "-m", "uvicorn", ... ],
)
This is going to always use uvicorn that is installed in the same env as
burr and it should work with `uv tool` or `pipx`
2) When you run `scripts/verify_apache_artifacts.py licenses --rat-jar
apache-rat-0.15.jar` . the script looks for .tar.gz in dist folder by
default, but at that time the source.tar.gz is not in the dist folder (if
you follow the verification process). It might be worth explaining that
you should use the `--artifacts-dir` option to point to the folder where
artifacts are.
3) The local development scripts described in docs are missing (both in the
sources of rc3 and in main branch in repo):
python scripts/build_artifacts.py build-ui # Build UI only
python scripts/build_artifacts.py wheel # Build wheel with UI
4) General suggestion for the tooling scripts of your - I think it might be
useful to add inline-metadata to your scripts
https://peps.python.org/pep-0723/ and leverage `uv run` or `hatch run`
capability of running those scripts (and using one of those in your docs
for copy&pasting). That has the advantage that you do not have to activate
any virtualenv or even install and manage python in order to use your
scripts, each of those scripts gets then automatically it's own virtualenv,
so if you will need to add some per-script dependencies, that will be super
easy and work out of the box. And it will not accidentally use some
activated venv that might have other dependencies. It's a pretty nice way
of turning your python scripts into executable ones. You might even change
their executable bits, add `uv run` or `hatch run` as hashbang and get them
executed by just ./script.py (though that binds you more with uv or hatch
or other selected tools).
J.
On Mon, Jan 12, 2026 at 8:01 AM Stefan Krawczyk <[email protected]>
wrote:
> Looks good.
>
> *[X] +1 Release this package as Apache burr 0.41.0-incubating*
> [ ] +0 No opinion
> [ ] -1 Do not release this package because... (reason required)
>
> Checklist for reference:
> [x] Download links are valid
> [x] Checksums and signatures are valid
> [x] LICENSE/NOTICE files exist
> [x] No unexpected binary files in source
> [x] All source files have ASF headers -- verified using rat-jar
> [x] Can compile from source -- built wheel from source and installed that
>
> I ran the UI with my open AI API key and the demos worked.
> I also ran the examples/hello-world-counter from the environment and it
> worked.
>
> Cheers,
>
> Stefan
>
> On Sun, Jan 11, 2026 at 12:37 PM Elijah ben Izzy <
> [email protected]> wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache burr 0.41.0-incubating
> > release candidate 3.
> >
> > The artifacts for this release candidate can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/burr/0.41.0-incubating-RC3
> > .
> >
> > The Git tag to be voted upon is: v0.41.0. With hash
> > c4bf188079923a7321906120789a0b3ea6cf64d4.
> >
> > Release artifacts are signed with the release manager's GPG key. The KEYS
> > file is available at https://downloads.apache.org/incubator/burr/KEYS.
> >
> > Please download, verify, and test the release candidate.
> >
> > We have three release artifacts, as well as associated signatures
> > - The archive – full source archive of apache burr (incubating)
> > - The wheel
> > - The sdist – source that goes in the wheel
> >
> > For detailed step-by-step instructions on how to verify this release,
> > please see the "For Voters: Verifying a Release" section in the
> > scripts/README.md file -- note we have an updated version that has been
> > further validated with the ability to build from scratch/not use a script
> > -- use this instead (it will be merged in for the next release):
> >
> >
> https://github.com/apache/burr/blob/b412a862f40a39df6feede5358895fbf7b997bd9/scripts/README.md
> > .
> >
> > The vote will run for a minimum of 72 hours.
> > Please vote:
> >
> > [ ] +1 Release this package as Apache burr 0.41.0-incubating
> > [ ] +0 No opinion
> > [ ] -1 Do not release this package because... (reason required)
> >
> > Checklist for reference:
> > [ ] Download links are valid
> > [ ] Checksums and signatures are valid
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files in source
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> > On behalf of the Apache burr PPMC,
> > Elijah ben Izzy
> >
>
