I agree with Udara. We could take the following approach to improve the efficiency:
1. Implement deployment policy management logic and service methods in CC without affecting any other modules 2. Implement dpeloyment policy management REST API methods, still this would not affect any other modules 3. Provide API method details to allow UI and CLI to be updated in parallel 4. Update application bean and definition to refer deployment policy ids, this can be done in parallel 5. Once 1, 2 and 4 are done, remove Application Policy and Chid Policy classes in Autoscaler 6. Rename previous Deployment Policy class in Autoscaler to Application Policy and add the new definition 7. Fix references to previous Deployment Policy in Autoscaler Thanks On Thu, Feb 12, 2015 at 11:20 PM, Udara Liyanage <ud...@wso2.com> wrote: > Hi, > > I started working on new branch. However it has lot of compilation > failures. I started fixing few, but there are many. It is true that we are > changing/adding some functionality which it is OK to functions not to work > properly. But we can avoid compilation issues IMO. We can change back end > first and then fix Rest API or some way. > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
