Re: [DISCUSS] Move Aria Tosca to Reporting Group 1

2016-11-01 Thread Ran Ziv
No objections here. On Wed, Nov 2, 2016 at 5:09 AM, Suneel Marthi wrote: > +1 for the move. But we still do file the November report correct? and the > next report would be due Jan 2017. > > > > On Tue, Nov 1, 2016 at 10:36 PM, John D. Ament >

Re: JIRA Issue Scheme

2016-11-01 Thread Ran Ziv
Yup, I completely understand. It did however take that first time you pointed it out for me to realize this though, and it's simply that the JIRA issue had been created before then :) I'll make sure all future communication goes through the mailing list. On Wed, Nov 2, 2016 at 4:29 AM, John D.

Re: [DISCUSS] Move Aria Tosca to Reporting Group 1

2016-11-01 Thread Suneel Marthi
+1 for the move. But we still do file the November report correct? and the next report would be due Jan 2017. On Tue, Nov 1, 2016 at 10:36 PM, John D. Ament wrote: > Hey guys > > I typically serve as incubator report manager. Boring job, but someone has > to do it.

[DISCUSS] Move Aria Tosca to Reporting Group 1

2016-11-01 Thread John D. Ament
Hey guys I typically serve as incubator report manager. Boring job, but someone has to do it. Anyways, there's a slight imbalance between the reporting groups (see [1]). Since we're still early, I wanted to propose moving AriaTosca from Reporting Group to Reporting Group 1. Its a new podling,

Re: JIRA Issue Scheme

2016-11-01 Thread John D. Ament
Hi Ran, Thanks for the insight. The biggest I'm trying to point out is to have open discussions on the mailing lists when making these types of decisions. I get that you guys at Gigaspaces are colocated and probably talked about this in your office - would be good to also have the discussion

[jira] [Resolved] (ARIATOSCA-7) Celery-based task executor

2016-11-01 Thread Ran Ziv (JIRA)
[ https://issues.apache.org/jira/browse/ARIATOSCA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Ziv resolved ARIATOSCA-7. - Resolution: Fixed Fix Version/s: 0.1.0 > Celery-based task executor > --

incubator-ariatosca git commit: ARIA-14 Implement initial engine tests

2016-11-01 Thread dankilman
Repository: incubator-ariatosca Updated Branches: refs/heads/ARIA-14-workflow-engine-tests [created] 5a77c4716 ARIA-14 Implement initial engine tests Project: http://git-wip-us.apache.org/repos/asf/incubator-ariatosca/repo Commit:

[jira] [Closed] (ARIATOSCA-7) Celery-based task executor

2016-11-01 Thread Ran Ziv (JIRA)
[ https://issues.apache.org/jira/browse/ARIATOSCA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Ziv closed ARIATOSCA-7. --- > Celery-based task executor > -- > > Key: ARIATOSCA-7 >

[jira] [Reopened] (ARIATOSCA-7) Celery-based task executor

2016-11-01 Thread Ran Ziv (JIRA)
[ https://issues.apache.org/jira/browse/ARIATOSCA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Ziv reopened ARIATOSCA-7: - > Celery-based task executor > -- > > Key: ARIATOSCA-7 >

[jira] [Created] (ARIATOSCA-14) Add tests for workflow engine module

2016-11-01 Thread Dan Kilman (JIRA)
Dan Kilman created ARIATOSCA-14: --- Summary: Add tests for workflow engine module Key: ARIATOSCA-14 URL: https://issues.apache.org/jira/browse/ARIATOSCA-14 Project: AriaTosca Issue Type: Task

[jira] [Closed] (ARIATOSCA-7) Celery-based task executor

2016-11-01 Thread Dan Kilman (JIRA)
[ https://issues.apache.org/jira/browse/ARIATOSCA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Kilman closed ARIATOSCA-7. -- Resolution: Fixed > Celery-based task executor > -- > > Key: