Update applications #611
kiara
commented
Owner
- #159 #65 #614 Operators can set when to update their applications.
- #214 Operators are guided through new options on updates.
- #629 Updating deployment options automated.
<!-- Staying up to date with the newest versions is relevant not only for new features, but for security purposes as well. As such, -->
1. #159 #65 #614 Operators can set when to update their applications.
<!--
1. Hosting providers should be able to present operators with options on updating policy which may include
1. #159 updating #65 when #614 possible,
1. #? notifying the operator on (major/minor) updates,
1. or applying application-specific preferences.
-->
<!-- 1. #123 Application state should be backed up prior to updates, and -->
1. #214 Operators are guided through new options on updates.
1. #629 Updating deployment options automated.
kiara
added the type: key result
label
kiara
added a new dependency
#159 Hosting providers can update their operators' deployments
kiara
added a new dependency
#65 Automated dependency updates
kiara
added a new dependency
#123 enable back-ups of application
kiara
added a new dependency
#214 aid needed actions on schema update
kiara
added a new dependency
#289 key features improving user experience supported
kiara
added a new dependency
#614 catch up on nixpkgs updates
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#289 key features improving user experience supported
fediversity/fediversity
#65 Automated dependency updates
fediversity/fediversity
#123 enable back-ups of application
fediversity/fediversity
#159 Hosting providers can update their operators' deployments
fediversity/fediversity
#214 aid needed actions on schema update
fediversity/fediversity
#614 catch up on nixpkgs updates
fediversity/fediversity
Reference: fediversity/fediversity#611
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?