Hi,
On Thu, Dec 10, 2015 at 10:57 AM, Akila Ravihansa Perera wrote:
> Hi Isuru,
>
> The problem is master branch will have not only bug fixes but also new
> features and backward incompatible API changes which should not go to a
> patch release.
>
If there are new features with API changes, IMO
On Thu, Dec 10, 2015 at 10:57 AM, Akila Ravihansa Perera wrote:
> Hi Isuru,
>
> The problem is master branch will have not only bug fixes but also new
> features and backward incompatible API changes which should not go to a
> patch release.
>
When we develop new feature and fix the bug, we can
Hi Isuru,
The problem is master branch will have not only bug fixes but also new
features and backward incompatible API changes which should not go to a
patch release.
Thanks.
On Thursday, 10 December 2015, Isuru Haththotuwa wrote:
> +1, will cherry pick the commits to master.
>
> On Thu, Dec
+1, will cherry pick the commits to master.
On Thu, Dec 10, 2015 at 9:37 AM, Akila Ravihansa Perera
wrote:
>
>
> On Wed, Dec 9, 2015 at 10:58 PM, Rajkumar Rajaratnam
> wrote:
>
>> Hi Isuru,
>>
>> We have rebased stratos-4.1.x branch into master branch. We should
>> continue the development in m
+1 for the release. verified following:
1. Build source with integration test.
2. Application deployment and undeployment with samples in Kubernetes IaaS.
3. CEP and DAS extensions distribution.
4. Tested metering and monitoring feature with DAS HA setup in Kubernetes
IaaS.
Thanks.
On Wed, Dec 9
On Wed, Dec 9, 2015 at 10:58 PM, Rajkumar Rajaratnam > wrote:
> Hi Isuru,
>
> We have rebased stratos-4.1.x branch into master branch. We should
> continue the development in master branch from now onwards.
>
+1
We should continue our dev work on master branch and do the 4.1.x releases
from stra
Thanks Imesh.
I will deploy a sample with routing services and in-container support, and
keep update here.
-D
On Wed, Dec 9, 2015 at 11:29 AM, Imesh Gunaratne wrote:
> Hi David,
>
> On Wed, Dec 9, 2015 at 2:34 PM, David Hbase wrote:
>
>> Hi, Team
>>
>> Need to confirm the "container and in-co
Hi David,
On Wed, Dec 9, 2015 at 2:34 PM, David Hbase wrote:
> Hi, Team
>
> Need to confirm the "container and in-container multi-tenancy capability".
> Is this means we can setup the Different Tenancy App within one Docker
> Host or Not?
>
> Container multi-tenancy would use a separate set of c
Observed the stacktrace [1] at application undeployment in EC2. However the
no impact on functionality, hence not a blocker for the release. Related
jira [2].
[1].
[2015-12-09 17:15:38,789] INFO
{org.apache.stratos.cloud.controller.iaases.JcloudsIaas} - Member
terminated: [member-id]
wso2as-521-
+1. Verified:
1. Application deployment, signup addition/removal, and application
undeployment on EC2
2. Application deployment/undeployment on Kubernetes.
On Mon, Dec 7, 2015 at 4:52 PM, Gayan Gunarathne wrote:
>
> Hi All,
>
> This is the third release candidate of Apache Stratos 4.1
Hi Isuru,
We have rebased stratos-4.1.x branch into master branch. We should continue
the development in master branch from now onwards.
Thanks,
Raj.
On Wed, Dec 9, 2015 at 10:39 PM, Isuru Haththotuwa
wrote:
>
>
> On Wed, Dec 9, 2015 at 10:38 PM, Isuru Haththotuwa
> wrote:
>
>> This is not co
[
https://issues.apache.org/jira/browse/STRATOS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa updated STRATOS-1637:
---
Fix Version/s: (was: FUTURE)
4.2.0
> Restore Initial Artifact
[
https://issues.apache.org/jira/browse/STRATOS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048985#comment-15048985
]
Isuru Haththotuwa commented on STRATOS-1637:
Fixed with commits 647cb07a2c31
[
https://issues.apache.org/jira/browse/STRATOS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa resolved STRATOS-1637.
Resolution: Fixed
> Restore Initial Artifacts after a Signup is Removed for a Tena
On Wed, Dec 9, 2015 at 10:38 PM, Isuru Haththotuwa
wrote:
> This is not committed to stratos-4.1.x branch.
>
Correction: This is now committed to stratos-4.1.x branch.
>
> On Tue, Dec 1, 2015 at 7:34 PM, Isuru Haththotuwa
> wrote:
>
>> Sent a PR [1] with the fix.
>>
>> [1]. https://github.com/
This is not committed to stratos-4.1.x branch.
On Tue, Dec 1, 2015 at 7:34 PM, Isuru Haththotuwa wrote:
> Sent a PR [1] with the fix.
>
> [1]. https://github.com/apache/stratos/pull/498/
>
> On Sun, Nov 29, 2015 at 9:18 PM, Isuru Haththotuwa
> wrote:
>
>>
>>
>> On Fri, Nov 27, 2015 at 11:51 AM,
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/498
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Hi, Team
Need to confirm the "container and in-container multi-tenancy capability".
Is this means we can setup the Different Tenancy App within one Docker Host
or Not?
If yes, then how can we realize this function? is there any wiki or
instruction?
If no, how can we understand these features? We
18 matches
Mail list logo
