About the releases
RubenRubens opened this issue · comments
Master release [Artifacts]
I believe it's a good idea to make releases based on schedules and not so much on functionality. Therefore, I suggest making a release every Monday that could be found at the artifacts.
Stable release [Releases]
There can be packages updated manually once there is a new CQ stable version. So in a few weeks I would suggest making a release called cq-cli 2.1.
CQ-editor binaries can follow a similar structure.
I'm not understanding why we would do a master release (artifacts) even when nothing has changed on master.
The code of this repo might not change but the code from cadquery does.
In the build process the latest cq version provided on conda is used. Let's pretend a bug is fixed on cadquery. If this repo is not updated very frequently users are going to use an old cq version.
This is only a suggestion.
@RubenRubens Ok, I see what you're thinking now. It might be a waste during times when CadQuery development is slow, but it makes sure to catch changes when things are moving fast. And these days CadQuery shows no signs of slowing down.
@RubenRubens The weekly build failed for Windows because it was trying to pull OCP 7.5-beta. I have pinned the version to 7.4 for now so that those builds should succeed, starting next week. I left the failed scheduled build in place for reference, but will probably delete it after the next successful weekly build.