I have tested following in single node as well as cluster

 - aar deployment
 - aar deployment with security policy

No issues found.

[x] - Stable - Go ahead and release.


Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: [email protected]
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
<http://firzhanblogger.blogspot.com/>  <http://suhothayan.blogspot.com/>*
*twitter: https://twitter.com/firzhan007 <https://twitter.com/firzhan007> |
linked-in: **https://www.linkedin.com/in/firzhan
<https://www.linkedin.com/in/firzhan>*

On Wed, Dec 23, 2015 at 10:25 AM, Himasha Guruge <[email protected]> wrote:

> Hi All,
>
> I have tested following.
> [1]. Load testing against stateless rule services.
>
> No issues found.
>
> [x] - Stable - Go ahead and release.
>
>
> Thanks,
> Himasha
>
> On Tue, Dec 22, 2015 at 8:48 PM, Milinda Perera <[email protected]> wrote:
>
>> Hi Devs,
>>
>> WSO2 BRS 2.2.0 RC Release Vote
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/browse/BRS-134?filter=12526
>>
>> Please download BRS 2.2.0 RC and test the functionality and vote. Vote
>> will be open for 72 hours or as needed.
>>
>> Binary distribution at:
>>
>> https://svn.wso2.org/repos/wso2/people/milindap/BRS/releases/RC/wso2brs-2.2.0.zip
>>
>> Maven staging repository:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2brs-233/
>>
>> The tag to be voted upon :
>> https://github.com/wso2/product-brs/tree/v2.2.0-RC
>>
>>
>> [-] Broken - do not release (explain why)
>> [+] Stable - go ahead and release
>>
>> Thanks and Regards,
>> WSO2 BPS/BRS Team
>>
>> --
>> Milinda Perera
>> Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
> Himasha Guruge
> *Software Engineer*
> WS*O2* *Inc.*
> Mobile: +94 777459299
> [email protected]
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to