On Tue, Dec 17, 2013 at 2:49 PM, Abhinandan Prateek <abhinandan.prat...@citrix.com> wrote: > The problem is that while you are verifying the build and someone > pushes some code your commit ids will change on a rebase.
let the build be based on a commit and create the branch on that. Then other commits won't hurt. The rebase be in the discipline of the release manager. I have been looking at the script 'build_asf' and it seems to already have tag functionality. I would like to remove it. my hidden agenda for these remarks is the thought of being able to release from master at any moment. The present form of the build script is to be adjusted for this I think. All the script should do is take a release branch, for instance master, replace the version numbers in the poms and check it in as a RC branch (which should not be touched for anything but transforming the RC to a release) ideally the script will take a commit as parameter to base itself on and could figure out the default as being the last one that was committed on the current branch when started. Can anybody contradict me when I say I am on the rigfht track, please? thanks, Daan
