Re: Apache and committer account

2018-01-09 Thread Thomas Nadeau
Exactly. --Tom On Tue, Jan 9, 2018 at 9:40 AM, Tal Liron wrote: > No worries, DJ. The process takes some time to learn... and it doesn't hurt > to have the ICLA on file, ready for when you are voted to be committer. :) > > On Tue, Jan 9, 2018 at 8:07 AM, D Jayachandran < >

Re: Apache and committer account

2018-01-09 Thread Tal Liron
No worries, DJ. The process takes some time to learn... and it doesn't hurt to have the ICLA on file, ready for when you are voted to be committer. :) On Tue, Jan 9, 2018 at 8:07 AM, D Jayachandran wrote: > It was communicated by Ran Ziv, to submit the ICLA, so I

RE: Apache and committer account

2018-01-09 Thread D Jayachandran
It was communicated by Ran Ziv, to submit the ICLA, so I thought I was necessary even to contribute. Now it's clear to me. -Original Message- From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] Sent: Tuesday, January 09, 2018 5:56 PM To: dev@ariatosca.incubator.apache.org Subject: Re:

Re: merging paused until release is completed

2018-01-09 Thread Thomas Nadeau
Yes, to be clear, keep pushing PRs; we're just not merging onto Master right now. --Tom On Tue, Jan 9, 2018 at 8:02 AM, Suneel Marthi wrote: > I don't see why u can't push a PR when a release is in progress as long as > the PRs are not merged until the release is finalized

Re: merging paused until release is completed

2018-01-09 Thread Suneel Marthi
I don't see why u can't push a PR when a release is in progress as long as the PRs are not merged until the release is finalized and have been rebased off of the latest master. Ofcourse you could always have development continue on a different branch if you are comfortable with merging and

Re: merging paused until release is completed

2018-01-09 Thread Thomas Nadeau
I agree for the next release. This was just the easiest approach for me since I had little assistance doing this first one. --Tom On Tue, Jan 9, 2018 at 7:49 AM, John D. Ament wrote: > Does it make sense to create a branch for the release (when prepped) and > merge that

Re: merging paused until release is completed

2018-01-09 Thread John D. Ament
Does it make sense to create a branch for the release (when prepped) and merge that in when done? I'd hate to see development slow down due to the release window in flight. Most other projects don't stop committing while this is happening. On Tue, Jan 9, 2018 at 7:41 AM Thomas Nadeau

merging paused until release is completed

2018-01-09 Thread Thomas Nadeau
I just saw a PR pushed Vaish and realized we probably had not communicated that we're holding off on merging PRs until the release is finished. The reasoning is to leave master in its current state in case anything odd happens and we need to redo the release (which has happened). Note that PRs

Re: Apache and committer account

2018-01-09 Thread Thomas Nadeau
Why are you submitting the ICLA? You only need to do that after you have been voted as a committer by the existing Committers. --Tom On Tue, Jan 9, 2018 at 2:00 AM, D Jayachandran wrote: > Hi All, > > I have already submitted the Apache ICLA and got the below

RE: TOSCA spec compliance on finding target node

2018-01-09 Thread D Jayachandran
Hi Tal, I have raised a JIRA issue for the below item https://issues.apache.org/jira/browse/ARIA-437 This would be contributed by us. Regards, DJ -Original Message- From: Tal Liron [mailto:t...@cloudify.co] Sent: Monday, August 07, 2017 9:01 PM To: dev@ariatosca.incubator.apache.org