This repository has been archived by the owner on Feb 5, 2021. It is now read-only.
Move into NCS #408
Comments
6 tasks
|
The biggest impact the move into NCS has is that we can no longer use automated semantic releases: https://bifravst.github.io/bifravst/docs/guides/AutomateHEXFileBuilding.html ... this also affects that we no longer provide pre-build HEX files that users can use to connect to their instance: https://bifravst.github.io/bifravst/docs/firmware/UsingPrebuildImages.html I think both is super valuable for customers, so I plan to add a |
coderbyheart
added a commit
that referenced
this issue
Jan 25, 2021
This removes all JavaScript dependencies from the repo, so we can easily maintain them outside of NCS (where the firmware is moving to). See #408
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Today we have decided that the best solution is to move this repository into the applications folder of NCS. It does not yet represent a good example for an out-of-tree NCS application and we can also benefit from being a fully integrated application because it requires all changes to NCS to be compatible with the firmware (or the firmware to be adapted in a PR). For customers it means they always get one place to find a working Asset Tracker reference implementation, for each release and for bleeding edge.
This yields the following tasks:
asset_tracker_v2inapplicationssdk-nrfrepositorybifravstrepository (and label themfirmware)See bifravst/bifravst#56
The text was updated successfully, but these errors were encountered: