ipfs/distributions

RC candidates _should not_ be the default download

Open

#70 opened on Jul 29, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Less (31 forks)auto 404
P0dif/easyeffort/hourshelp wantedkind/bugstatus/readytopic/design-front-end

Repository metrics

Stars
 (49 stars)
PR merge metrics
 (PR metrics pending)

Description

Looks like go-ipfs @ 0.4.3-rc1 is the default download at https://dist.ipfs.io/ right now. This is not great, because RCs could have serious issues and vulnerabilities.

In this case, 0.4.3-rc1 is thought to be much better than 0.4.2, but i'm not sure this merits skipping the release process... this is the sort of thing that can make small problems big.

Contributor guide

Research direction
Locate the configuration that determines the default download link on dist.ipfs.io and update it to always point to the latest stable release, ensuring release candidates are not set as default.
Tech stack
None
Domain
release
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70