> Could the rc/qa releases be tagged in git? It'd be helpful to know > what fixes to expect in a given point release. Also, is there an > intention to eventually merge the release-2.0 branch with master, or > is the master branch going to eventually become 2.1? release-2.0 will just keep getting bug fixes, and is the recommended branch for usage (till release-2.1 branch is made down the line). Minor releases (2.0.x) will be made off the release-2.0 branch. Patches going into release-2.0 (bug fixes) get double committed into mainline, but mainline gets other patches as well and is more dynamic, hence not recommended for deployments. 2.1 branch will eventually be made off the mainline. Avati
