-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outdated PCB design shown #416
Comments
Hey, sorry about this, it's an issue on our end. I will fix it as soon as I can. |
Does this look right? https://review.staging.kitspace.dev/OpenGammaProject/MicroFC-SiPM-Carrier-Board (Not really a public site, just our staging for kitspace-v2) |
Gerber and README look good, but the BOM is still the old one. |
Ok, thanks, now it's good? |
Yup, thanks! |
Hey, uh I'm not sure if this should be resolved by now (on kitspace.org), but I still see the old files. How often do you query the repos for files? Cause all the repos below also don't show the latest files: 😕 https://kitspace.org/boards/github.com/opengammaproject/mini-sid/ Are you trying to address this with kitspace-v2? If so, do you have an ETA on that? :) |
Hiya, yes it should all be solved by V2, please do check if all your projects look right here: https://review.staging.kitspace.dev/search?q=opengamma Unfortunately I'm not totally sure about an ETA on switching over, we are in that last 5% phase that always seems to take longer than expected, even when you try and expect it to take longer. I will try and find some time over the Christmas break to do it. |
Okay, well then I'll just wait for v2. Thanks for clarifying! |
Hi there,
Regarding my project:
The PCB currently shown on Kitspace is outdated unfortunately. As you can see in the files in the repo, the current release is 2.0, while Kitspace still has the 1.3 revision. Not sure if it's something with my Kitspace config or if this is an issue on your end. This looks to be a problem with the entire GitHub repo since not only the Gerber file and the BOM are wrong, but this also extends to the README as well.
The text was updated successfully, but these errors were encountered: