Re: [Kicad-developers] 5.1 branch freeze

Please see the comments about #4328 onnthe issue itself. I don't think you are testimg with the same conditions. ons. 6. maj 2020 12.55 skrev jp charras : > Le 06/05/2020 à 00:09, Nick Østergaard a écrit : > > Mmm, when you mean branch freeze, I assume you really mean that we > > have a string

Re: [Kicad-developers] 5.1 branch freeze

Le 06/05/2020 à 00:09, Nick Østergaard a écrit : > Mmm, when you mean branch freeze, I assume you really mean that we > have a string freeze for the branch. > > I am sorta wondering why we can't enable the CI, for example. [1] > > Also as a heads up, there a couple of critical issues for the

Re: [Kicad-developers] 5.1 branch freeze

Mmm, when you mean branch freeze, I assume you really mean that we have a string freeze for the branch. I am sorta wondering why we can't enable the CI, for example. [1] Also as a heads up, there a couple of critical issues for the 5.1.6 milestone being added after 5.1.6-rc1 [2], most

Re: [Kicad-developers] 5.1 branch freeze

We are just under two weeks out of the 5.1.6 release. If anyone needs any extra time. Please let me know. Thanks, Wayne On 4/16/20 8:19 AM, Wayne Stambaugh wrote: > Done. > > On 4/16/20 7:58 AM, Nick Østergaard wrote: >> Just the tag in git >> >> tor. 16. apr. 2020 13.25 skrev Wayne

Re: [Kicad-developers] 5.1 branch freeze

Hi, On 16.04.20 03:30, Wayne Stambaugh wrote: > The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable > release. Please do not make any commits to the 5.1 branch without first > confirming with the lead dev team and no translated string changes. Presumably that implies that

Re: [Kicad-developers] 5.1 branch freeze

Done. On 4/16/20 7:58 AM, Nick Østergaard wrote: > Just the tag in git > > tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh >: > > Nick, > > Do you need a source archive or just the tag? > > Cheers, > > Wayne > > On 4/16/20 3:58 AM, Nick

Re: [Kicad-developers] 5.1 branch freeze

Just the tag in git tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh : > Nick, > > Do you need a source archive or just the tag? > > Cheers, > > Wayne > > On 4/16/20 3:58 AM, Nick Østergaard wrote: > > Can we have a 5.1.6-rc1 tag then? > > > > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh >

Re: [Kicad-developers] 5.1 branch freeze

Nick, Do you need a source archive or just the tag? Cheers, Wayne On 4/16/20 3:58 AM, Nick Østergaard wrote: > Can we have a 5.1.6-rc1 tag then? > > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh >: > > The 5.1 branch has been frozen in order to prepare for

Re: [Kicad-developers] 5.1 branch freeze

Can we have a 5.1.6-rc1 tag then? tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh : > The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable > release. Please do not make any commits to the 5.1 branch without first > confirming with the lead dev team and no translated string

[Kicad-developers] 5.1 branch freeze

The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable release. Please do not make any commits to the 5.1 branch without first confirming with the lead dev team and no translated string changes. I would like to release on Friday, May 15th if possible so please let me know if

Re: [Kicad-developers] 5.1 branch commits

Oops. At least one of those was mine. Apologies. Cheers, Jeff. > On 6 Nov 2019, at 22:08, Wayne Stambaugh wrote: > > Just a reminder, please do not push any commits to the 5.1 branch unless > it fixes a high priority bug (crash or data loss) without letting the > dev team know. I want to

[Kicad-developers] 5.1 branch commits

Just a reminder, please do not push any commits to the 5.1 branch unless it fixes a high priority bug (crash or data loss) without letting the dev team know. I want to avoid the 5.1.1 and 5.1.3 disasters. Looking at the commits that flew in under the radar I didn't see anything that looked like

Re: [Kicad-developers] 5.1 branch

Cool. Thanks, Tom. > On 19 Jul 2018, at 16:28, Tomasz Wlostowski wrote: > > On 18/07/18 13:06, Jeff Young wrote: >> Hi Tom, et al, >> >> I assume we just need to drop wxDC for the canvas, but that UI constructs >> (such as colour swatches, etc.) would continue to use wxDC? > > To clarify:

Re: [Kicad-developers] 5.1 branch

On 18/07/18 13:06, Jeff Young wrote: > Hi Tom, et al, > > I assume we just need to drop wxDC for the canvas, but that UI constructs > (such as colour swatches, etc.) would continue to use wxDC? To clarify: SCH/PCB preview widgets will also use GAL. Tom > > Thanks, > Jeff. > > >> On 17 Jul

Re: [Kicad-developers] 5.1 branch

Hi Jeff, Yes, for the moment we work to replace wxDC only in places that really need it. So far it was necessary in pcbnew to boost performance, now eeschema suffers the same problem with GTK3. Cheers, Orson On 07/18/2018 01:06 PM, Jeff Young wrote: > Hi Tom, et al, > > I assume we just need

Re: [Kicad-developers] 5.1 branch

Hi Tom, et al, I assume we just need to drop wxDC for the canvas, but that UI constructs (such as colour swatches, etc.) would continue to use wxDC? Thanks, Jeff. > On 17 Jul 2018, at 15:44, Tomasz Wlostowski wrote: > > On 16/07/18 17:54, Wayne Stambaugh wrote: >> I was really hoping just

Re: [Kicad-developers] 5.1 branch

On 16/07/18 17:54, Wayne Stambaugh wrote: > I was really hoping just to fix the wxDC issues with GTK3 rather than > implement GAL unless Tom implemented a wxDC GAL and that is all we > expose for 5.1. The primary goal here is to fix the GTK3 rendering > issues so we can enable wxPython support

Re: [Kicad-developers] 5.1 branch

On 07/16/2018 05:54 PM, Wayne Stambaugh wrote: > I was really hoping just to fix the wxDC issues with GTK3 rather than > implement GAL unless Tom implemented a wxDC GAL and that is all we > expose for 5.1. The primary goal here is to fix the GTK3 rendering > issues so we can enable wxPython

Re: [Kicad-developers] 5.1 branch

Whew, I think that was ~1200 bugs fixed/feature requests handled. Well done, team! Now let's sweep our mailboxes.. Cheers, Orson On 07/16/2018 06:14 PM, Jeff Young wrote: > I started doing some by hand and Orson is right: tedious isn’t the half of > it. I’ll wait for his script. ;) > > >> On

Re: [Kicad-developers] 5.1 branch

I have the script ready to run. It will just change all KiCad bug statuses from 'Fix Committed' to 'Fix Release'. I assume there are no bugs that are marked as 'Fix Committed', but not actually in the master branch, right? Are you ready for an infinite stream of bug tracker notifications? :>

Re: [Kicad-developers] 5.1 branch

Le 16/07/2018 à 17:54, Wayne Stambaugh a écrit : > I was really hoping just to fix the wxDC issues with GTK3 rather than > implement GAL unless Tom implemented a wxDC GAL and that is all we > expose for 5.1. The primary goal here is to fix the GTK3 rendering > issues so we can enable wxPython

Re: [Kicad-developers] 5.1 branch

I started doing some by hand and Orson is right: tedious isn’t the half of it. I’ll wait for his script. ;) > On 16 Jul 2018, at 16:59, Wayne Stambaugh wrote: > > My finger is on the delete key. Fire when ready! > > On 7/16/2018 11:48 AM, Maciej Sumiński wrote: >> I have the script ready

Re: [Kicad-developers] 5.1 branch

My finger is on the delete key. Fire when ready! On 7/16/2018 11:48 AM, Maciej Sumiński wrote: > I have the script ready to run. It will just change all KiCad bug > statuses from 'Fix Committed' to 'Fix Release'. I assume there are no > bugs that are marked as 'Fix Committed', but not actually

Re: [Kicad-developers] 5.1 branch

No time like the present! -S Am Mo., 16. Juli 2018 um 08:49 Uhr schrieb Maciej Sumiński < maciej.sumin...@cern.ch>: > I have the script ready to run. It will just change all KiCad bug > statuses from 'Fix Committed' to 'Fix Release'. I assume there are no > bugs that are marked as 'Fix

Re: [Kicad-developers] 5.1 branch

I was really hoping just to fix the wxDC issues with GTK3 rather than implement GAL unless Tom implemented a wxDC GAL and that is all we expose for 5.1. The primary goal here is to fix the GTK3 rendering issues so we can enable wxPython support again. We need to limit our risk exposure for 5.1.

Re: [Kicad-developers] 5.1 branch

Tom has already prepared a proof-of-concept eeschema with GAL rendering, which still uses the legacy tools. I have some promising results switching the printing system to Cairo GAL. Obviously we will face some unexpected obstacles, but I have high hopes. Cheers, Orson On 07/16/2018 03:40 PM,

Re: [Kicad-developers] 5.1 branch

That would probably be the easiest solution with the least amount of risk. Although you could not run it for point releases because bugs that are only valid for the development branch would get set to fix released which would not be correct. On 7/16/2018 11:08 AM, Maciej Sumiński wrote: > It is

Re: [Kicad-developers] 5.1 branch

It is terribly tedious to go through the bug list and change statuses one by one, so I offer to help with the bug report status fiddling. We may employ Janitor, but I guess it would be better to execute a simple script to change Fix Committed->Fix Released whenever we release a new version.

Re: [Kicad-developers] 5.1 branch

Hi Jeff, I just played with a few of your 5.1 changes. Many are good, but the new netclass management is not as efficient as the current dialog: - Modifying the netclass of a lot of nets is very tedious: the change must be done for each net (this is the major issue). - we cannot see easily

Re: [Kicad-developers] 5.1 branch

On 7/16/2018 10:37 AM, jp charras wrote: > Le 16/07/2018 à 16:09, Jeff Young a écrit : >> I keep seeing issues with “incorrect” ratsnests on the kicad.info >>  forums.  Can >> we put the curved ratsnests into 5.1? > > This artifact exists only in Legacy mode, due to the XOR

Re: [Kicad-developers] 5.1 branch

Le 16/07/2018 à 16:09, Jeff Young a écrit : > I keep seeing issues with “incorrect” ratsnests on the kicad.info >  forums.  Can > we put the curved ratsnests into 5.1? This artifact exists only in Legacy mode, due to the XOR mode used to draw them. curved ratsnests (it can be

Re: [Kicad-developers] 5.1 branch

I can't think of any reason not to change the fix committed bug reports to fix released so if you have the time, have at it. On 7/16/2018 9:54 AM, Jeff Young wrote: > Cool. I’ll wait a few more days to make sure everything is settled down and > then merge the 5.1 stuff to master. > > Should we

Re: [Kicad-developers] 5.1 branch

I keep seeing issues with “incorrect” ratsnests on the kicad.info forums. Can we put the curved ratsnests into 5.1? > On 16 Jul 2018, at 14:54, Jeff Young wrote: > > Cool. I’ll wait a few more days to make sure everything is settled down and > then merge the 5.1 stuff

Re: [Kicad-developers] 5.1 branch

Yes, assuming we can get that to work without dragging in Phoenix. On 7/16/2018 9:27 AM, Jeff Young wrote: > 5.1 is also for the GTK3 fixes, right? > >> On 16 Jul 2018, at 14:23, Wayne Stambaugh wrote: >> >> On 7/16/2018 9:19 AM, Simon Richter wrote: >>> Hi, >>> >>> On 15.07.2018 13:39, Jeff

Re: [Kicad-developers] 5.1 branch

Cool. I’ll wait a few more days to make sure everything is settled down and then merge the 5.1 stuff to master. Should we go ahead and start making the Fix Committed bugs Fix Released, or do we want to wait for the release announcement? > On 16 Jul 2018, at 14:30, Wayne Stambaugh wrote: > >

Re: [Kicad-developers] 5.1 branch

Hey Jeff, We have been manually changing the bug status from fix committed to fix released after a new stable release. AFAIK, the janitor does not handle this. I suppose the janitor could be modified to test for a new release and change the tag for all bugs associated with that release. That

Re: [Kicad-developers] 5.1 branch

5.1 is also for the GTK3 fixes, right? > On 16 Jul 2018, at 14:23, Wayne Stambaugh wrote: > > On 7/16/2018 9:19 AM, Simon Richter wrote: >> Hi, >> >> On 15.07.2018 13:39, Jeff Young wrote: >> >>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there. >> >> What is the

Re: [Kicad-developers] 5.1 branch

On 7/16/2018 9:19 AM, Simon Richter wrote: > Hi, > > On 15.07.2018 13:39, Jeff Young wrote: > >> I renamed my 6.0 branch to 5.1, since most of what it contains goes there. > > What is the difference between 5.1 and 6.0? What goes into which branch? > >Simon > 5.1 is only for the UI

Re: [Kicad-developers] 5.1 branch

Hi Wayne, The other issue is that the Janitor is going to mark my fixes as Fix Committed, and I don’t know if the auto-bug-release facility is smart enough to check the milestone before converting Fix Committed to Fix Released. So we may need to do that first too. Cheers, Jeff. > On 16 Jul

Re: [Kicad-developers] 5.1 branch

Hi, On 15.07.2018 13:39, Jeff Young wrote: > I renamed my 6.0 branch to 5.1, since most of what it contains goes there. What is the difference between 5.1 and 6.0? What goes into which branch? Simon signature.asc Description: OpenPGP digital signature

Re: [Kicad-developers] 5.1 branch

Jeff, As a general rule, we merge changes into the development branch and then merge them into the stable release branch after they have been tested. In the past this has only been bug fixes so your case is slightly different. The problem I see with merging your changes into the 5.1 branch first

Re: [Kicad-developers] 5.1 branch

Thanks, JP! I’ll make the fix. > On 16 Jul 2018, at 09:24, jp charras wrote: > > Le 16/07/2018 à 10:10, Jeff Young a écrit : >> Well, rats. I couldn’t figure out why "git rebase —interactive" wasn’t >> showing me any of my >> commits, and it turns out that I somehow accidentally merged them

Re: [Kicad-developers] 5.1 branch

Le 16/07/2018 à 10:10, Jeff Young a écrit : > Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t > showing me any of my > commits, and it turns out that I somehow accidentally merged them all to > origin/5.1 sometime last > night.  Anyway, you don’t have to fetch my private

Re: [Kicad-developers] 5.1 branch

Well, rats. I couldn’t figure out why "git rebase —interactive" wasn’t showing me any of my commits, and it turns out that I somehow accidentally merged them all to origin/5.1 sometime last night. Anyway, you don’t have to fetch my private branch to test it anymore; the kicad 5.1 branch will

Re: [Kicad-developers] 5.1 branch

ma 16. heinäk. 2018 klo 8.48 Nick Østergaard (oe.n...@gmail.com) kirjoitti: > Can you edit anything on them? Can you provide a screenshot of the > preferences dialog? > > https://drive.google.com/file/d/1eq26OWT7TDeBTnbyAfUpUckT5V6MuwU8/view?usp=sharing

Re: [Kicad-developers] 5.1 branch

Can you edit anything on them? Can you provide a screenshot of the preferences dialog? søn. 15. jul. 2018 23.15 skrev Eeli Kaikkonen : > > > su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti: > >> I renamed my 6.0 branch to 5.1, since most of what it contains goes there. >> >>

Re: [Kicad-developers] 5.1 branch

su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti: > I renamed my 6.0 branch to 5.1, since most of what it contains goes there. > > Has anyone had a chance to try out the paged dialogs (Preferences and > Board Setup) on Windows or Linux? They weren’t working for Nick (disabled

Re: [Kicad-developers] 5.1 branch

Le 15/07/2018 à 13:39, Jeff Young a écrit : > I renamed my 6.0 branch to 5.1, since most of what it contains goes there. > > Has anyone had a chance to try out the paged dialogs (Preferences and Board > Setup) on Windows or Linux? They weren’t working for Nick (disabled panels). > > Cheers, >

[Kicad-developers] 5.1 branch

I renamed my 6.0 branch to 5.1, since most of what it contains goes there. Has anyone had a chance to try out the paged dialogs (Preferences and Board Setup) on Windows or Linux? They weren’t working for Nick (disabled panels). Cheers, Jeff. ___