time boxed releases versus release on master merge #11
Description
this relates a little to this issue: #10
what if folks want to move to a time boxed release approach; so that merges to master just do a developer build (so a mvn fabric8:deploy in some namespace); then later on they trigger a CD release via a separate pipeline?
So we'd want a developer pipeline for master; then a Jenkins job folks can trigger to do a release when they choose to do.
How should we configure/record that? As we'd want 2 Jenkins jobs really - one for master and one for 'time boxed releases'?
Maybe the simplest approach for this use case is to create a release branch with a Jenkinsfile which runs the CD release pipeline - from the master branch (so you never need to really edit the release branch unless you wanna edit the release pipeline)?