chore: release notes for 0.5.0 (#12556)

Should be a good release.

api/release-notes-internal.md

@@ -4,9 +4,9 @@ For more details about this release, please see the full [technical change log][
 
 ---
 
-# Internal Release 0.4.0
+# Internal Release 0.5.0
 
-This is internal release 0.4.0 for the Opentrons Flex robot software, involving both robot control and the on-device display.
+This is internal release 0.5.0 for the Opentrons Flex robot software, involving both robot control and the on-device display.
 
 Some things are known not to work, and are listed below. Specific compatibility notes about peripheral hardware are also listed.
 
@@ -21,7 +21,10 @@ Some things are known not to work, and are listed below. Specific compatibility
 ## Big Things That Don't Work Yet So Don't Report Bugs About Them
 
 ### ODD
-- Changing the text size on the ODD through the settings
+- While many individual flows work, going in between them often does not, you have to use the secret menu
+- The ODD generally won't synch up to what the robot is doing if the app is controlling it - for instance, if you start a protocol from the app the ODD won't follow along on its own
+- The ODD doesn't really tell you if the robot server hasn't started yet; if a robot looks on but has the name "opentrons", or says it's not network-connected when you know it is, probably the server isn't up yet, give it another little bit
+- It can take a while for the robot to start after installing an update (it's the firmware updates happening on boot). Allow 10 minutes after an update that has a firmware change.
 
 ### Robot Control
 - USB connectivity
@@ -31,15 +34,22 @@ Some things are known not to work, and are listed below. Specific compatibility
 
 ## Reasonably Sized New Things
 ### ODD
-- No more unsightly menu bar at the top
-- You can delete runs  and protocols from the ODD
-- The ODD now displays the firmware version of attached devices. If devices are on different firmwares, it will display them in a list. If this is happening, it means something wasn't updated, and you should restart the robot with that thing connected.
-- More in-depth liquid setup screens
+- More focus on visuals around alignment, sizing, and spacing, especially between screens - this is mostly catchup from removing the menu bar
+- Recently-run protocols is now populated!
+- In general, it's pretty doable to run protocols and pre-protocol from the ODD; give it a try by sending a protocol to the flex with the "send to OT3" button in the desktop app
 
 ### Robot Control
-- Updates to accelerations and speeds from hardware testing
-- Module calibration offsets will now be loaded in protocols once you run it with the script
-- When running the repl, you can disable automatic firmware update by setting the `OT3_DISABLE_FW_UPDATES` environment variable. Please do this rarely, since often you will see weird failures if you have out-of-date firmware.
+- Even more acceleration changes from hardware testing
+- Improved trash bin positioning should mean dropped tips don't go quite as "everywhere"
+- DVT multis return tips a little better now
+- Fixed a bunch of behavior stuff around the 96 with plunger stalls, breaking instruments endpoints, etc. Should be usable now.
+- You should be able to cancel a protocol now without breaking the robot
+- Calibration should raise an error if it got a really bizarre output now
+- Logging overhaul:
+  - CANbus messages (and USB rear panel messages) are logged now; you can see them by downloading serial logs or running `journalctl -t opentrons-api-serial`
+  - We limited what goes in the api logs, removing HTTP access logs and SQL logs and move command spam; they should be more useful now. You can see them by downloading API logs or running `journalctl -t opentrons-api`.
+  - All the above is now in the robot-server unit logs, which can be accessed via `journalctl -u opentrons-robot-server`
+- Protocol analysis should be a _lot_ faster
 
 ## Big Things That Do Work Please Do Report Bugs About Them
 ### Robot Control
@@ -49,7 +59,7 @@ Some things are known not to work, and are listed below. Specific compatibility
 - Pipette and gripper automated offset calibration
 - Network connectivity and discoverability
 - Firmware update for all devices attached when the robot turns on
-- Cancelling a protocol run. We're pretty sure we fixed this so definitely tell us if it's not.
+- Cancelling a protocol run. We're even more sure we fixed this so definitely tell us if it's not.
 
 ### ODD
 - Protocol execution
@@ -65,4 +75,4 @@ Some things are known not to work, and are listed below. Specific compatibility
 ## Smaller fun features
 - Turn on display idle in the display settings for a fun surprise
 - The lights work (don't do anything yet though)
-- Lots of visual updates and improvements in the ODD
+

app-shell/build/release-notes-internal.md

@@ -3,22 +3,25 @@ For more details about this release, please see the full [technical changelog][]
 
 ---
 
-# Internal Release 0.4.0
+# Internal Release 0.5.0
 
-This is 0.4.0, an internal release for the app supporting the Opentrons Flex.
+This is 0.5.0, an internal release for the app supporting the Opentrons Flex.
 
 This is still pretty early in the process, so some things are known not to work, and are listed below. Some things that may surprise you do work, and are also listed below. There may also be some littler things of note, and those are at the bottom.
 
 ## New Stuff In This Release
-- No real big changes in the desktop app this week
+- Protocol analysis of Flex protocols is faster
+- Overhaul of pipette data generally should mean that 
+  - Flex instrument calibration shows up now
+  - 96-channels should show up in the instruments page and work in protocols
+  - We don't cause a lot of instrument polling anymore on the robot
 
 
 ## Big Things That Don't Work Yet So Don't Report Bugs About Them
 - Attach, detach, and calibration flows for anything from the protocol setup page
 - USB connectivity
 - Pipette/gripper firmware update on attach: if you need to attach a new instrument, attach it and then power-cycle the robot
-- If you leave the app on the device page it will very frequently ask what instrument is connected, which causes problems; don't leave the app on the device page of the robot for a really long time
-- The app always says instrument calibration is out of date
+
 
 ## Big Things That Do Work Please Do Report Bugs About Them
 - Connecting to a Flex