Skip to content
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

New Release #274

Open
jmwright opened this issue Jul 2, 2021 · 7 comments
Open

New Release #274

jmwright opened this issue Jul 2, 2021 · 7 comments

Comments

@jmwright
Copy link
Member

jmwright commented Jul 2, 2021

Can we do a 0.2.1 release of CQ-editor? I've got pre-built packages on my fork with the latest version that I and other users are having good luck with. I would be happy to draft a new release and attach the archives to it so that it's easier for users to find and download.

@adam-urbanczyk
Copy link
Member

The release of CQ-editor is related to the release of CQ

@jmwright
Copy link
Member Author

jmwright commented Jul 2, 2021

Then can we do like I have with cq-cli and do a 0.2.1-beta.1 release?

@adam-urbanczyk
Copy link
Member

I don't think that this is sustainable - tomorrow there will be someone with yet another issue that is not present in master.

Do you know where we could upload nightly builds from your pyinstaller pipeline - if possible that would be IMO much better?

@jmwright
Copy link
Member Author

jmwright commented Jul 2, 2021

I have the schedule set to build weekly right now, but I can do nightly if that will help. I'm not sure if GitHub changed something or not, but I thought that the builds on my fork were only visible if you were logged into GitHub. It appears that's not the case though as I can see these from a browser where I'm not logged into GitHub. These are still mentioned in the CQ-editor readme. https://github.com/jmwright/CQ-editor/actions/workflows/pyinstaller-builds-actions.yml

@narvalotech
Copy link

The release of CQ-editor is related to the release of CQ

Can what @jmwright said be implemented? ie have a latest/unstable/nightly release version automatically updated by the CI builds? Because every time this is mentioned, the instructions are to navigate the CI pipeline page to find and download the artifacts. IMO that's just adding unnecessary friction, most users will expect the docs page to be aligned with the latest release.

I'm using a version installed from the AUR and it grabs the latest GH release, but that version is out of date with the docs, just found out now when it refused to add a .sketch() to my workplane.

If it's a problem of time, I can help out.

@adam-urbanczyk
Copy link
Member

adam-urbanczyk commented Jul 22, 2023

Are you looking for this: https://github.com/CadQuery/CQ-editor/releases/tag/nightly ?

It is mentioned in the README: https://github.com/CadQuery/CQ-editor#development-packages , is the phrasing not clear or was it simply missed?

@narvalotech
Copy link

Ah yeah I feel dumb now 😅

I still think it's not clear enough though, maybe making that tag more visible somewhere in the docs or on the readme:

could be in the documentation directly for features that are not supported on the stable release (ie Sketch) or there could be in the readme of cq-editor a section on the features that are missing from the stable release.

It seems the problem is that the stable cq-editor releases are tied to cq itself, right? Is there a particular reason that a stable cq release hasnt been cut?
I'm running a nightly package (from the ci artifacts) on my other laptop (Ubuntu) and it doesnt seem particularly unstable.

In any case, Im really happy about both cq and its editor that you made!
Just want to make the install smoother, thats all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants