Hi Everybody, This project is getting to the end and I am looking for a last round of reviewers and testers before planning a weekly release with the new process. I opened a pull request (link <https://github.com/jenkins-infra/release/pull/53/files>) with instructions about how to trigger a release but currently, it only covers weekly releases. Our first objective is to successfully release weekly versions from https://release.ci.jenkins.io, then we'll focus on stable and security releases.
For security releases, the way I see it: 1) We add two security profile, one for weekly and the second one for the stable in order to trigger a release from jenkinsci-cert/jenkins:master to https://repo.jenkins-ci.org/releases/ 2) Trigger packaging job(weekly or stable profile), 3) We manually merge from jenkinsci-cert/jenkins:master to jenkinsci/jenkins:master For stable releases: 1) We update the stable <https://github.com/jenkins-infra/release/blob/master/profile.d/stable> profile branch to 'stable-<version>', variable JENKINS_GIT_BRANCH) 2) We trigger stable release job 3) We trigger stable packaging job Another topic that needs clarification is who should be able to trigger a release from release.ci.jenkins.io and who will trigger the different releases? Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8656f659-17ef-49f3-b265-950488fd9b45%40www.fastmail.com.
