Hi Harrissou
> On 10 Jul 2020, at 10:45, DelazJ wrote:
>
> Hi all,
>
> I think that the changes should be considered in the light of another fact:
> the updating of the documentation. I don't know where/when to integrate it
> but keep in mind that the docs team is also interested in a clear,
Hi all,
I think that the changes should be considered in the light of another fact:
the updating of the documentation. I don't know where/when to integrate it
but keep in mind that the docs team is also interested in a clear,
detailed, non-developer oriented description generated issue reports.
O
Hi
> On 7 Jul 2020, at 08:26, Matthias Kuhn wrote:
>
> Thanks Charles and Tim,
>
> I this kind of semi-automated process with clear rules is a very good balance
> for increasing changelog quality and decreasing the load on developers to
> write changelog entries last minute.
>
>
Great - I
Thanks Charles and Tim,
I this kind of semi-automated process with clear rules is a very good
balance for increasing changelog quality and decreasing the load on
developers to write changelog entries last minute.
If we want some tech-fancy stuff in the backend, a github workflow could
be wri
Hi
> On 7 Jul 2020, at 01:19, Nyall Dawson wrote:
>
> Hi Tim,
>
> Thanks for your hard work here!
>
>> 2) Tasked Charles to read each PR that has a ‘Feature’ label as it comes in
>> and in the comments section, nudge the author if the description is not
>> clear / well described. Would be gr
Hi Tim,
Thanks for your hard work here!
> 2) Tasked Charles to read each PR that has a ‘Feature’ label as it comes in
> and in the comments section, nudge the author if the description is not clear
> / well described. Would be grateful if the PR gatekeepers could hold back on
> merging Feature
