-
Notifications
You must be signed in to change notification settings - Fork 202
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
No documentation for 1.0.0 #524
Comments
We tagged the first rc of 1.0 last week, the actual release will likely come in a couple of weeks. API documentation for v0.3 is here https://www.tensorflow.org/jvm. We'll get it updated to 1.0 when that is released. |
Sort of relevant, do we think we will get a proper release for this version? depending on snapshot version is not great, as I also noticed that we got upgraded to 2.16.1. Thanks |
There will be tagged releases for 1.0 (depending on TF 2.16), as usual Windows was causing a bit of trouble but I think we've got that ironed out. New releases will follow TF Python releases much more closely once we've done 1.0 as the build process has been drastically simplified so we're much less reliant on Github Actions not complaining when building certain platforms. |
Thank you for the quick response! Do you have a tentative date for the tagged release? |
I expect there will be 1.0-rc next week, then we'll leave it a couple of weeks to see if there are any major issues, then tag 1.0. |
Please make sure that this is a documentation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:doc_template
System information
Documentation is not available. Your api for 2.15 is completely new and I can't use it without documentation. When is proper 1.0.0 release?? Is any documentation availble for snapshot?? I must finish my project asap and can't do it
We welcome contributions by users. Will you be able to update submit a PR (use the doc style guide) to fix the doc Issue?
The text was updated successfully, but these errors were encountered: