- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for maintenant (0.18 sec)
-
CONTRIBUTING.md
* Include unit tests when you contribute new features, as they help to a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost. * Bug fixes also generally require unit tests, because the presence of bugs usually indicates insufficient test coverage. * Keep API compatibility in mind when you change code in core TensorFlow,
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0) -
ci/official/README.md
# generated artifacts like .whl files, and "script.log", from the script. # Note that files created under Docker will be owned by "root". ls build_output ``` ## Contribution & Maintenance The TensorFlow team does not yet have guidelines in place for contributing to this directory. We are working on it. Please join a TF SIG Build meeting (see:
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0) -
RELEASE.md
### Bug Fixes and Other Changes * The use of the ambe config to build and test aarch64 is not needed. The ambe config will be removed in the future. Making cpu_arm64_pip.sh and cpu_arm64_nonpip.sh more similar for easier future maintenance. # Release 2.12.0 ### Breaking Changes * Build, Compilation and Packaging
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Mon Apr 29 19:17:57 GMT 2024 - 727.7K bytes - Viewed (8)