Release process #115
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#115
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
There are many points we may want to discuss for Garage.
_release/
on Garage's bucket.Feel free to add your ideas and remarks
I'm against making repositories for Debian and Fedora. We don't want to care about distribution specifics, especially if we are already giving out a statically linked binary that works everywhere.
Let's have these two methods of release: docker image for people who use docker, statically linked binary for people who don't use docker.
Having many targets (x86_64, armv7, arm, i686, etc) is good. I don't know if there are any issues specific to 32-bit platforms, do we know of any?
Supporting macOS and Windows isn't a priority.
Let's automate the build using Drone, not on each commit but under certain conditions (see below)
We can have the following schedule for building and publishing a release:
Closing for now as we have answered many questions asked here.