Re: [Kicad-developers] rc3

Folks, enjoy your vacations. We've all earned them! :) Wayne, if you could please announce on the list when you tag rc3, that would be awesome. Thanks! Adam On Fri, Jun 29, 2018 at 7:27 PM Rene Pöschl wrote: > > What a coincidence. I will also be out of town for the next one and a > half weeks

Re: [Kicad-developers] rc3

What a coincidence. I will also be out of town for the next one and a half weeks. As i can not guarantee that i will have internet access during this time it might be necessary that somebody else tags the final kicad 5 library release. (I should be back at June the 10th late at night CET.) So

[Kicad-developers] rc3

I think we are good to go with rc3. I'm going to tag it tomorrow unless something comes up between now and then. Once rc3 is tagged, I would like to hold off on any commits that are not critical bug fixes. Since I will be out of the country all next week for vacation, this will give users time t

Re: [Kicad-developers] Jenkins e-mails?

Hmmm… just guessing, I just know what works for me… AFAIK gmail strictly respects DMARC policies. Jenkins mails come from "miguelan...@ajo.es ”. ajo.es has a DMARC record, which enforces a 100% reject on “illegal” mails: <<< v=DMARC1;p=reject;pct=100 >

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #3622

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-devel

Re: [Kicad-developers] Jenkins e-mails?

Thanks for digging into this. I use GMail. The last notification I received from Jenkins was Dec 2017. I see now that others have been receiving them as I get the replies they send quoting the original. The messages are not in Spam, so there's something else going on. Does anyone on the list u

Re: [Kicad-developers] Jenkins e-mails?

I checked and I also got the kicad-qa Jenkins mail Seth mentioned. No, I don’t use gmail. I am running my own mail server. I had a quick look into the mail headers and server logs for such a Jenkins mail. I didn’t see anything suspicious that would prevent delivery (at least with my config and

Re: [Kicad-developers] Jenkins e-mails?

Ok thanks, yes those are the ones. Do you use gmail, or what could possibly be the issue here? Clearly the emails reach the dev list. fre. 29. jun. 2018 14.52 skrev Bernhard Stegmaier : > Just FYI… I do receive them, see attached. > Or, do you mean different ones? > > > Regards, > Bernhard > > >

Re: [Kicad-developers] Jenkins e-mails?

Just FYI… I do receive them, see attached.Or, do you mean different ones?Regards,Bernhard--- Begin Message --- See -- Started by upstream project "any-kicad-mirror-head" build num

Re: [Kicad-developers] [PATCH] V5 upgrade documentation

Thanks Nick! On 06/28/2018 06:00 PM, Nick Østergaard wrote: > I have put the upated image live now, and it seems to work. I will try > to revert the removal of the macros. > > Den tor. 28. jun. 2018 kl. 23.21 skrev Nick Østergaard > mailto:oe.n...@gmail.com>>: > > Hi Seth > > Ok, thank

Re: [Kicad-developers] [PATCH] V5 upgrade documentation

Does this mean that we will be able to put the github macros back into the adoc file? I also checked the latest doc build and I did not see the version upgrade section in the kicad documentation as if the include statement failed. Any ideas or am I missing something? Wayne On 06/28/2018 05:21 P

Re: [Kicad-developers] [PATCH v2] Rewrite test for valid characters in names

Thanks Simon, I have just pushed your patch to the master branch. Cheers, Orson On 06/28/2018 08:34 PM, Simon Richter wrote: > Hi Seth, > > On 06/28/2018 07:56 PM, Seth Hillbrand wrote: > >> ​Understood.   What's the impact of the array assignment now?  ​ > > MSVC refuses to compile it. > > I

Re: [Kicad-developers] [PATCH] V5 upgrade documentation

On Fri, Jun 29, 2018 at 12:00:21AM +0200, Nick Østergaard wrote: > I have put the upated image live now, and it seems to work. I will try to > revert the removal of the macros. > > Den tor. 28. jun. 2018 kl. 23.21 skrev Nick Østergaard : > > > Hi Seth > > > > Ok, thank you for your investigation.