ipfs/kubo

Signed releases

Open

#957 opened on Mar 22, 2015

View on GitHub
 (20 comments) (2 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/enhancementtopic/release

Description

Once Go 1.5 lands we can compile all archs in one place. We can then do signed releases. It would be ideal to deploy these releases using ipfs itself, using the gateways.

Contributor guide

Tech stack
go
Domain
releasedevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Go programmingIPFSRelease engineeringCryptographic signing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the current state of Go cross compilation for ipfs/kubo. Check if there are existing release scripts or CI configuration in the repository. Look for any linked issues or discussions about signing in the comments. Consider proposing a design for signed releases using Go's standard tooling and IPFS gateways.