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

[Epic] Introduce update mechanism #484

Open
4 tasks
gbraad opened this issue Aug 28, 2019 · 4 comments
Open
4 tasks

[Epic] Introduce update mechanism #484

gbraad opened this issue Aug 28, 2019 · 4 comments
Labels
kind/epic Large chunk of work points/7 priority/major status/pinned Prevents the stale bot from closing the issue
Milestone

Comments

@gbraad
Copy link
Contributor

gbraad commented Aug 28, 2019

@anjannath
Copy link
Member

I am going to work on the last task in the list:

  • interpret info from release.txt

anjannath added a commit to anjannath/crc that referenced this issue Sep 20, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 20, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 20, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 20, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 20, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 21, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 24, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 24, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 25, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 26, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 26, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 26, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 27, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 27, 2019
Ask the user if wants to continue using the current version or not
when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 27, 2019
warn the user when a new version is available on mirror.
anjannath added a commit to anjannath/crc that referenced this issue Sep 27, 2019
warn the user when a new version is available on mirror.
gbraad pushed a commit that referenced this issue Sep 27, 2019
warn the user when a new version is available on mirror.
@sspeiche sspeiche added this to the backlog milestone Dec 17, 2019
@stale
Copy link

stale bot commented Feb 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Feb 15, 2020
@stale stale bot closed this as completed Feb 29, 2020
@gbraad
Copy link
Contributor Author

gbraad commented Mar 2, 2020

Any progress and changes to this?

@gbraad gbraad reopened this Mar 2, 2020
@stale stale bot removed the status/stale Issue went stale; did not receive attention or no reply from the OP label Mar 2, 2020
@gbraad gbraad added the status/pinned Prevents the stale bot from closing the issue label Mar 2, 2020
@guillaumerose guillaumerose changed the title Introduce update mechanism [Epic] Introduce update mechanism Jun 21, 2021
@guillaumerose guillaumerose added kind/epic Large chunk of work and removed kind/enhancement New feature or request labels Jun 21, 2021
@gbraad
Copy link
Contributor Author

gbraad commented Jan 19, 2022

Ref: #1860
Ref: #2168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic Large chunk of work points/7 priority/major status/pinned Prevents the stale bot from closing the issue
Projects
Status: No status
Development

No branches or pull requests

4 participants