Hi All, Still we don't have exact policy on parallel branch maintenance on Axis2 project, we discussed this matter up to some extend during the Vancouver Axis2 BOF. Following are some of the ideas we discussed and I would like to define following set of policies on Axis2 project.
1.) At any given time Axis2 at most maintenance 3 parallel branches including trunk. Releases happen only on these three branches unless in a exceptional case such as release to fix security issue in a older version etc. Community can agree on these exceptional cases. IMO above number is feasible when considering number of active contributors of the project. e.g - At the moment we have trunk, 1.6 and 1.5 2.) Notify EOL notice for a specific branch before last two releases on same branch so that user have enough time to make a decision or report bugs for next two releases. Feel free to comment on above items or add more ? Thanks ! -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara
