Re: [Kicad-developers] 5.0 RC2 / release status
Great work Rene! Last call for any changes before I tag RC2. I wait another hour or two but I'm going to tag rc2 before I call it a night unless there is something critical that needs to get committed. On 05/20/2018 10:24 AM, Rene Pöschl wrote: > Hi all, > > as promised in my last response the library repos are now tagged with > 5.0.0-rc2 > If there is another major delay we might need to introduce a rc2.1 tag > or something (or accept that at that time the libs are a bit older) > > On 18/05/18 23:45, Wayne Stambaugh wrote: >> Hi Rene, >> >> On 05/18/2018 11:53 AM, Rene Pöschl wrote: >>> On 18/05/18 16:44, Wayne Stambaugh wrote: If any of our doc and library devs are on this mailing list, please forward this information so we aren't making major changes to the docs and libraries at the last minute. >>> We have one important pull request open that i will fix up my self >>> tomorrow if the contributor does not fix the remaining issues him self. >>> (Removing duplicate power pins from symbols as this can be quite >>> dangerous if the user connects them multiple times.) >>> >>> After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow >>> evening) >>> >>> After this tag is set we will no longer allow renaming of libs until v6 >>> development. (Adding new libs will still be allowed.) >> I'm OK with this. >> >>> I will also create a kicad 4 compatibility backport for this lib. (The >>> intention is to allow users to use the new library structure for new >>> projects even if they can not update to a nightly build. This should >>> reduce their work when they then switch over to kicad 5) >>> >>> This backport will contain a reduced number of footprints as footprints >>> with custom or roundrect pads are not supported by kicad 4. I will also >>> backport the symbol libs. The 3d lib does not need any work in this >>> regard but i will still ad a separate release tag to make it easier for >>> users. Not sure if i will make a backport of the templates. >>> Creating this backport will take some time but i hope to have it done >>> one week after the rc2 tag is set. >> Awesome! I'm sure our v4 users will appreciate this. >> >>> >>> Regarding the issue about footprint connection you reported in [1]: >>> All symbols that have a valid symbol in the footprint lib are now >>> correctly connected. Sadly a lot of symbols still need footprints to be >>> generated. (Symbols where in the lib that never had a valid footprint) >>> Some of this will be fixed after the rc2 release. This will not impact >>> the library structure so i assume we can include these changes in the >>> final v5 release. (It will simply add more footprints.) >> That fine by me. If we are going add new symbol libraries during v5, I >> don't see any reason not to add new footprints and footprint libraries. >> We should try to avoid wholesale renaming and/or moving of libraries and >> their contents to avoid headaches for users. If we have any major >> library reorganizations, we can always create a v5 branch as we do for >> the KiCad source. >> >> Thank you for all of your hard work on the libraries. They really have >> come a long way since v4 was released. >> >> Cheers, >> >> Wayne >> >>> [1]: https://github.com/KiCad/kicad-symbols/issues/520 >>> >>> ___ >>> 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 ___ 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] 5.0 RC2 / release status
Hi all, as promised in my last response the library repos are now tagged with 5.0.0-rc2 If there is another major delay we might need to introduce a rc2.1 tag or something (or accept that at that time the libs are a bit older) On 18/05/18 23:45, Wayne Stambaugh wrote: Hi Rene, On 05/18/2018 11:53 AM, Rene Pöschl wrote: On 18/05/18 16:44, Wayne Stambaugh wrote: If any of our doc and library devs are on this mailing list, please forward this information so we aren't making major changes to the docs and libraries at the last minute. We have one important pull request open that i will fix up my self tomorrow if the contributor does not fix the remaining issues him self. (Removing duplicate power pins from symbols as this can be quite dangerous if the user connects them multiple times.) After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow evening) After this tag is set we will no longer allow renaming of libs until v6 development. (Adding new libs will still be allowed.) I'm OK with this. I will also create a kicad 4 compatibility backport for this lib. (The intention is to allow users to use the new library structure for new projects even if they can not update to a nightly build. This should reduce their work when they then switch over to kicad 5) This backport will contain a reduced number of footprints as footprints with custom or roundrect pads are not supported by kicad 4. I will also backport the symbol libs. The 3d lib does not need any work in this regard but i will still ad a separate release tag to make it easier for users. Not sure if i will make a backport of the templates. Creating this backport will take some time but i hope to have it done one week after the rc2 tag is set. Awesome! I'm sure our v4 users will appreciate this. Regarding the issue about footprint connection you reported in [1]: All symbols that have a valid symbol in the footprint lib are now correctly connected. Sadly a lot of symbols still need footprints to be generated. (Symbols where in the lib that never had a valid footprint) Some of this will be fixed after the rc2 release. This will not impact the library structure so i assume we can include these changes in the final v5 release. (It will simply add more footprints.) That fine by me. If we are going add new symbol libraries during v5, I don't see any reason not to add new footprints and footprint libraries. We should try to avoid wholesale renaming and/or moving of libraries and their contents to avoid headaches for users. If we have any major library reorganizations, we can always create a v5 branch as we do for the KiCad source. Thank you for all of your hard work on the libraries. They really have come a long way since v4 was released. Cheers, Wayne [1]: https://github.com/KiCad/kicad-symbols/issues/520 ___ 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] 5.0 RC2 / release status
A bug related to some recent changes is https://bugs.launchpad.net/kicad/+bug/1769143 It sounds simple, but I don't know if it is. 2018-05-19 9:24 GMT+02:00 Andrey Kuznetsov : > What about this bug for MacOS that makes it too frustrating to use > eeschema? > > Basically, I cannot navigate by zooming around in eeschema because the > mouse scroll triggers on fine steps of the scroll wheel instead of the > larger ratchet steps, it's not just that this is a granularity issue it's a > consistency of navigation issue because when the scroll wheel springs back > to the ratchet position of the original zoom, the actual zoom level is > different and I have to play with the scroll wheel until the zoom level > looks OK. Coupled with a HiDPI display which slows down Eeschema and GOOD > BYE KiCAD on MacOS, it's too frustrating. > > https://bugs.launchpad.net/kicad/+bug/1753054 > > On Fri, May 18, 2018 at 2:45 PM, Wayne Stambaugh > wrote: > >> Hi Rene, >> >> On 05/18/2018 11:53 AM, Rene Pöschl wrote: >> > On 18/05/18 16:44, Wayne Stambaugh wrote: >> >> If any of our doc and library devs are on this mailing list, please >> >> forward this information so we aren't making major changes to the docs >> >> and libraries at the last minute. >> >> >> > >> > We have one important pull request open that i will fix up my self >> > tomorrow if the contributor does not fix the remaining issues him self. >> > (Removing duplicate power pins from symbols as this can be quite >> > dangerous if the user connects them multiple times.) >> > >> > After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow >> > evening) >> > >> > After this tag is set we will no longer allow renaming of libs until v6 >> > development. (Adding new libs will still be allowed.) >> >> I'm OK with this. >> >> > >> > I will also create a kicad 4 compatibility backport for this lib. (The >> > intention is to allow users to use the new library structure for new >> > projects even if they can not update to a nightly build. This should >> > reduce their work when they then switch over to kicad 5) >> > >> > This backport will contain a reduced number of footprints as footprints >> > with custom or roundrect pads are not supported by kicad 4. I will also >> > backport the symbol libs. The 3d lib does not need any work in this >> > regard but i will still ad a separate release tag to make it easier for >> > users. Not sure if i will make a backport of the templates. >> > Creating this backport will take some time but i hope to have it done >> > one week after the rc2 tag is set. >> >> Awesome! I'm sure our v4 users will appreciate this. >> >> > >> > >> > Regarding the issue about footprint connection you reported in [1]: >> > All symbols that have a valid symbol in the footprint lib are now >> > correctly connected. Sadly a lot of symbols still need footprints to be >> > generated. (Symbols where in the lib that never had a valid footprint) >> > Some of this will be fixed after the rc2 release. This will not impact >> > the library structure so i assume we can include these changes in the >> > final v5 release. (It will simply add more footprints.) >> >> That fine by me. If we are going add new symbol libraries during v5, I >> don't see any reason not to add new footprints and footprint libraries. >> We should try to avoid wholesale renaming and/or moving of libraries and >> their contents to avoid headaches for users. If we have any major >> library reorganizations, we can always create a v5 branch as we do for >> the KiCad source. >> >> Thank you for all of your hard work on the libraries. They really have >> come a long way since v4 was released. >> >> Cheers, >> >> Wayne >> >> > >> > [1]: https://github.com/KiCad/kicad-symbols/issues/520 >> > >> > ___ >> > 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 >> > > > > -- > Remember The Past, Live The Present, Change The Future > Those who look only to the past or the present are certain to miss the > future [JFK] > > kandre...@gmail.com > Live Long and Prosper, > Andrey > > ___ > 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://launchp
Re: [Kicad-developers] 5.0 RC2 / release status
What about this bug for MacOS that makes it too frustrating to use eeschema? Basically, I cannot navigate by zooming around in eeschema because the mouse scroll triggers on fine steps of the scroll wheel instead of the larger ratchet steps, it's not just that this is a granularity issue it's a consistency of navigation issue because when the scroll wheel springs back to the ratchet position of the original zoom, the actual zoom level is different and I have to play with the scroll wheel until the zoom level looks OK. Coupled with a HiDPI display which slows down Eeschema and GOOD BYE KiCAD on MacOS, it's too frustrating. https://bugs.launchpad.net/kicad/+bug/1753054 On Fri, May 18, 2018 at 2:45 PM, Wayne Stambaugh wrote: > Hi Rene, > > On 05/18/2018 11:53 AM, Rene Pöschl wrote: > > On 18/05/18 16:44, Wayne Stambaugh wrote: > >> If any of our doc and library devs are on this mailing list, please > >> forward this information so we aren't making major changes to the docs > >> and libraries at the last minute. > >> > > > > We have one important pull request open that i will fix up my self > > tomorrow if the contributor does not fix the remaining issues him self. > > (Removing duplicate power pins from symbols as this can be quite > > dangerous if the user connects them multiple times.) > > > > After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow > > evening) > > > > After this tag is set we will no longer allow renaming of libs until v6 > > development. (Adding new libs will still be allowed.) > > I'm OK with this. > > > > > I will also create a kicad 4 compatibility backport for this lib. (The > > intention is to allow users to use the new library structure for new > > projects even if they can not update to a nightly build. This should > > reduce their work when they then switch over to kicad 5) > > > > This backport will contain a reduced number of footprints as footprints > > with custom or roundrect pads are not supported by kicad 4. I will also > > backport the symbol libs. The 3d lib does not need any work in this > > regard but i will still ad a separate release tag to make it easier for > > users. Not sure if i will make a backport of the templates. > > Creating this backport will take some time but i hope to have it done > > one week after the rc2 tag is set. > > Awesome! I'm sure our v4 users will appreciate this. > > > > > > > Regarding the issue about footprint connection you reported in [1]: > > All symbols that have a valid symbol in the footprint lib are now > > correctly connected. Sadly a lot of symbols still need footprints to be > > generated. (Symbols where in the lib that never had a valid footprint) > > Some of this will be fixed after the rc2 release. This will not impact > > the library structure so i assume we can include these changes in the > > final v5 release. (It will simply add more footprints.) > > That fine by me. If we are going add new symbol libraries during v5, I > don't see any reason not to add new footprints and footprint libraries. > We should try to avoid wholesale renaming and/or moving of libraries and > their contents to avoid headaches for users. If we have any major > library reorganizations, we can always create a v5 branch as we do for > the KiCad source. > > Thank you for all of your hard work on the libraries. They really have > come a long way since v4 was released. > > Cheers, > > Wayne > > > > > [1]: https://github.com/KiCad/kicad-symbols/issues/520 > > > > ___ > > 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 > -- Remember The Past, Live The Present, Change The Future Those who look only to the past or the present are certain to miss the future [JFK] kandre...@gmail.com Live Long and Prosper, Andrey ___ 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] 5.0 RC2 / release status
Hi Rene, On 05/18/2018 11:53 AM, Rene Pöschl wrote: > On 18/05/18 16:44, Wayne Stambaugh wrote: >> If any of our doc and library devs are on this mailing list, please >> forward this information so we aren't making major changes to the docs >> and libraries at the last minute. >> > > We have one important pull request open that i will fix up my self > tomorrow if the contributor does not fix the remaining issues him self. > (Removing duplicate power pins from symbols as this can be quite > dangerous if the user connects them multiple times.) > > After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow > evening) > > After this tag is set we will no longer allow renaming of libs until v6 > development. (Adding new libs will still be allowed.) I'm OK with this. > > I will also create a kicad 4 compatibility backport for this lib. (The > intention is to allow users to use the new library structure for new > projects even if they can not update to a nightly build. This should > reduce their work when they then switch over to kicad 5) > > This backport will contain a reduced number of footprints as footprints > with custom or roundrect pads are not supported by kicad 4. I will also > backport the symbol libs. The 3d lib does not need any work in this > regard but i will still ad a separate release tag to make it easier for > users. Not sure if i will make a backport of the templates. > Creating this backport will take some time but i hope to have it done > one week after the rc2 tag is set. Awesome! I'm sure our v4 users will appreciate this. > > > Regarding the issue about footprint connection you reported in [1]: > All symbols that have a valid symbol in the footprint lib are now > correctly connected. Sadly a lot of symbols still need footprints to be > generated. (Symbols where in the lib that never had a valid footprint) > Some of this will be fixed after the rc2 release. This will not impact > the library structure so i assume we can include these changes in the > final v5 release. (It will simply add more footprints.) That fine by me. If we are going add new symbol libraries during v5, I don't see any reason not to add new footprints and footprint libraries. We should try to avoid wholesale renaming and/or moving of libraries and their contents to avoid headaches for users. If we have any major library reorganizations, we can always create a v5 branch as we do for the KiCad source. Thank you for all of your hard work on the libraries. They really have come a long way since v4 was released. Cheers, Wayne > > [1]: https://github.com/KiCad/kicad-symbols/issues/520 > > ___ > 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] 5.0 RC2 / release status
On 18/05/18 16:44, Wayne Stambaugh wrote: If any of our doc and library devs are on this mailing list, please forward this information so we aren't making major changes to the docs and libraries at the last minute. We have one important pull request open that i will fix up my self tomorrow if the contributor does not fix the remaining issues him self. (Removing duplicate power pins from symbols as this can be quite dangerous if the user connects them multiple times.) After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow evening) After this tag is set we will no longer allow renaming of libs until v6 development. (Adding new libs will still be allowed.) I will also create a kicad 4 compatibility backport for this lib. (The intention is to allow users to use the new library structure for new projects even if they can not update to a nightly build. This should reduce their work when they then switch over to kicad 5) This backport will contain a reduced number of footprints as footprints with custom or roundrect pads are not supported by kicad 4. I will also backport the symbol libs. The 3d lib does not need any work in this regard but i will still ad a separate release tag to make it easier for users. Not sure if i will make a backport of the templates. Creating this backport will take some time but i hope to have it done one week after the rc2 tag is set. Regarding the issue about footprint connection you reported in [1]: All symbols that have a valid symbol in the footprint lib are now correctly connected. Sadly a lot of symbols still need footprints to be generated. (Symbols where in the lib that never had a valid footprint) Some of this will be fixed after the rc2 release. This will not impact the library structure so i assume we can include these changes in the final v5 release. (It will simply add more footprints.) [1]: https://github.com/KiCad/kicad-symbols/issues/520 ___ 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] 5.0 RC2 / release status
MacOS is not 100% ready to go, but the large technical hurdles appear to be past us. Today I am working on adding OCE, which is a bit of a pain, but the massive Python packaging rework is building solidly and ngspice was just added. If anyone is interested in helping with the macOS packaging, there are a good handful of issues in the github repository that just require someone who knows KiCad to download a dmg, install it, run KiCad, and check that something works, and maybe write a few sentences on how to verify that that feature works. https://github.com/wayneandlayne/kicad-mac-builder/issues Adam Wolf On Fri, May 18, 2018 at 9:44 AM, Wayne Stambaugh wrote: > Hey Jon, > > A really nasty bug[1] was putting rc2 on hold. The commit to fix it was > just made yesterday. I was just getting ready to make a last call so > hear goes. > > I plan on tagging rc2 on Sunday evening barring any more show stoppers. > I have one last bug to fix (template paths) which I should get done by > today or tomorrow. If anyone else has any bug fixes for rc2, please get > them committed by then. Once rc2 is tagged, the UI string freeze is > officially in place. No further UI string changes will be accepted > except for spelling errors until after v5 is released. The goal is to > give our translators time to finish up the translations for v5 release. > Hopefully this will take less than a month. > > Where do we stand on the package front? Is macos packaging ready to go? > The goal would be to have everything ready to go within a week or two > of tagging and branching v5. > > If any of our doc and library devs are on this mailing list, please > forward this information so we aren't making major changes to the docs > and libraries at the last minute. > > Thank you to everyone for all of your hard work. Your efforts are > greatly appreciated. > > Cheers, > > Wayne > > [1]: https://bugs.launchpad.net/kicad/+bug/1767826 > > On 5/18/2018 10:29 AM, Jon Evans wrote: >> Hi all, >> >> I've been mostly away from KiCad recently due to other things going on >> in life, but I have been trying to follow the mailing list at least. >> Seems like progress towards a RC2 release may have stalled, but it's not >> clear why. Meanwhile lots of small changes continue to go in to master >> (I don't think that's necessarily a bad thing but I wonder whether or >> not we know what the critical path is to RC2) >> >> Where do we stand / if someone like me has a few hours somewhere to push >> on something, what is the most valuable area to look at? >> >> -Jon >> >> >> ___ >> 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] 5.0 RC2 / release status
Hey Jon, A really nasty bug[1] was putting rc2 on hold. The commit to fix it was just made yesterday. I was just getting ready to make a last call so hear goes. I plan on tagging rc2 on Sunday evening barring any more show stoppers. I have one last bug to fix (template paths) which I should get done by today or tomorrow. If anyone else has any bug fixes for rc2, please get them committed by then. Once rc2 is tagged, the UI string freeze is officially in place. No further UI string changes will be accepted except for spelling errors until after v5 is released. The goal is to give our translators time to finish up the translations for v5 release. Hopefully this will take less than a month. Where do we stand on the package front? Is macos packaging ready to go? The goal would be to have everything ready to go within a week or two of tagging and branching v5. If any of our doc and library devs are on this mailing list, please forward this information so we aren't making major changes to the docs and libraries at the last minute. Thank you to everyone for all of your hard work. Your efforts are greatly appreciated. Cheers, Wayne [1]: https://bugs.launchpad.net/kicad/+bug/1767826 On 5/18/2018 10:29 AM, Jon Evans wrote: > Hi all, > > I've been mostly away from KiCad recently due to other things going on > in life, but I have been trying to follow the mailing list at least. > Seems like progress towards a RC2 release may have stalled, but it's not > clear why. Meanwhile lots of small changes continue to go in to master > (I don't think that's necessarily a bad thing but I wonder whether or > not we know what the critical path is to RC2) > > Where do we stand / if someone like me has a few hours somewhere to push > on something, what is the most valuable area to look at? > > -Jon > > > ___ > 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] 5.0 RC2 / release status
Hi Jon, Welcome back! There was one very serious issue [1] blocking RC2, but fortunately it was fixed yesterday. Looking at the to-do list for v5 [2], there are three minor issues and two more serious bugs that may need some extra data from the reporters. It would be great to have the former two bugs closed for the final release, but I suppose we are ok for RC2. At least it would get us some extra testing eyes. Regards, Orson 1. https://bugs.launchpad.net/kicad/+bug/1767826 2. https://launchpad.net/kicad/+milestone/5.0.0-rc2 On 05/18/2018 04:29 PM, Jon Evans wrote: > Hi all, > > I've been mostly away from KiCad recently due to other things going on in > life, but I have been trying to follow the mailing list at least. Seems > like progress towards a RC2 release may have stalled, but it's not clear > why. Meanwhile lots of small changes continue to go in to master (I don't > think that's necessarily a bad thing but I wonder whether or not we know > what the critical path is to RC2) > > Where do we stand / if someone like me has a few hours somewhere to push on > something, what is the most valuable area to look at? > > -Jon > > > > ___ > 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 > signature.asc Description: OpenPGP digital signature ___ 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
