Cleanup PIP package tools and installation documentation.
There are a few users to consider: 1. A developer on TFF wants source at HEAD. 2. A researcher using TFF wants pip package at release in 90% of scenarios and sometimes (ideally rarely) wants nightly, but never wants to build a pip package. 3. A developer making a framework using TFF wants pip release and nightly, but never wants to build a pip package. 4. A researcher upstreaming change to TFF basically has moved from #2 to #3. Fixes: #878 PiperOrigin-RevId: 321226038
Showing
- docs/install.md 34 additions, 85 deletionsdocs/install.md
- tensorflow_federated/tools/client/build_image.sh 3 additions, 1 deletiontensorflow_federated/tools/client/build_image.sh
- tensorflow_federated/tools/development/build_pip_package.sh 45 additions, 9 deletionstensorflow_federated/tools/development/build_pip_package.sh
- tensorflow_federated/tools/development/publish_pip_package.sh 30 additions, 2 deletions...orflow_federated/tools/development/publish_pip_package.sh
- tensorflow_federated/tools/development/setup.py 29 additions, 16 deletionstensorflow_federated/tools/development/setup.py
- tensorflow_federated/tools/development/test_pip_package.sh 28 additions, 4 deletionstensorflow_federated/tools/development/test_pip_package.sh
- tensorflow_federated/tools/runtime/container/build_image.sh 3 additions, 1 deletiontensorflow_federated/tools/runtime/container/build_image.sh
Loading
Please register or sign in to comment