-
Notifications
You must be signed in to change notification settings - Fork 10
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
Prepare for 1.0 release #115
Comments
@furgo16 any interest in helping this along ? |
@luzpaz to the measure of my capabilities, sure. How can I help? |
Update: if I understand it correctly, this has not been done yet. Let me know when the change is ready for testing. Happy to help if I can. |
Also another task on this issue should probably be to update OCT to the same version that will be shipped with 1.0. |
I have synchronized stable with master, so the latest release candidate should match the build used for the weeklies. |
@chennes thank you.
Which looks good. The only thing that caught my eye is that the beta channel seems to have stopped updating at some point. If it's supposed to be automatically updated every week from the master branch, it the relese available there should be |
Just kickstarted promite-to-beta action. Let see if it updates correctly |
@chennes promote-to-beta is still pulling from master and not main.
|
Is it pulling the snap repo? It's still called "master" here. |
That seemed to work:
On a different note: is there really a need for the I don't have a strong opinion on this, I just feel it might reduce maintenance overhead (and potentially confusion, since |
I don't see any extra overheard, honestly. |
This is a catch-all meta-ticket for readying the Snap package for the upcoming 1.0 release
CC @chennes @adrianinsaval
The text was updated successfully, but these errors were encountered: