Hi Imesh,

STRATOS-148 <https://issues.apache.org/jira/browse/STRATOS-148> is already
fixed.

Thanks
Sajith


On Mon, Dec 2, 2013 at 3:47 PM, Imesh Gunaratne <[email protected]> wrote:

> Hi Devs,
>
> This is regarding the next milestone. I could find following tasks tagged
> for this milestone at the moment [1]:
>
> *Tasks Unresolved*
>
>    *Issue Type* *Key* *Summary*  Bug 
> STRATOS-229<https://issues.apache.org/jira/browse/STRATOS-229> Autoscaler
> component shouldn't bundle drools into the autoscaler jar but the feature
> Sub-task STRATOS-119 <https://issues.apache.org/jira/browse/STRATOS-119> 
> STRATOS-138
> HA and scaling support for the instances using Region and Zone  Sub-task
> STRATOS-120 <https://issues.apache.org/jira/browse/STRATOS-120> STRATOS-138
> Support to define various transports from the cartridge definition
> Sub-task STRATOS-124 <https://issues.apache.org/jira/browse/STRATOS-124> 
> STRATOS-138
> Remove ProxyPort and deploymnet from cartridge definition  Sub-task
> STRATOS-125 <https://issues.apache.org/jira/browse/STRATOS-125> STRATOS-138
> Clean up features from Cloud controller  Sub-task 
> STRATOS-147<https://issues.apache.org/jira/browse/STRATOS-147> STRATOS-144
> Fault handling scenarios for Stratos cartridge instances implementation:
> Network Issue  Bug 
> STRATOS-148<https://issues.apache.org/jira/browse/STRATOS-148> Remove
> Repo Information Service of SC (Stratos Manager)  Sub-task 
> STRATOS-166<https://issues.apache.org/jira/browse/STRATOS-166> STRATOS-138
> Registry persitance for Topology in CC  Improvement 
> STRATOS-184<https://issues.apache.org/jira/browse/STRATOS-184> Use
> same knowledge base session for evaluate rules and update objects
> Improvement STRATOS-188<https://issues.apache.org/jira/browse/STRATOS-188> 
> Removing
> redundant variables in topology cluster model  Bug 
> STRATOS-209<https://issues.apache.org/jira/browse/STRATOS-209> Autoscaler
> throwing exceptions when unsubscribe from a cartridge  Bug 
> STRATOS-210<https://issues.apache.org/jira/browse/STRATOS-210> Error
> while starting Autoscaler with the default policy: economyPolicy  Sub-task
> STRATOS-219 <https://issues.apache.org/jira/browse/STRATOS-219> STRATOS-97
> Implement Load Balancer Static Configuration  Task 
> STRATOS-225<https://issues.apache.org/jira/browse/STRATOS-225> Test
> Rest API Functionality  Task 
> STRATOS-226<https://issues.apache.org/jira/browse/STRATOS-226> Support
> Cartridge Definition Deploying through Rest API  Improvement 
> STRATOS-227<https://issues.apache.org/jira/browse/STRATOS-227> Incorporate
> commit feature for cartridge agent deployment synchronizer  Sub-task
> STRATOS-236 <https://issues.apache.org/jira/browse/STRATOS-236> STRATOS-100
> Create a separate partition deployer  Sub-task 
> STRATOS-237<https://issues.apache.org/jira/browse/STRATOS-237> STRATOS-100
> AutoScaler API  Sub-task 
> STRATOS-238<https://issues.apache.org/jira/browse/STRATOS-238> STRATOS-136
> Update Stratos Installer to support Message Broker  Sub-task 
> STRATOS-137<https://issues.apache.org/jira/browse/STRATOS-137> STRATOS-134
> Remove Stratos agent related code from the Stratos componets
> *Tasks Completed*
>
>    *Issue Type* *Key* *Summary*  Improvement 
> STRATOS-223<https://issues.apache.org/jira/browse/STRATOS-223> Add
> all levels of comments to the AutoscaleAlgorithm API  Bug 
> STRATOS-194<https://issues.apache.org/jira/browse/STRATOS-194> Error
> while CEP is starting  Bug 
> STRATOS-233<https://issues.apache.org/jira/browse/STRATOS-233> Load
> balancer assembly has wso2server.bat in bin folder
>
>
> Please update this thread once tasks are resolved. Once everything is
> ready we could mark M4. Information related to milestones are being
> discussed in thread "[Discuss] Stratos 4.0.0 release process".
>
> [1] https://issues.apache.org/jira/browse/STRATOS/fixforversion/12325285
>
>
> Many Thanks
> Imesh
>



-- 
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.*
*AMIE (SL)*
*Blog: http://sajithblogs.blogspot.com/ <http://sajithblogs.blogspot.com/>*
*Mobile: +94772269575*

Reply via email to