ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-01-18 02:40:07 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

stronger language for adding contributors & make commands stand out

Browse Source 
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
This commit is contained in:
fenn-cs 2021-11-18 11:46:01 +01:00
parent 882f197306
commit 92e8d78a3d
2 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.rst
View File

@ -95,12 +95,13 @@ As a community-driven open source project, Tahoe-LAFS welcomes contributions of
- `Patch reviews <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/PatchReviewProcess>`__
Before authoring or reviewing a patch, please familiarize yourself with the `Coding Standard <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CodingStandards>`__ and the `Contributor Code of Conduct <docs/CODE_OF_CONDUCT.md>`__.
Before authoring or reviewing a patch, please familiarize yourself with the `Coding Standard <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CodingStandards>`__ and the `Contributor Code of Conduct <docs/CODE_OF_CONDUCT.md>`__.
🥳 First Contribution?
----------------------
If you are committing to Tahoe for the very first time, consider adding your name to our contributor list in `CREDITS <CREDITS>`__
If you are committing to Tahoe for the very first time, it's required that you add your name to our contributor list in `CREDITS <CREDITS>`__. Please ensure that this addition has it's own commit within your first contribution.
🤝 Supporters

18
docs/release-checklist.rst
View File

@ -17,7 +17,7 @@ This checklist is based on the original instructions (in old revisions in the fi
Any Contributor
```````````````
---------------
Anyone who can create normal PRs should be able to complete this
portion of the release process.
@ -50,7 +50,11 @@ previously generated files.
practice to give it the release name. You MAY also discard this directory once the release
process is complete.*
- ``cd`` into the release directory and install dependencies by running ``python -m venv venv && source venv/bin/activate && pip install --editable .[test]``
Get into the release directory and install dependencies by running
- ``cd ../tahoe-release-x.x.x`` (assuming you are still in your original clone)
- ``python -m venv venv``
- ``./venv/bin/pip install --editable .[test]``
Create Branch and Apply Updates
@ -137,16 +141,18 @@ they will need to evaluate which contributors' signatures they trust.
- build all code locally
- these should all pass:
- tox -e py27,codechecks,docs,integration
- ``tox -e py27,codechecks,docs,integration``
- these can fail (ideally they should not of course):
- tox -e deprecations,upcoming-deprecations
- ``tox -e deprecations,upcoming-deprecations``
- build tarballs
- tox -e tarballs
- Confirm that release tarballs exist by runnig: ``ls dist/ | grep 1.16.0rc0``
- Confirm that release tarballs exist by runnig:
- ``ls dist/ | grep 1.16.0rc0``
- inspect and test the tarballs
@ -160,7 +166,7 @@ they will need to evaluate which contributors' signatures they trust.
Privileged Contributor
``````````````````````
-----------------------
Steps in this portion require special access to keys or
infrastructure. For example, **access to tahoe-lafs.org** to upload