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

[charm-dev] bump versions #57

Merged
merged 2 commits into from
Nov 7, 2024
Merged

Conversation

sed-i
Copy link
Collaborator

@sed-i sed-i commented Jul 19, 2024

In this PR, bumping:

  • ubuntu from 22.04 to 24.04
  • MicroK8s 1.29 to 1.30
  • Add a motd message encouraging users to use beta channels to help the charming community.

@sed-i sed-i marked this pull request as ready for review July 19, 2024 04:07
Copy link
Collaborator

@ricab ricab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sed-i, thanks for the PR. We need to wait for a little while after releasing 1.14 — which we were about to release when we found a couple of regressions — to give people a chance to update Multipass and be able to get the 24.04 alias (that should be more dynamic, but we haven't had a chance yet).

In the meantime, I am not entirely convinced by the "beta" thing. The way I understand it, this blueprint is meant for development of charms, not Juju itself; after all, dev is qualified by charm- in the name. And the description is "A development and testing environment for charmers".

I guess this is another thing that would benefit from parameterization. Until then, how difficult is it to snap refresh after the launch?

@sed-i
Copy link
Collaborator Author

sed-i commented Jul 30, 2024

Agreed @ricab, wrote this down in a motd instead.

@ricab
Copy link
Collaborator

ricab commented Jul 31, 2024

Nice, I like that MOTD idea. Let's give it a couple of weeks or so and then we'll update.

Copy link
Collaborator

@ricab ricab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @sed-i, question inline

echo " encounter in you journey!"
echo
echo " sudo snap refresh juju --channel=3/beta"
echo " sudo snap refresh charmcraft --classic --channel=3.x/beta"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this channel is currently closed. Can you confirm if this really is the intention?

$ sudo snap refresh charmcraft --classic --channel=3.x/beta
charmcraft (3.x/candidate) 3.1.1 from Canonical✓ refreshed
Channel 3.x/beta for charmcraft is closed; temporarily forwarding to 3.x/candidate.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh. I think it worked yesterday (?), not sure.
Yes, I'll change to candidate.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok odd, snap info looks fine. Let's keep at beta?

  3.x/stable:       –                                           
  3.x/candidate:    3.1.1                2024-07-24 (4264) 62MB classic
  3.x/beta:         ↑                                           
  3.x/edge:         3.1.1.post4+g1330582 2024-07-31 (4318) 62MB classic

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, that's what it looks like when the channel is closed, it just forwards to the next "more stable" channel. And that worked fine. If something is later published to beta, the snap will update to that.

Anyway, I am fine with beta. I mainly wanted to be sure that you didn't mean to have candidate or edge instead.

Copy link
Collaborator

@ricab ricab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @sed-i, worked like a charm 🥁

Copy link
Collaborator

@ricab ricab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright, let's get this in finally. Thank you @sed-i!

@ricab ricab merged commit e540fec into canonical:main Nov 7, 2024
3 checks passed
@sed-i sed-i deleted the feature/bump-charm-dev branch December 1, 2024 04:43
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

Successfully merging this pull request may close these issues.

2 participants