You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nlpcraft.apache.org by Paul King <pa...@asert.com.au> on 2020/06/09 07:36:37 UTC
Re: [VOTE] Branching policy.
+1
Also, it is good practice to close off the vote so that the result is clear
in the email history.
cheers, Paul.
On Fri, May 29, 2020 at 6:31 PM Sergey Kamov <sk...@gmail.com> wrote:
> NLPCrafters,
>
> based on [1] discussion lets start a vote on branching policy:
> - all logical tasks should be split into minimal possible working
> tasks, which can be merged to master independed from each other.
> - each task should be done in separated branch by one developer, and
> merged via PR into master with single summary comment (squash)
> - if several developers have to work together in one branch on one
> task, all developers should be mentioned in this comment, using
> Co-authored-by
>
> https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors
>
>
> Please vote:
> +1 - I agree with the new structure
> 0 - don't care
> -1 - I disagree (explain why).
>
> The simple majority vote will be held for 72 hours and will end on June
> 01, 2020 at midnight MSK.
>
> [1]
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202005.mbox/%3Ce22390c3-2d1b-98de-3c28-9f8d89ebe42c%40gmail.com%3E
>
> Regards,
> Sergey
>
>
Re: [VOTE] Branching policy.
Posted by Paul King <pa...@asert.com.au>.
Ignore my last email. I just saw the result vote. It wasn't threaded in my
email client and the order was not what I was expecting.
Cheers, Paul.
On Tue, Jun 9, 2020 at 5:36 PM Paul King <pa...@asert.com.au> wrote:
> +1
>
> Also, it is good practice to close off the vote so that the result is
> clear in the email history.
>
> cheers, Paul.
>
> On Fri, May 29, 2020 at 6:31 PM Sergey Kamov <sk...@gmail.com> wrote:
>
>> NLPCrafters,
>>
>> based on [1] discussion lets start a vote on branching policy:
>> - all logical tasks should be split into minimal possible working
>> tasks, which can be merged to master independed from each other.
>> - each task should be done in separated branch by one developer, and
>> merged via PR into master with single summary comment (squash)
>> - if several developers have to work together in one branch on one
>> task, all developers should be mentioned in this comment, using
>> Co-authored-by
>>
>> https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors
>>
>>
>> Please vote:
>> +1 - I agree with the new structure
>> 0 - don't care
>> -1 - I disagree (explain why).
>>
>> The simple majority vote will be held for 72 hours and will end on June
>> 01, 2020 at midnight MSK.
>>
>> [1]
>>
>> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202005.mbox/%3Ce22390c3-2d1b-98de-3c28-9f8d89ebe42c%40gmail.com%3E
>>
>> Regards,
>> Sergey
>>
>>