On Tue, Jul 20, 2010 at 10:02 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote:
> >>> The usual practice is not to branch again for patch releases. Rather we >>> tag. >>> >> >> +1 for releasing Carbon 3.0.1 from the 3.0.0 branch. This is how we did >> all the other Carbon releases. >> > > Sameera, I don't get it. Usually we do patch releases on a newly created > branch. The new branch is a copy of the previous release branch. For an > example take Carbon 2.0. The original release branch can be found at [1]. > Then we created 2.0.1 branch [2] and 2.0.2 branch [3] for the two patch > releases. For the 2.0.3 release we created another branch [4]. 2.0.1 was > copied from the 2.0 branch and 2.0.2 was copied from the 2.0.1 branch. > > 2.0 numbering was a mistake. We have discussed that in the past. that they should have been 2.x.0 s and not 2.0.x s. This was becase, they were not really patch releases, rather minor releases. We should not do the same mistake with 3.0.0 Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
