LBRYCommunity/lbry.tech
1
0
Fork 0
Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

change releases to build

Browse source
This commit is contained in:
Niko Storni 2018-09-19 09:23:52 -04:00
parent bcef25efbe
commit 9d9184b33a
No known key found for this signature in database
GPG key ID: F37FE63398800368
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
documents/contribute.md
View file

@ -85,7 +85,7 @@ A number of our code bases (`lbrycrd`, `lbry`, all applications, more...) go thr
For any projects that you want to be a tester on, "Watch" the repo on GitHub. You will receive an email with release notes whenever a release candidate is out. For any projects that you want to be a tester on, "Watch" the repo on GitHub. You will receive an email with release notes whenever a release candidate is out.
For even harder-core testing, you can follow the `README` instructions in a project and test against the `master` branch of a project at any time. Additionally, `master` builds for some projects are always available via [releases.lbry.io](http://releases.lbry.io). For even harder-core testing, you can follow the `README` instructions in a project and test against the `master` branch of a project at any time. Additionally, `master` builds for some projects are always available via [build.lbry.io](http://build.lbry.io).
Opening well-specified issues against release candidates or master builds is extremely useful in helping us create quality software. Opening well-specified issues against release candidates or master builds is extremely useful in helping us create quality software.