Latest release should automatically build against latest appliance releases. #14
Labels
No labels
Accepted
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
In Review
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-docker#14
Loading…
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?
Any appliance that is containerized by this repository should be automatically built against the latest under an "edge" or "latest" tag as discussed within the LBRY team. Ideally, you want ALL users on the latest possible build to prevent looking like a security disaster. We are a cryptocurrency project of course security privacy and autonomy are all paramount.
edgemay come with no assertion of stabilitylatestmay come with no breaking changes offering potential case management for updating volume stored data upgrading to the latest releases.This may require active engagement from the leaders of the various projects that will be containerized here. @tzarebczan I'll likely need you to engage the people responsible as I don't know 100% who is in charge of each project I know some of them. I need to know if we can have some degree of control over release names etc so that we can build CI/CD for all of this.