Hi all, Now that 3.1.0 chunk1 has been released, we need to get along with fixing some critical issues that we left over to be patched. Some of these issues require API and design changes, where as some require new features. Therefore, we have decided to go for Carbon 3.2.0 soon after Carbon 3.1.0. Work for Carbon 3.2.0 will initially happen on the trunk, and in order to get started we need to ensure the stability of the trunk. Therefore, we have come up with an action plan.
1. EACH AND EVERY DEVELOPER should go through the recent commits that they have done on the Carbon 3.1.0 branch and apply them to the trunk. If there are any conflicts with someone else's commits, please send a mail to this list. IMPORTANT: Please go through all your commits and complete adding them on to the trunk by 5.00pm (IST) tomorrow (14th December 2010). 2. While this process is going on, we will write a script to verify that each and every commit made to the branch has a corresponding commit to the trunk. If we are to come up with process to ensure that this script is running smoothly, we will inform this list. Also, we are planning to discuss what they script will do, and what mechanisms that it will use to determine any conflicting commits etc. Thanks, Senaka. -- *Senaka Fernando* Associate Technical Lead & Product Manager - WSO2 G-Reg; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
