phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasudevan, Ramkrishna S" <ramkrishna.s.vasude...@intel.com>
Subject RE: best development methodology for Apache git?
Date Wed, 29 Jan 2014 07:01:42 GMT
I have not worked on the git repo in apache still.  So we will give patches like in HBase but
prepared using git?  Or it is push/pull requests only? When I worked with the older Phoenix
git repo we used to discuss on the UI provided by github.

Regards
Ram

-----Original Message-----
From: Devaraj Das [mailto:ddas@hortonworks.com] 
Sent: Wednesday, January 29, 2014 12:24 PM
To: dev@phoenix.incubator.apache.org
Subject: Re: best development methodology for Apache git?

Hey James, couldn't we use the jira comments as a way to discuss/feedback, even though we
use git repo?

On Tue, Jan 28, 2014 at 10:47 PM, James Taylor <jamestaylor@apache.org> wrote:
> I know you HBase guys use svn as your source of truth, but Phoenix is 
> using git. With our old git repo which was hosted on github, we'd 
> typically do work locally and then send a pull request to the 
> source-of-truth github repo. That way others could comment on the 
> pending commit before it was pulled in. Pulling it in could be done 
> with a single click by someone with write privileges.
>
> Now, though, our source-of-truth is *not* on github, but on a git repo 
> hosted by Apache. It's only mirrored to github in a read-only manner. 
> Plus, it may be lagging behind the source-of-truth repo.
>
> What's the best, recommended methodology and ui to use for getting 
> feedback pre-commit?
>
> Thanks,
> James

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.

Mime
View raw message