Re: work-in-progress team branches

[Maxim Cournoyer <maxim.cournoyer@gmail.com>]

Hello,

Christopher Baines <mail@cbaines.net> writes:

[...]

>> Does the following doc addition makes sense?  I've placed it at the end
>> of the 'Managing Patches and Branches' section:
>>
>> --8<---------------cut here---------------start------------->8---
>> 1 file changed, 11 insertions(+)
>> doc/contributing.texi | 11 +++++++++++
>>
>> modified   doc/contributing.texi
>> @@ -2362,6 +2362,17 @@ Managing Patches and Branches
>>  Once the branch has been merged, the issue should be closed and the
>>  branch deleted.
>>  
>> +@cindex work-in-progress branches, wip
>> +@cindex wip branches
>> +Sometimes, branches may be a work in progress, for example, for larger
>> +efforts such as updating the GNOME desktop.  For such cases, the branch
>> +name should reflect this by having the ``wip-'' prefix.  The QA
>> +infrastructure will avoid building work-in-progress branches, so that
>> +the available resources can be better focused on building the branches
>> +that are ready to me merged.  When the branch is not longer a work in
>> +progress, it should be renamed, with the ``wip-`` prefix removed, and
>> +only then should the merge requests be created, as documented earlier.
>> +
>>  @node Debbugs User Interfaces
>>  @subsection Debbugs User Interfaces
>> --8<---------------cut here---------------end--------------->8---
>
> Yep, sounds reasonable.

Great, I've fixed a few typos and pushed as
097de97982f328a79394b197d3836842bcfbac44.

-- 
Thanks,
Maxim