Closed rburema closed 1 year ago
Hi, thanks for notifying me, I will test my plugin against the prelease as soon as possible. Also, could you tell me where exactly I need to add my contact info and what information is needed in order to receive that notifications in the future? Is it a email in the plugin.json? Thanks and best regards!
Also, could you tell me where exactly I need to add my contact info and what information is needed in order to receive that notifications in the future? Is it a email in the plugin.json?
Sorry for the late response, we use the email given to us when registering in the community portal.
Okay, good to know. I just opened the community portal (until now I only have used the contributor portal) and had to give some more info, but not an email. Maybe my community account was now created from my Ultimaker account and it could now work. Do you have some way too look up, if the contact email is now accessible for the future? Thank you :)
Hm, then you might be right in that it's the field from the plugin instead. Here's what I see when I'm administrating the plugin portal, for your plugin (next to the envelope icon you'd expect an email address).
Just found the setting in the Ultimaker Contributor portal. Feeling stupid, that it took me so long to find it. If you're curious, I am attaching an image. Also just to be safe, could you check once again? Thank you :)
I can confirm your email is now also visible to us in the portal. Thanks!
Question: Hi! Cura dev here. You've not listed any contact information, which we use to inform plugin-contributors of upcoming Cura versions -- we're releasing 5.5 soon-ish (in fact, the beta is already out). None of the changes should be breaking with the 8.x.x SDK (minor upgrade from 8.4.0 to 8.5.0), but it might be a good idea to test your plugin(s) with the upcoming version anyway via the beta.
Additional information: It's ok to not have the contact information there if you don't want to, but we're probably not going to make the effort each time to submit an issue on github either.
The original mail follows: