Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RC candidates _should not_ be the default download #70

Open
jbenet opened this issue Jul 29, 2016 · 2 comments
Open

RC candidates _should not_ be the default download #70

jbenet opened this issue Jul 29, 2016 · 2 comments
Labels
dif/easy Someone with a little familiarity can pick up effort/hours Estimated to take one or several hours help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P0 Critical: Tackled by core team ASAP status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work

Comments

@jbenet
Copy link
Member

jbenet commented Jul 29, 2016

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.

@ghost
Copy link

ghost commented Jul 29, 2016

Agreed

  • the dist page should be maybe be able to show mutliple releases per project -- here's the "stable" release, and here's the "testing" release
  • these should be explicitly settable, instead of picking the latest as per semver

@Kubuxu
Copy link
Member

Kubuxu commented Jul 29, 2016

Latest full release could be used for stable and latest total for testing.

@jessicaschilling jessicaschilling added dif/easy Someone with a little familiarity can pick up effort/hours Estimated to take one or several hours help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P0 Critical: Tackled by core team ASAP status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work labels Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/easy Someone with a little familiarity can pick up effort/hours Estimated to take one or several hours help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P0 Critical: Tackled by core team ASAP status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work
Projects
None yet
Development

No branches or pull requests

3 participants