This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
civilinfrastructureplatform:cip-sw-updates [2020/02/20 04:16] suzuki [CIP Software Updates] |
civilinfrastructureplatform:cip-sw-updates [2020/02/25 07:53] (current) suzuki [Roadmap Iteration #3] |
||
---|---|---|---|
Line 22: | Line 22: | ||
Here is the 3rd iteration work items: | Here is the 3rd iteration work items: | ||
- | - T.B.D. | + | - Prepare minimum required development environment |
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/3|#3]]: Clean a branch relevant to SWUpdate on isar-cip-core | ||
+ | - Commit source codes that already exists in my local machine | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/4|#4]]: Add a demo of ELCE 2019 regarding a safe update feature | ||
+ | - Fix what should have been integrated into the current software update mechanism | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/5|#5]]: Enable u-boot environment redundancy so that software updates can continue if a power failure occurs | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/6|#6]]: Fix how to use binary delta update | ||
+ | - Support new basic features | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/7|#7]]: Support kernel update feature | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/8|#8]]: Support HTTPS connection between client and server | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/9|#9]]: Support rollout feature | ||
+ | - Make a demo better | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/10|#10]]: Fix bug of hawkBit dashboard regarding screen refresh | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/11|#11]]: Add multiple ways to trigger software updates such as push update and arbitrary polling time | ||
+ | - [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/12|#12]]: Automate a demo | ||
The period of this iteration will be from the beginning of Feb 2020 to the end of Jul 2020. | The period of this iteration will be from the beginning of Feb 2020 to the end of Jul 2020. | ||
Line 32: | Line 46: | ||
* Deliverable: demo shown at [[https://events19.linuxfoundation.org/events/embedded-linux-conference-europe-2019/|ELCE 2019]] (the detail is described in [[https://wiki.linuxfoundation.org/_media/civilinfrastructureplatform/cipconferences/sw_updates_wg_mini-summit.pdf|Slides of CIP Mini Summit]]) | * Deliverable: demo shown at [[https://events19.linuxfoundation.org/events/embedded-linux-conference-europe-2019/|ELCE 2019]] (the detail is described in [[https://wiki.linuxfoundation.org/_media/civilinfrastructureplatform/cipconferences/sw_updates_wg_mini-summit.pdf|Slides of CIP Mini Summit]]) | ||
- Make it easier to contribute to SW Updates WG | - Make it easier to contribute to SW Updates WG | ||
- | * Clarify current SW Updates WG's tasks | + | * Clarify current SW Updates WG's tasks [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks|cip-sw-update-tasks]] |
* Provide how to prepare an environment for developing and testing [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-demo|cip-sw-update-demo]] | * Provide how to prepare an environment for developing and testing [[https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-demo|cip-sw-update-demo]] | ||
- Work on remaining tasks for the reference software update mechanism -> Move to the next iteration | - Work on remaining tasks for the reference software update mechanism -> Move to the next iteration |