Sooryakumar Thoppan

Thanks for the response. 1. Version is, 'org.ajoberstar.reckon' version '0.16.0' 2. Reckon Block is, reckon { stages('beta','rc', 'final') scopeCalc = calcScopeFromProp() stageCalc = calcStageFromProp() } 3. Is the developer's branch...

``` >git log --graph --oneline --decorate feature/CD-5602-versioninghappypath * 844d8c3 (HEAD -> feature/CD-5602-versioninghappypath, origin/feature/CD-5602-versioninghappypath) CD-6502- build gradle changes * 9c62c83 (tag: 1.2.0-rc.1, origin/master, origin/HEAD) Merge pull request #6 from xxx/feature/CD-5602-versioninghappypath |\...

As per our expecting flow, 1.1.0 is the final version, which we think to convert after qa testing of 1.1.0-rc-1 & 1.1.0-rc.2 completed. 1.1.0-rc.1 & 1.1.0-rc.2 are two different release...

great. thanks for the suggestion & recommendation. Let me check with different scenarios and update this thread with outcomes

I have tried few scenarios and need a help **Scenario 1:** Having two release candidates in the master branch 0.1.0-rc.1 0.1.0-rc.2 QA testing rc.1 and try to make rc.1 alone...

Thank you for the response! still am trying to evaluate the reckon plugin against the "Trunk Based Development". Need a quick thought of yours on using reckon on TBD approach....