Gina Hoiska

where they had this funny security issue where some printers suddenly fetched the wrong stuff from the cloud and started printing in the middle of the night for models from strangers.

where they had this funny security issue where some printers suddenly fetched the wrong stuff from the cloud and started printing in the middle of the night for models from strangers.

Yeah. And stuff like this happens, then this is a big, big no for me. And also the part with all of what 3D printing is these days, what 3D printing has come to over the last 10 years, that was... done on the shoulder of open source.

Yeah. And stuff like this happens, then this is a big, big no for me. And also the part with all of what 3D printing is these days, what 3D printing has come to over the last 10 years, that was... done on the shoulder of open source.

And now all of these companies, it's not just Bamboo, it's a bunch of others as well, are just rolling in and trying to lock everything down and trying to lock everything in and creating their own little gardens. And it's just not the way that I want to see all of this happening. I'm a bit afraid that we will lose all of the open access that we have now if stuff continues like that.

And now all of these companies, it's not just Bamboo, it's a bunch of others as well, are just rolling in and trying to lock everything down and trying to lock everything in and creating their own little gardens. And it's just not the way that I want to see all of this happening. I'm a bit afraid that we will lose all of the open access that we have now if stuff continues like that.

So it should be obvious that it's pretty much impossible to test every possible printer, firmware, plug-in, operation system, starting state of software situations. So what I do before I actually roll out a full release is there goes a long, long phase of release candidates. And Octoprint has a release branch system built in. So if you feel fine with testing stuff that is not...

So it should be obvious that it's pretty much impossible to test every possible printer, firmware, plug-in, operation system, starting state of software situations. So what I do before I actually roll out a full release is there goes a long, long phase of release candidates. And Octoprint has a release branch system built in. So if you feel fine with testing stuff that is not...

necessarily fully stable yet then you can just switch over to another release branch and then you will get release candidates whenever I push those out and they actually get the same procedure that I do for every single release and I will go quickly over that later as well but

necessarily fully stable yet then you can just switch over to another release branch and then you will get release candidates whenever I push those out and they actually get the same procedure that I do for every single release and I will go quickly over that later as well but

The idea behind that is that if I have something like 1,000, 2,000 people out there testing a release candidate and putting it through several years of print duration over the course of the release candidate phase, then I can be pretty sure that a lot of these combinations that I would never be able to test has been tested. And

The idea behind that is that if I have something like 1,000, 2,000 people out there testing a release candidate and putting it through several years of print duration over the course of the release candidate phase, then I can be pretty sure that a lot of these combinations that I would never be able to test has been tested. And

Yeah, it usually takes something like three to four release candidates until no more bugs come in. And at that point, then I declare this stable. And of course, after I've pushed out a stable release, so the current stable version is 1.10. But we are now already at 1.10.1. So there are bug fix releases that I also push out.

Yeah, it usually takes something like three to four release candidates until no more bugs come in. And at that point, then I declare this stable. And of course, after I've pushed out a stable release, so the current stable version is 1.10. But we are now already at 1.10.1. So there are bug fix releases that I also push out.

Those do not go through a full release candidate phase again, but they only get bug fixes and maybe small minor improvements of existing functionality. They do not get new features. They do not get... big changes. They obviously also get security fixes, stuff like that. But I try to really limit what goes in there.

Those do not go through a full release candidate phase again, but they only get bug fixes and maybe small minor improvements of existing functionality. They do not get new features. They do not get... big changes. They obviously also get security fixes, stuff like that. But I try to really limit what goes in there.

And if it feels too risky, then it goes into the next stable release that will actually get the full release candidate phase again. And what I do for every single release is... So OctoPrint can basically run anywhere where you can run Python. But most people run it on a Raspberry Pi. So that is also what I concentrate on for testing.

And if it feels too risky, then it goes into the next stable release that will actually get the full release candidate phase again. And what I do for every single release is... So OctoPrint can basically run anywhere where you can run Python. But most people run it on a Raspberry Pi. So that is also what I concentrate on for testing.

And there is this dedicated image that someone else is maintaining, Guy Sheffer, for OctoPrint, which is called OctoPi. And a lot of people confuse the image with the software and the software with the image, which also causes a lot of complications in support. But

And there is this dedicated image that someone else is maintaining, Guy Sheffer, for OctoPrint, which is called OctoPi. And a lot of people confuse the image with the software and the software with the image, which also causes a lot of complications in support. But