Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of ted.dunning@gmail.com
 designates 209.85.210.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <b645fb05d74f303c317b8077599e1af2@cs.helsinki.fi>
References: <b645fb05d74f303c317b8077599e1af2@cs.helsinki.fi>
From: Ted Dunning <ted.dunning@gmail.com>
Date: Tue, 14 May 2013 09:14:13 -0700
Message-ID: 
 <CAJwFCa19vh+jEo_m2wb1YMBoEz=qtbAY0JtNufJbRtQQwciJXg@mail.gmail.com>
Subject: Re: [SANDBOX] Adding one more shortest path algo to Graph?
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=089e014953e0605ada04dcafee46

--089e014953e0605ada04dcafee46
Content-Type: text/plain; charset=UTF-8

On Tue, May 14, 2013 at 8:55 AM, Rodion Efremov <
rodion.efremov@cs.helsinki.fi> wrote:

> The reason I contact you is that I wanted to make sure that I understand
> the process. (Bare with me, as this is the very first time I contact ANY
> open-source community.) Now, is the following procedure acceptable?
>
> 1. Create an issue I in JIRA with type 'New feature'
> 2. Clean my working dir with 'mvn clean' to get rid of everything
> irrelevant
> 3. Create the patch with 'svn diff > my.patch'
> 4. Attach my.patch to I
> 5. Wait for any response R from the community
> 6. If R is of type 'something is unfunky'
> 7.     Improve local repo
> 8.     Go to step 2
> 9. Celebrate
>

Yes.  This is a fine procedure to follow.  You might be able to economize
some steps regarding the patch creation, but the flavor is correct.

Also, the polarity of the of 6 might be reversed.  I am sure you have it
right in your head.

--089e014953e0605ada04dcafee46--