Release 0.4.3

[gcheng]

Dev Estimate: 3
Test estimate: 5
PM estimate: 1

One part is after jsr review, the code need to be moved to public repo for release.

Acceptance Criteria:
Publish release 0.4.2

Java Release Process

1. Branch
   1. Dev - Create release branch. Issue Pull request from dev branch to release branch. After review, merge the pull request. Run release branch CI project.
2. Add Release Notes
   1. PM – issue pull request with the necessary changes in the pom.xml and ChangeLog.md.
3. Build the branch: Automatically on the CI server (http://azuresdkciag.cloudapp.net:8080/job/)
   1. QA: Validate all unit tests pass on CI server (except for 4 timeouts when running Media Service tests)
   2. QA: Validate all unit tests pass locally (except for 2 timeouts when running Media Service tests, and 3 encryption faiulres due to the IT guys updating my JVM)
   3. QA: Validate everything in branch is Policheck clean
   4. QA: Validate licences
   5. QA: Validate that new code is warning-free
4. Sign the JAR using code-sign
   1. PM - go to codesign-gtm.microsoft.com from an intranet connected computer
   2. PM - Follow the steps to submit the files for signing.
   3. PM - Notify the team members who need to approve of the release that they must do so.
   4. QA - Copy the Jar files from signing server to local machine before the Jar files are expired. Verify that the signatures for all three JARs (jar, javadoc.jar, sources.jar), jarsigner.exe -verify -certs, and verify output for each is: jar verified.
   5. QA: Unzip the *.sources.jar, and compare with the sources. (This is a little tricky, because the Java build process combines the generated code with product code.) Compare these ...\azure-sdk-for-java\microsoft-azure-api\target\generated-sources\xjc and ...\azure-sdk-for-java\microsoft-azure-api\src\main\java to <unzipped sources.jar folder>(compile the source code at Eclipse should generate 10+ java files)
   6. QA: Verify that the docs in the *.javadocs.jar *look" like Java docs, and that any any changed APIs appear in the as expected in the docs.
   7. QA: In the test project, go to the Java Build Path->Projects and remove the "microsoft-azure-api" project.
      1. Refresh the project to see that it no longer compiles.
      2. In the Java Build Path->Libraries, click "Add External JARs...", and add all the signed JARs.
      3. Run the tests, verify the same results as for the unsigned JARs.
   8. QA - Do a validation pass on SDK doc assets
5. Binary release.
   1. QA - Push the code to the public master on GitHub through a commit request.
   2. Dev - TAG the master branch with the release info .
   3. Dev - Push the update to the Maven Central Repository, please see team one note for details.
   4. PM - Email Martin Sawicki the signed JARs
   5. PM - Update download links
6. Source code release.
   1. QA Push code from public release to public master.
   2. QA Push code from public master to public dev.
   3. QA Push code from public dev to private dev.
7. Documentation release.
   1. UE - Validate link status for Java online docs
   2. QA - Validate new doc content is visible on the site.

[gcheng]

closed by mistake, public dev and all private branches hasn't been populated yet. reopen

[gcheng]

close.