accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edmon Begoli <ebeg...@gmail.com>
Subject Re: subversion protocol and patches setup
Date Tue, 31 Jul 2012 15:57:33 GMT
Thanks David.

Is there some kind of Apache provided facility when design can be
posted, reviewed, discussed, critiqued and adopted
before any code is written. I am guessing Wiki at the minimum, but
something like Confluence would be great.
(http://www.atlassian.com/software/confluence/overview).

On Tue, Jul 31, 2012 at 11:40 AM, Keith Turner <keith@deenlo.com> wrote:
> I have been naming patches with the ticket number and a count, like
> ACCUMULO-123-1.txt, and attaching that to the ticket.   If I upload a
> new version of the patch I update the count.
>
> If its a large change, we can place the patch on review board [1] for
> code review.
>
> [1] : https://reviews.apache.org/dashboard/
>
> If its a big project, I think its worthwhile to write up a little
> design doc and post that for review on the ticket before you start
> coding.
>
>
> On Tue, Jul 31, 2012 at 11:31 AM, Edmon Begoli <ebegoli@gmail.com> wrote:
>> Folks,
>>
>> What is the protocol for working with accumulo svn, submitting
>> patches, going after unassigned issues, etc,
>> and is there a difference on how committer vs. contributor would work
>> within the svn/Jira lifecycle?
>>
>> I have checked out the accumulo trunk using:
>> svn co https://svn.apache.org/repos/asf/accumulo/trunk/
>>
>> Thank you,
>> Edmon

Mime
View raw message