On Thu, Apr 13, 2017 at 07:53:50AM +0000, Christian Ridderström wrote: > Hi > > We already have CI jobs that run tasks on branch master. We'll keep them > running of course, and likely add more jobs. > > However, do we at some future point also want CI jobs that run based on a > branch/branches related to the upcoming release?
Interesting, I hadn't thought about that. Perhaps we simply want testing on all branches? I imagine this wouldn't be much of a waste because if there is no new commit to a branch, the tests aren't run again, correct? i.e. stale branches would cause no harm. > Sorry for being a bit imprecise here, but I think it'd be useful with a > discussion about how/if we should us the CI system for more tasks related > to release. Particularly to reduce the load of the release manager. > > Would it be bad of me to also ask for a quick summary of how we intend to > use branches/tagging in connection to the different releases? Good question. See our discussion here: https://www.mail-archive.com/search?l=mid&q=20170307000624.qxvce7oyhn6h6rgt%40steph Scott
signature.asc
Description: PGP signature
