11945 2017-08-17 19:51:21 +0000 Release candidate builds should generate BSPs for the release. 2020-04-09 15:12:22 +0000 1 1 5 Infrastructure AutoBuilder autobuilder unspecified x86 Multiple RESOLVED WONTFIX Medium enhancement Future 1 tracy.graydon unassigned infras.ab.watcher Infras.watcher mhalstead pidge randy.macleod stephano tracy.graydon --- --- Don't know oldest_to_newest 75963 0 tracy.graydon 2017-08-17 19:51:21 +0000 Currently, for Major/Minor/Point releases, we generate the BSP tarballs via the release staging scripts (living at http://git.yoctoproject.org/cgit/cgit.cgi/release-tools). Note that we do not generate BSP blobs for milestones. While the scripts do this adequately, it would be ideal for these to be generated by the build system. This may or may not be trivial to do, since we don't necessarily generate BSP packages for all the platforms that we build. We may need to be able to turn that on/off for a given platform. i.e. We wouldn't package that for *-lsb builds or we might want to turn off, say mpc8315e-rdb (just as an example). If this is makes sense to do, it will reduce the overhead in staging a release, as well as the opportunity for something to fail. When the script fails due to loss of an ssh session or whatever, someone has to go in and figure out what barfed, reset some things or restore files in the staging dir, and then try again. 86966 1 randy.macleod 2020-04-09 15:12:22 +0000 We want to encourage people to use the git repos rather than the tarballs.