List view
This milestone is for tracking breaking changes that we want to make in blueapi 2.0 when it materialises blueapi 2.0: - Is a base container that `village_bluesky` extends - Does not depend on dodal - It and `village_bluesky` both manage their dependencies with uv, renovate, submodules - `village_bluesky` depends on dodal with a submodule - The Helm chart then deploys `village_bluesky` container - Fetches information from file system by calling a daq-config-server - Writes data into tiled and/or with the NeXus service only - In production never* mounts /dls or /dls_sw - In production never* runs with hostNetwork true, always using the epics-gateways - In production always* runs as uid 1000
No due date•0/10 issues closedSee https://github.com/DiamondLightSource/blueapi/issues/509
No due date•3/5 issues closedThere is a list of issues regarding the worker, model classes and the logic around how we wrap around the RunEngine. It is known that it needs to be ready before the release 1.0. Another crucial fact is that the changes are tightly coupled with one another, so it would be best if they are addressed jointly.
Overdue by 1 year(s)•Due by July 31, 2024•16/28 issues closed- Overdue by 4 month(s)•Due by August 1, 2025•17/17 issues closed