Re: [Tails-dev] (review)[doc] wiki/src/doc/first_steps/rese…

Delete this message

Reply to this message
Autore: spriver
Data:  
To: The Tails public development discussion list
Oggetto: Re: [Tails-dev] (review)[doc] wiki/src/doc/first_steps/reset/linux.mdwn
Hi,


sajolida:
> intrigeri:
>> spriver wrote (07 Jan 2016 21:12:59 GMT) :
>>> Small question; should I add then some child tickets to each page
>>> related to #8043 and then assign those tickets to each branch?
>>
>> I see that when he created #8043 a while ago, sajolida created a bunch
>> of subtasks, that presumably were meant to cover all the work he saw
>> was needed. If there's more work to do in this area, then I would
>> personally advise using the same workflow, and indeed adding subtasks
>> if needed.
>>
>> I can't answer regarding how fine-grained the branches shall be.
>
> That's a bit up to you. Still, I find it useful when each branch
> corresponds to at most one ticket. So you can use the "Feature branch"
> field. And yes, it's better to track the status of this on Redmine,
> setting "Assignee: sajolida", and "QA Check: Ready for QA" when you
> think you're ready. You can send mails as well, but they are a bit
> duplicate if you update everything on Redmine already.
>
> Here I admit that the granularity of the subtasks of #8043 is a bit
> arbitrary and not really consistent, so I won't mind if for example, you
> create new subtickets for different pages or work on #8044 (screenshots)
> and #8045 (path) in the same branch.
>
> Also we use the doc/XXXXX-ticket-description nomenclature for branches
> so it's easier to spot them, keep your repo tidy, etc.
>
> By the way, I can't find your branch doc_disks nor your commit 69cca8d.
> Did you push it?


Thanks for describing. I hope I did it the right way now, I assigned two
child tickets to you and pushed again. Should work now.

Stay tuned, there's coming more stuff in the next days ;)

Cheers!