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

Adding a "Warning" label #1575

Closed
sunjam opened this issue Sep 26, 2022 · 6 comments
Closed

Adding a "Warning" label #1575

sunjam opened this issue Sep 26, 2022 · 6 comments

Comments

@sunjam
Copy link

sunjam commented Sep 26, 2022

Description
Adding a Warning label (Github version of tags) for issues known to cause breaking changes in NextcloudPi, so we can offer a perma-link which directs to those known issues an admin should be aware of if curious on potential issues with the updater, etc.

Thanks either way for considering.
Related issues #1574 #1570 etc.

@theCalcaholic
Copy link
Collaborator

theCalcaholic commented Sep 26, 2022

I like that idea! Let's maybe call it "disruption" or "impairment" something like that

@REAPERSbattlecry
Copy link

I'm not sure if everyone is reading the github/forum posts before upgrading. As far as I can see most of the users are running their ncp-instance on autoupdate (many devices are still on buster).

Is it possible or maybe possible in advance to your idea to choose in the webUI between stable and testing update. And in testing the devel-branch gets used permanently.
Maybe we find more people to do testing on different instances.

But despite all my critics I like that idea as well.

@theCalcaholic
Copy link
Collaborator

theCalcaholic commented Sep 26, 2022

@REAPERSbattlecry This would not be a tool for users who want to update, but for people who answer community questions, like in the forums.
Makes it easier for me to communicate with people like @sunjam or @ZendaiOwl

Regarding the idea to offer a "testing" branch in the web UI, I have to think about that. It's not exactly trivial to implement with the current update mechanism

@REAPERSbattlecry
Copy link

Ohh okay. Thanks for clarification.
Now I understand the idea and I like it.

@theCalcaholic
Copy link
Collaborator

I have created the label: disruption Issues actively causing problems with existing installations

@victor-rays
Copy link
Collaborator

That's perfect 🥳

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

No branches or pull requests

4 participants