Home | History | Annotate | Download | only in antlr-3.4

Lines Matching full:branch

51 The main development branch of ANTLR is stored within the Perforce SCM at:
185 branch of the toolset should never be modified to contain a release
233 of the plugin, so when we release we must change the main branch of
297 0) Run a build of the main branch and check that it is builds and
300 1) First make a branch from main into the target release
305 --- Use main development branch from here ---
308 development branch, so we don't deploy what is now the new release
339 6) Run a build of the main branch:
345 7) Submit the pom changes of the main branch to perforce.
353 9) You are now finished with the main development branch and should change
354 working directories to the release branch you made earlier.
356 --- Use release branch from here ---
358 10) Check out all the pom.xml files in the release branch (and if you are
390 14) Run a build of the release-3.1.3 branch:
396 15) Submit the pom changes of the release-3.1.3 branch to perforce.
406 17) The final step is that we must update the main branch pom.xml for
411 under the main (that's the MAIN branch, not the release branch)
415 probably rebuild the main branch and let it run the junit