search for: dot0

...o account for that change beforehand, so that release testers can do that seamlessly. Currently, we have "rcN" and "final", we should move to "rcN.M" and "dotN" or something similar, to account for the dot releases... So: rc0.1 -> rc0.2 -> rc0.3 -> dot0 -> rc1.1 -> ... -> dot1 -> ... So that, in the script, we chose: "-release 3.4 {-rc2.1 or -final}| and the script will checkout the correct tag of the correct branch. Of course, to not disrupt the current release process, "-rc1" would have to alias to "-rc0.1"...

Hi, A few months ago, I mentioned I was interested in helping to make dot releases for LLVM 3.3. Now that 3.3 has been released, I would like to kick off the process of collecting bug fixes and merging them into the 3.3 branch. I reviewed the previous discussion about dot releases: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/060821.html and I've come up with the following dot