Our general process is that contributors who are not committers (i.e. you) should attach a patch to a JIRA ticket.
Then committers and others should review the patch and a committer should commit it when there is consensus that it is ready. Ready generally means that the code looks clean, fixes a problem or extends capability and has good test coverage. Style issues aren't a big deal for you to worry about because somebody can revise your patch to match Mahout style. It is nice if that isn't necessary, but it takes a bit of practice to get all the details of that straight. On Mon, Oct 18, 2010 at 11:14 AM, Tim Liu <[email protected]> wrote: > In addition to normal engineering procedures of code checkin, does mahout > have other instructions? > > I'd like to know them before I start to commit code. >
