Flume doesn't accept PR's so fork or not is your choice. Simplest workflow could be keep an updated clone of repo Make the changes Create a patch and upload to JIRA
I think your main concern is how to manage locally. I prefer to keep clone's specific to JIRA's which help me in tracking them easily. It's a little painful like this, but the simplicity makes my life easy. Since each one is different, helps me to keep track of it. In my case I usually work on lot of JIRA's in parallel. Some are simple and some takes few weeks to get in shape. You can choose whatever works for you. Hope it answers your question. On Mon, Sep 28, 2015 at 9:06 AM, IT CTO <[email protected]> wrote: > Hi, > I read the > https://cwiki.apache.org/confluence/display/FLUME/Developers+Quick+Hack+Sheet > > If I write my code where my origin is the > origin https://github.com/apache/flume.git (fetch) > origin https://github.com/apache/flume.git (push) > How can I save my changes while they are being reviewed? > Shouldn't I fork the repo, checkout from my repo so I can save the changes? > > Can someone share his method of work? > Eran > -- > Eran | "You don't need eyes to see, you need vision" (Faithless) -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
