Guys. what about the pending fix verification effort before the release?
That also matters, to get an idea in terms of when exactly we could
release.
On Wed, May 22, 2013 at 3:28 PM, Pavithra Madurangi wrote:
> Hi all,
>
> Following is the jira status of API-M 1.4.0
> https://wso2.org/jira/secur
Most of the issues have been fixed by the team. Only there are L3s.
The pack building is on the way and we (QA team) need time to verify the
reported jiras and for regression, before giving the ok to release.
On Wed, May 22, 2013 at 3:40 PM, Nirodha Pramod wrote:
> Hi,
>
> Considering that fact
Hi,
Considering that fact that BAM and API-M should be released together we
have to delay BAM release deadline to the same day. @Tharindu, Chamara how
is the status of BAM release? Is it possible to delay it too?
regards,
Nirodha
On Wed, May 22, 2013 at 3:28 PM, Pavithra Madurangi wrote:
> H
Hi all,
Following is the jira status of API-M 1.4.0
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10990
There are 2 L2s and few L3s
Except Google analytics and login to API store with SAML2 web SSO , we've
tested other features. Please refer [1] for more detail. We've run l
