Merge pull request #62 from balena-os/release_v2.26.0+rev1

Release v2.26.0+rev1
This commit is contained in:
Florin Sarbu 2018-11-12 12:25:15 +02:00 committed by GitHub
commit a4c59e93e0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 28 additions and 7 deletions

View file

@ -68,16 +68,37 @@ To contribute send github pull requests targeting this repository.
Please refer to: [Yocto Contribution Guidelines](https://wiki.yoctoproject.org/wiki/Contribution_Guidelines#General_Information) and try to use the commit log format as stated there. Example: Please refer to: [Yocto Contribution Guidelines](https://wiki.yoctoproject.org/wiki/Contribution_Guidelines#General_Information) and try to use the commit log format as stated there. Example:
``` ```
test.bb: I added a test <component>: Short description
[Issue #01]
I'm going to explain here what my commit does in a way that history I'm going to explain here what my commit does in a way that history
would be useful. would be useful.
Changelog-entry: User facing description of the issue
Signed-off-by: Joe Developer <joe.developer@example.com> Signed-off-by: Joe Developer <joe.developer@example.com>
``` ```
The header of each commit must not exceed 72 characters in length and must be in 1 line only.
The header and the subject of each commit must be separated by an empty line.
The subject of each commit must not exceed 72 characters in length but can be wrapped to several lines.
The subject and the footer of each commit must be separated by an empty line.
Every pull request must contain at least one commit annotated with the `Changelog-entry` footer. The messages contained in these footers will be used to automatically fill the changelog on every new version.
Also, every update to `meta-resin` should be separated into its own commit, if the body of that commit contains the following line `Updated meta-resin from X to Y` the generated changelog will include a button to show all the updates in `meta-resin` from the version after `X` to `Y`.
An example of a valid commit updating `meta-resin` is:
```
layers/meta-resin: Update to v2.24.0
Update meta-resin from 2.19.0 to 2.24.0
Changelog-entry: Update the meta-resin submodule from v2.19.0 to v2.24.0
```
Make sure you mention the issue addressed by a PR. See: Make sure you mention the issue addressed by a PR. See:
* https://help.github.com/articles/autolinked-references-and-urls/#issues-and-pull-requests * https://help.github.com/articles/autolinked-references-and-urls/#issues-and-pull-requests
* https://help.github.com/articles/closing-issues-via-commit-messages/#closing-an-issue-in-a-different-repository * https://help.github.com/articles/closing-issues-via-commit-messages/#closing-an-issue-in-a-different-repository

@ -1 +1 @@
Subproject commit 47a185d60ca0af6ff4bd156f1abc31df59e71f40 Subproject commit 426f69000bf1c6f632345a1b63a1572f99c55e77

View file

@ -1,4 +1,4 @@
CONNECTIVITY_FIRMWARES_append = " linux-firmware-ap6212 linux-firmware-brcm43362" CONNECTIVITY_FIRMWARES_append = " linux-firmware-ap6212 linux-firmware-brcm43362"
CONNECTIVITY_MODULES_append = " rtl8189" CONNECTIVITY_MODULES_append_orangepi-plus2 = " rtl8189"
CONNECTIVITY_FIRMWARES_append_nanopi-neo-air = " linux-firmware-bcm43430" CONNECTIVITY_FIRMWARES_append_nanopi-neo-air = " linux-firmware-bcm43430"

View file

@ -9,7 +9,7 @@ SRC_URI = " \
file://0001-Use-modules_install-as-wanted-by-yocto.patch \ file://0001-Use-modules_install-as-wanted-by-yocto.patch \
" "
SRCREV ="3dfd3e9ca67405bdd6352d5c2f887382859e0861" SRCREV ="f6da92d3b2a17630d9decb21c99e4d5597990fa8"
S = "${WORKDIR}/git" S = "${WORKDIR}/git"

@ -1 +1 @@
Subproject commit 8312741e13604a9d166370349061876afb22c0fa Subproject commit a118ee9883101269bb56620074c384b3f582aba4