Many of us found it convenient to work in github and publish intermediate snapshots in apache review board. I have a somewhat dated writeup about my workflow with git, github and apache svn that you may find something useful in :
http://weatheringthrutechdays.blogspot.com/2011/04/git-github-and-committing-to-asf-svn.html hope that helps. there are caveats but in general it works for me. It also helpful if we want to enable multiple people working on the same patch. And it is much easier to maintain it in sync with trunk that way. -d On Thu, Feb 23, 2012 at 9:11 PM, Paritosh Ranjan <[email protected]> wrote: > Hi, > > I would like to do some small, not so risky commit soon ( hours/days, > depends on when the code is ready ) to get used to the commit process. > I could not find any document on how its done in Apache. > > I will : > > a) Do a build without skipping junit tests > b) If build is successful, then commit it in svn repository > (https://svn.apache.org/repos/asf/mahout/trunk) using my Apache Id and > password ( Using eclipse or some svn utility ). > c) I hope that CI is already in place and the build will be triggered > herehttps://builds.apache.org/job/Mahout-Quality/. I will keep on eye on it > so that it does not fail. > d) If it fails, fix it. And then start again from point "a". > > Is this how it should be done in Apache? If not, please tell. > > Thanks and Regards, > Paritosh >
