Re: [Kicad-developers] availability
Hi Adam If the current 5.1 nightly build jobs are to be used again, maybe we can enable it now to see what we are missing? Assuming there is enough build capacity available. Nick On Tue, 7 Apr 2020 at 16:16, Adam Wolf wrote: > > Hi folks! > > My KiCad time has been dramatically reduced for the past month due to > schools closing for COVID-19. > > I hope to have the OCC switchover complete this week--there were some > fixup_bundle snags again. (I swear this whole fiasco ends with me > joining the CMake macOS team...) After the OCC switchover, I need to > debug something weird with the 5.1.5 package, so we're ready for > 5.1.6. At that point, I have one thing to clear up from a project > management (not technical) perspective re the notarization and that > should be able to be setup on our nightlies and releases. > > Thanks for your patience as I continue to improve the macOS package :) > I appreciate bug reports and ideas and PRs but I'm currently only > able to make time to process my KiCad backlog maybe once or twice a > week. > > Adam Wolf > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] availability
[1]: https://gitlab.com/kicad/code/kicad/-/issues/4169 On 4/7/20 10:57 AM, Wayne Stambaugh wrote: > Adam, > > No problem. A new macOS crash bug[1] just reared it's ugly head so we > will have get this fixed before we freeze for 5.1.6 so you have some > time to get the OCC switchover completed. Thanks for working on this > and stay safe. > > Cheers, > > Wayne > > On 4/7/20 10:16 AM, Adam Wolf wrote: >> Hi folks! >> >> My KiCad time has been dramatically reduced for the past month due to >> schools closing for COVID-19. >> >> I hope to have the OCC switchover complete this week--there were some >> fixup_bundle snags again. (I swear this whole fiasco ends with me >> joining the CMake macOS team...) After the OCC switchover, I need to >> debug something weird with the 5.1.5 package, so we're ready for >> 5.1.6. At that point, I have one thing to clear up from a project >> management (not technical) perspective re the notarization and that >> should be able to be setup on our nightlies and releases. >> >> Thanks for your patience as I continue to improve the macOS package :) >> I appreciate bug reports and ideas and PRs but I'm currently only >> able to make time to process my KiCad backlog maybe once or twice a >> week. >> >> Adam Wolf >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] availability
Adam, No problem. A new macOS crash bug[1] just reared it's ugly head so we will have get this fixed before we freeze for 5.1.6 so you have some time to get the OCC switchover completed. Thanks for working on this and stay safe. Cheers, Wayne On 4/7/20 10:16 AM, Adam Wolf wrote: > Hi folks! > > My KiCad time has been dramatically reduced for the past month due to > schools closing for COVID-19. > > I hope to have the OCC switchover complete this week--there were some > fixup_bundle snags again. (I swear this whole fiasco ends with me > joining the CMake macOS team...) After the OCC switchover, I need to > debug something weird with the 5.1.5 package, so we're ready for > 5.1.6. At that point, I have one thing to clear up from a project > management (not technical) perspective re the notarization and that > should be able to be setup on our nightlies and releases. > > Thanks for your patience as I continue to improve the macOS package :) > I appreciate bug reports and ideas and PRs but I'm currently only > able to make time to process my KiCad backlog maybe once or twice a > week. > > Adam Wolf > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] availability
Thank you very much for the effort! On Tue, 7 Apr 2020 at 16:16, Adam Wolf wrote: > > Hi folks! > > My KiCad time has been dramatically reduced for the past month due to > schools closing for COVID-19. > > I hope to have the OCC switchover complete this week--there were some > fixup_bundle snags again. (I swear this whole fiasco ends with me > joining the CMake macOS team...) After the OCC switchover, I need to > debug something weird with the 5.1.5 package, so we're ready for > 5.1.6. At that point, I have one thing to clear up from a project > management (not technical) perspective re the notarization and that > should be able to be setup on our nightlies and releases. > > Thanks for your patience as I continue to improve the macOS package :) > I appreciate bug reports and ideas and PRs but I'm currently only > able to make time to process my KiCad backlog maybe once or twice a > week. > > Adam Wolf > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Availability of the KiCad coding style policy
2015-01-06 14:48 GMT+01:00 Wayne Stambaugh stambau...@gmail.com: On 1/5/2015 7:28 PM, Adam Wolf wrote: I think that is a good idea. Is our coding standard checker script still working well? I haven't used uncrustify in a while so I'm not sure. The last time I did use it, it seemed to handle everything OK except the _() macros which for some reason the strings got moved to a new line which made for some less than desirable formatting. They are easy enough to fix by hand. Adam Wolf On Mon, Jan 5, 2015 at 5:23 PM, Nick Østergaard oe.n...@gmail.com mailto:oe.n...@gmail.com wrote: Hi Wayne I was just looking at the coding style policy in Documentation/coding_style_policy.pdf and think the format (pdf) is not that great for linking and sharing to newcomers. I agree with your logic but the reason it was done this way was to prevent unsolicited changes and maintain control of the coding policy. I am not opposed to converting the policy to markdown and adding it to the doxygen-docs as long as everyone understands that under _no_ circumstances is the coding policy to be modified without the consent of the development team and approval of the lead developers. I believe I have the latest odt version of the coding policy which can be converted to markdown using odt2sphinx and then using sphinx to convert the rst file to markdown. I'm not sure Doxygen's markdown support is complete so I don't know how much manual work would be required. Would it be a good idea to convert it to md for the use in the doxygen-docs along side the roadmap and stable realease policy? I would expect that all the formatting in the document can be converted to md such that it is rendered properly by doxygen. If you are interested in converting this, please let me know and I will send you the latest odt file. I am willing to do this, although I am pretty busy the rest of the week so don't expect any blazing fast conversion. Thanks, Wayne The bonus is that if you have the doxygen-docs, you will also have the coding style policy at hand. Regards Nick Østergaard ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto:kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Availability of the KiCad coding style policy
On 1/5/2015 7:28 PM, Adam Wolf wrote: I think that is a good idea. Is our coding standard checker script still working well? I haven't used uncrustify in a while so I'm not sure. The last time I did use it, it seemed to handle everything OK except the _() macros which for some reason the strings got moved to a new line which made for some less than desirable formatting. They are easy enough to fix by hand. Adam Wolf On Mon, Jan 5, 2015 at 5:23 PM, Nick Østergaard oe.n...@gmail.com mailto:oe.n...@gmail.com wrote: Hi Wayne I was just looking at the coding style policy in Documentation/coding_style_policy.pdf and think the format (pdf) is not that great for linking and sharing to newcomers. I agree with your logic but the reason it was done this way was to prevent unsolicited changes and maintain control of the coding policy. I am not opposed to converting the policy to markdown and adding it to the doxygen-docs as long as everyone understands that under _no_ circumstances is the coding policy to be modified without the consent of the development team and approval of the lead developers. I believe I have the latest odt version of the coding policy which can be converted to markdown using odt2sphinx and then using sphinx to convert the rst file to markdown. I'm not sure Doxygen's markdown support is complete so I don't know how much manual work would be required. Would it be a good idea to convert it to md for the use in the doxygen-docs along side the roadmap and stable realease policy? I would expect that all the formatting in the document can be converted to md such that it is rendered properly by doxygen. If you are interested in converting this, please let me know and I will send you the latest odt file. Thanks, Wayne The bonus is that if you have the doxygen-docs, you will also have the coding style policy at hand. Regards Nick Østergaard ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto:kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Availability of the KiCad coding style policy
I think the uncrustify script is working well. I tested it on the pcbnew/eagle_plugin.cpp which I am going to make a patch for, but it did change a lot, like making multiline comments to have asterisks in each line. So will it be better to submit a patch for the functional changes, such that they are easier to review, or should I make the changes and uncrustify it? 2015-01-06 1:28 GMT+01:00 Adam Wolf adamw...@feelslikeburning.com: I think that is a good idea. Is our coding standard checker script still working well? Adam Wolf On Mon, Jan 5, 2015 at 5:23 PM, Nick Østergaard oe.n...@gmail.com wrote: Hi Wayne I was just looking at the coding style policy in Documentation/coding_style_policy.pdf and think the format (pdf) is not that great for linking and sharing to newcomers. Would it be a good idea to convert it to md for the use in the doxygen-docs along side the roadmap and stable realease policy? I would expect that all the formatting in the document can be converted to md such that it is rendered properly by doxygen. The bonus is that if you have the doxygen-docs, you will also have the coding style policy at hand. Regards Nick Østergaard ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Availability of the KiCad coding style policy
I think that is a good idea. Is our coding standard checker script still working well? Adam Wolf On Mon, Jan 5, 2015 at 5:23 PM, Nick Østergaard oe.n...@gmail.com wrote: Hi Wayne I was just looking at the coding style policy in Documentation/coding_style_policy.pdf and think the format (pdf) is not that great for linking and sharing to newcomers. Would it be a good idea to convert it to md for the use in the doxygen-docs along side the roadmap and stable realease policy? I would expect that all the formatting in the document can be converted to md such that it is rendered properly by doxygen. The bonus is that if you have the doxygen-docs, you will also have the coding style policy at hand. Regards Nick Østergaard ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
