On Wed, Jul 29, 2020 at 01:51:14PM +0200, Mathias Neumann wrote:
> Hi at all,
>
> as a new Member in the Documentation Team i have read this discussion and
> want to say my opinion about the Workflow with a stable and a developer
> branch.
>
> 1) It makes sense to have a developer Branch (master)
Hi at all,
as a new Member in the Documentation Team i have read this discussion
and want to say my opinion about the Workflow with a stable and a
developer branch.
1) It makes sense to have a developer Branch (master) and an stable.
My suggestion is that the stable documentation contains th
On Mon, May 18, 2020 at 08:05:21AM -0400, Wayne Stambaugh wrote:
> On 5/17/20 3:53 PM, Nick Østergaard wrote:
> > On Sun, 17 May 2020 at 21:00, wrote:
> >>
> >> Yes, it's done :-)
> >>
> >> But if anyone wants to take an issue, I'll be happy too ;-)
> >>
> >> I've left 2 issues which involves redo
be cherry-pick later
>> - followed by 1 commit on master documenting v6 behavior and this one should
>> never be cherry-pick
>
> If that works for now, please do that. If you have changes that
> applies to 5.1, don't hold them back. It is better to get it in ASAP,
> i
sco
>
> ----- Mail original -----
> From: "Nick Østergaard"
> To: "f dos santos"
> Date: 17/05/2020 19:19:28
> Subject: Re: [Kicad-doc-devs] Documentation workflow with stable and
> development branch
>
> Hello Francisco
>
> I see you have created
"Nick Østergaard"
To: "f dos santos"
Date: 17/05/2020 19:19:28
Subject: Re: [Kicad-doc-devs] Documentation workflow with stable and
development branch
Hello Francisco
I see you have created a bunch of detailed issues with various details
in the issue-tracker. I assume you a
Hi Francisco
Thank you for your interest and effort. I have added you now, you
should be able to manage the issuetracker, please test it.
Some thoughts about yours:
Tracking things to be updated or changed is better done in the issue tracker.
I think all effort should be focused on the master b
7 matches
Mail list logo
