You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Edmon Begoli <eb...@gmail.com> on 2012/07/31 17:31:58 UTC
subversion protocol and patches setup
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
Re: subversion protocol and patches setup
Posted by David Medinets <da...@gmail.com>.
On Tue, Jul 31, 2012 at 11:57 AM, Edmon Begoli <eb...@gmail.com> wrote:
> Is there some kind of Apache provided facility when design can be
> posted, reviewed, discussed, critiqued and adopted
> before any code is written.
This list and JIRA tickets seem like good places to discuss code.
Re: subversion protocol and patches setup
Posted by Edmon Begoli <eb...@gmail.com>.
Sounds good.
On Tue, Jul 31, 2012 at 1:12 PM, Keith Turner <ke...@deenlo.com> wrote:
> On Tue, Jul 31, 2012 at 11:57 AM, Edmon Begoli <eb...@gmail.com> wrote:
>> 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).
>>
>
> Not that I know of. What I have seen other apache projects do is post
> a design doc as an attachment on a ticket and then discuss it in the
> comments section of the ticket.
>
>> On Tue, Jul 31, 2012 at 11:40 AM, Keith Turner <ke...@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 <eb...@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
Re: subversion protocol and patches setup
Posted by Keith Turner <ke...@deenlo.com>.
On Tue, Jul 31, 2012 at 11:57 AM, Edmon Begoli <eb...@gmail.com> wrote:
> 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).
>
Not that I know of. What I have seen other apache projects do is post
a design doc as an attachment on a ticket and then discuss it in the
comments section of the ticket.
> On Tue, Jul 31, 2012 at 11:40 AM, Keith Turner <ke...@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 <eb...@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
Re: subversion protocol and patches setup
Posted by Edmon Begoli <eb...@gmail.com>.
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 <ke...@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 <eb...@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
Re: subversion protocol and patches setup
Posted by Keith Turner <ke...@deenlo.com>.
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 <eb...@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