RE: Summary of IRC Meeting in #apachehelix

2014-03-05 Thread Kanak Biscuitwala
I just created  https://cwiki.apache.org/confluence/display/HELIX/API+Redesign+-+Progress so that we have a common place where we can track work and update whenever decisions are made. Kanak > From: kana...@hotmail.com > To: dev@helix.apache.org > Subjec

[jira] [Commented] (HELIX-397) Add tagging information to the REST GET response on /resourceGroups

2014-03-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HELIX-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921992#comment-13921992 ] Hudson commented on HELIX-397: -- SUCCESS: Integrated in helix #1238 (See [https://builds.apach

RE: Summary of IRC Meeting in #apachehelix

2014-03-05 Thread Kanak Biscuitwala
Yes, that sounds like a reasonable plan for 0.7.1. > Date: Wed, 5 Mar 2014 18:12:43 -0800 > Subject: Re: Summary of IRC Meeting in #apachehelix > From: g.kish...@gmail.com > To: dev@helix.apache.org > > Looks like you guys had lot of fun. > > Agree with Ka

Re: Summary of IRC Meeting in #apachehelix

2014-03-05 Thread kishore g
Looks like you guys had lot of fun. Agree with Kanak, the main goal of API works is to get the external interface right and if we want to get there as soon as possible. I would like to finalize the API for all roles not just Administrator. So here is the order I would suggest 1. * Admin AP

[jira] [Commented] (HELIX-397) Add tagging information to the REST GET response on /resourceGroups

2014-03-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HELIX-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921866#comment-13921866 ] Hudson commented on HELIX-397: -- ABORTED: Integrated in helix #1237 (See [https://builds.apach

Re: Review Request 18812: [HELIX-397] REST GET for resources should include tag information

2014-03-05 Thread Kishore Gopalakrishna
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18812/#review36276 --- Ship it! Test case please. - Kishore Gopalakrishna On March 5, 2

Review Request 18812: [HELIX-397] REST GET for resources should include tag information

2014-03-05 Thread Kanak Biscuitwala
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18812/ --- Review request for helix, Zhen Zhang and Kishore Gopalakrishna. Bugs: HELIX-397

[jira] [Created] (HELIX-397) Add tagging information to the REST GET response on /resourceGroups

2014-03-05 Thread Kanak Biscuitwala (JIRA)
Kanak Biscuitwala created HELIX-397: --- Summary: Add tagging information to the REST GET response on /resourceGroups Key: HELIX-397 URL: https://issues.apache.org/jira/browse/HELIX-397 Project: Apache

Summary of IRC Meeting in #apachehelix

2014-03-05 Thread ASF IRC Bot
Summary of IRC Meeting in #apachehelix at Wed Mar 5 18:02:59 2014: Attendees: hsaputra, kanakb, osgigeek - Preface - 3/5/14 morning meeting IRC log follows: ## Preface ## ## 3/5/14 morning meeting ## [Wed Mar 5 18:05:23 2014] : so for those unaware, we decided to do biweekly morning meeting