docs: Prepare release of jeff-v0.3.0

[denialhaag]

This PR prepares the release of jeff-v0.3.0 by updating the changelog.

[denialhaag]

If you all agree, I'd say we can release jeff-v0.3.0 once #72 is merged. Would any of you prefer we hold off and change something else before a release?

While not a must, I'd like to pin a released version in PennyLaneAI/jeff-mlir#23, so I'd prefer we release rather soon. 🙂

[burgholzer]

This generally looks good to me 👍🏼

I was a bit surprised that this only changes the changelog and no other places. Then I found https://github.com/unitaryfoundation/jeff/blob/6ef694bf977c059252199e0fe15493737c59cf10/impl/py/pyproject.toml which we definitely forgot to update previously. Maybe it is worth checking for other places where a version number is off.

We should probably also start publishing the Python package at some point. Do we have the respective infrastructure set up already?
There is no direct need to do this as part of this release series; but I would assume it to be beneficial in the midterm.

[denialhaag]

I was a bit surprised that this only changes the changelog and no other places. Then I found https://github.com/unitaryfoundation/jeff/blob/6ef694bf977c059252199e0fe15493737c59cf10/impl/py/pyproject.toml which we definitely forgot to update previously. Maybe it is worth checking for other places where a version number is off.

Yeah, good point! We also have changelogs for Python and Rust, but I didn't update those because I figured that only makes sense if we actually release the package and the crate. I'm not entirely sure what the strategy is here. Does every GitHub release necessarily include a PyPI and a crates.io release? Are the versions necessarily aligned?

We should probably also start publishing the Python package at some point. Do we have the respective infrastructure set up already? There is no direct need to do this as part of this release series; but I would assume it to be beneficial in the midterm.

We do have documentation on releasing the Python package, but I don't think that release-please is actually set up. I created #45 a while back to at least track this.

On a related note, I'm now relying on the Python package in PennyLaneAI/jeff-mlir#23, but I'm using uv to install it from GitHub for now.

[dime10]

Looks good thanks!

We can go ahead releasing the spec without worrying about the bindings.
For the Python ones specifically they were never released because they never reached full coverage of the spec.

[burgholzer]

Except for the things David already mentioned, this LGTM 👍🏼