Re: [Emc-developers] next release discussion: Why not make the branch new

Am 23.08.22 um 15:44 schrieb Jérémie Tarot: hey @lcvette o/ Le mar. 23 août 2022 à 15:15, Small Shop Concepts a écrit : on Gitkraken for QtPyvcp we use the GLO Boards which is basically just an item check list with some good formatting, this way it is recorded what has to be fixed and strik

Re: [Emc-developers] next release discussion: Why not make the branch new

hey @lcvette o/ Le mar. 23 août 2022 à 15:15, Small Shop Concepts a écrit : > on Gitkraken for QtPyvcp we use the GLO Boards which is basically just an > item check list with some good formatting, this way it is recorded what has > to be fixed and strikes through once it has been completed. you

Re: [Emc-developers] next release discussion: Why not make the branch new

on Gitkraken for QtPyvcp we use the GLO Boards which is basically just an item check list with some good formatting, this way it is recorded what has to be fixed and strikes through once it has been completed. you can have an overall running list and other lists so you could perhaps setup a DTG (d

Re: [Emc-developers] next release discussion: Why not make the branch new

On Wed, 10 Aug 2022 at 20:21, Hans Unzner wrote: > Andy, should I assist you by creating such a project? Possibly? (I am working through an email backlog, and only just got to this) -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechani

Re: [Emc-developers] next release discussion: Why not make the branch new

PM To: emc-developers@lists.sourceforge.net Subject: Re: [Emc-developers] next release discussion: Why not make the branch new I think we all agree that setting a date for the next release is mandatory, but nobody of the candidates has the adequate time for that job. Maybe we could start by picking

Re: [Emc-developers] next release discussion: Why not make the branch new

I think we all agree that setting a date for the next release is mandatory, but nobody of the candidates has the adequate time for that job. Maybe we could start by picking the issues/tasks we want to have have/do in/for 2.9. We talked about creating a GitHub project