Improve compilation time on Windows

+ few fixes for release

Author: karllessard

.github/workflows/ci.yml

@@ -123,9 +123,9 @@ jobs:
     if: github.event_name == 'push' || contains(github.event.pull_request.labels.*.name, 'CI build')
     runs-on: windows-latest
     needs: prepare
-    #    strategy:
-    #      matrix:
-    #        ext: ["", -mkl, -gpu, -mkl-gpu]
+    strategy:
+       matrix:
+         ext: ["", -mkl, -gpu, -mkl-gpu]
     steps:
       - name: Configure page file
         uses: al-cheb/[email protected]

README.md

@@ -85,12 +85,12 @@ systems, you should add the following dependencies:
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-api</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
 </dependency>
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-api</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
   <classifier>linux-x86_64${javacpp.platform.extension}</classifier>
 </dependency>
 ```
@@ -101,24 +101,24 @@ native dependencies as follows:
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-api</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
 </dependency>
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-api</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
   <classifier>linux-x86_64${javacpp.platform.extension}</classifier>
 </dependency>
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-api</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
   <classifier>macosx-x86_64${javacpp.platform.extension}</classifier>
 </dependency>
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-api</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
   <classifier>windows-x86_64${javacpp.platform.extension}</classifier>
 </dependency>
 ```
@@ -131,7 +131,7 @@ artifact includes transitively all the artifacts above as a single dependency:
 <dependency>
   <groupId>org.tensorflow</groupId>
   <artifactId>tensorflow-core-platform${javacpp.platform.extension}</artifactId>
-  <version>0.2.0-SNAPSHOT</version>
+  <version>0.2.0</version>
 </dependency>
 ```
 
@@ -173,7 +173,8 @@ This table shows the mapping between different version of TensorFlow for Java an
 | TensorFlow Java Version  | TensorFlow Version |
 | ------------- | ------------- |
 | 0.1.0-SNAPSHOT  | 2.2.0  |
-| 0.2.0-SNAPSHOT  | 2.3.0  |
+| 0.2.0-SNAPSHOT  | 2.3.1  |
+| 0.2.0  | 2.3.1  |
 
 ## How to Contribute?
 

RELEASE.md

@@ -58,8 +58,13 @@ version number.
 3.  Update the version of the Maven artifacts to the full version of the release
     ```
     mvn versions:set -DnewVersion=1.0.0
-    ``` 
-4.  Commit the changes and push the new branch to the GitHub repository
+    ```
+4.  In the [README.md](https://github.com/tensorflow/java/blob/master/README.md) file,
+    update the ['Using Maven Artifacts'](https://github.com/tensorflow/java/blob/master/README.md#using-maven-artifacts)
+    section and the ['TensorFlow Version Support'](https://github.com/tensorflow/java/blob/master/README.md#tensorflow-version-support)
+    table to reflect the new version being released.
+
+5.  Commit the changes and push the new branch to the GitHub repository
     ```
     git add .
     git commit -m "Releasing 1.0.0"
@@ -83,8 +88,13 @@ version number.
 4.  Update the version of the Maven artifacts to the full version of the release
     ```
     mvn versions:set -DnewVersion=1.0.1
-    ``` 
-4.  Commit the changes and push the branch to the GitHub repository
+    ```
+5.  In the [README.md](https://github.com/tensorflow/java/blob/master/README.md) file,
+    update the ['Using Maven Artifacts'](https://github.com/tensorflow/java/blob/master/README.md#using-maven-artifacts)
+    section and the ['TensorFlow Version Support'](https://github.com/tensorflow/java/blob/master/README.md#tensorflow-version-support)
+    table to reflect the new version being released.
+
+6.  Commit the changes and push the branch to the GitHub repository
     ```
     git add .
     git commit -m "Releasing 1.0.1"
@@ -109,7 +119,7 @@ To do so, follow the same steps as the [CI build](https://github.com/tensorflow/
 for the same platform and make sure to checkout the release branch and to provide your Sonatype credentials
 for temporary staging.
 
-### Building and deploying all artifacts to Sonatype
+### Performing the release
 
 1.  At the root of your TensorFlow Java copy, create a Maven settings.xml file with your OSSRH credentials and
     your GPG key passphrase:
@@ -162,29 +172,53 @@ for temporary staging.
     of your release and click `Close` and `Release` to finalize the release. You always have the option
     to `Drop` it to abort and restart if something went wrong.
 
-4.  Some things of note:
+4.  Go to GitHub and create a release tag on the release branch with a summary of what the version includes.
+
+Some things of note:
     - For details, look at the [Sonatype guide](http://central.sonatype.org/pages/releasing-the-deployment.html).
     - Syncing with [Maven Central](http://repo1.maven.org/maven2/org/tensorflow/)
       can take 10 minutes to 2 hours (as per the [OSSRH
       guide](http://central.sonatype.org/pages/ossrh-guide.html#releasing-to-central)).
 
 ### Finishing a release
 
-Go to GitHub and create a release tag at the release branch with a summary of what the version includes.
-
 #### Major or minor release
 
-1. In your local copy, checkout the master branch and increase the next snapshot version.
+1. Checkout the master branch and merge back changes from the released branch
+   ```
+   git checkout master
+   git merge r1.0
+   ```
+2. In your local copy, checkout the master branch and increase the next snapshot version.
    ```
    mvn versions:set -DnewVersion=1.1.0-SNAPSHOT
    ```
-2. Commit your changes and push the master branch to the GitHub repository
+3.  In the [README.md](https://github.com/tensorflow/java/blob/master/README.md) file,
+    update the ['Using Maven Artifacts'](https://github.com/tensorflow/java/blob/master/README.md#using-maven-artifacts)
+    section and the ['TensorFlow Version Support'](https://github.com/tensorflow/java/blob/master/README.md#tensorflow-version-support)
+    table to reflect the new snapshot version.
+
+4. Commit your changes and push the master branch to the GitHub repository
    ```
    git add .
    git commit -m "Increase version for next iteration"
    git push
    ```
 
+#### Patch release
+
+1. Checkout the master branch and merge back changes from the released branch
+   ```
+   git checkout master
+   git merge r1.0
+   ```
+2. Commit the changes and push the master branch to the GitHub repository
+   ```
+   git add .
+   git commit -m "Merge release 1.0.1"
+   git push
+   ```
+
 ## References
 
 -   [Sonatype guide](http://central.sonatype.org/pages/ossrh-guide.html) for

tensorflow-core/tensorflow-core-api/.bazelrc

@@ -285,6 +285,10 @@ build:windows --verbose_failures
 # On windows, we never cross compile
 build:windows --distinct_host_configuration=false
 
+# Following option reduces considerably the compilation time on Windows with VS16.4+
+build:windows --copt=/d2ReducedOptimizeHugeFunctions
+build:windows --host_copt=/d2ReducedOptimizeHugeFunctions
+
 # Suppress all warning messages.
 build:short_logs --output_filter=DONT_MATCH_ANYTHING
 

tensorflow-core/tensorflow-core-platform-gpu/pom.xml

@@ -64,7 +64,7 @@
   -->
   <profiles>
     <profile>
-      <id>release</id>
+      <id>releasing</id>
       <dependencies>
         <dependency>
           <groupId>org.bytedeco</groupId>

tensorflow-core/tensorflow-core-platform-mkl-gpu/pom.xml

@@ -75,7 +75,7 @@
   -->
   <profiles>
     <profile>
-      <id>release</id>
+      <id>releasing</id>
       <dependencies>
         <dependency>
           <groupId>org.bytedeco</groupId>

tensorflow-core/tensorflow-core-platform-mkl/pom.xml

@@ -93,7 +93,7 @@
   -->
   <profiles>
     <profile>
-      <id>release</id>
+      <id>releasing</id>
       <dependencies>
         <dependency>
           <groupId>org.bytedeco</groupId>