-
Notifications
You must be signed in to change notification settings - Fork 859
Release Procedure
-
Prepare a release message
-
Commit the change to hard-wired version numbers:
- README.md
- docs/docker.md
- docs/R-setup.md
- docs/gpu-setup.md (warning: one non-word, don't rely on grep -w)
-
For the precise format of the release text in the tag below, you can look at old tags with:
git show --quiet "v0.11^{tag}"
-
Tag master with the new version (tag with -a to annotate with the above release text) => In GH, copy the release text to a release for the tag, use "##" for section headers: https://github.com/Azure/mmlspark/tags (leave the subject empty, so it'll use the existing tag name) => Clear the environment, just in case: > ssh ms-vm rm -rf lib => run a build with PUBLISH=all
-
Lock the build in VSTS to retain it indefinitely
-
prepare a "mmlspark-X.Y.zip" file:
cd ~/tmpV="0.12"U="https://mmlspark.blob.core.windows.net/"U+="maven/com/microsoft/ml/spark/mmlspark_2.11"- mmlspark-X.Y.jar:
curl "$U/$V/mmlspark_2.11-$V.jar" -o "mmlspark-$V.jar"
- mmlspark-X.Y.pom
curl "$U/$V/mmlspark_2.11-$V.pom" | \ sed -e 's#<\(groupId\)>com.microsoft.ml.spark</\1>#<\1>Azure</\1>#' \ -e 's#<\(artifactId\)>\(mmlspark\)_2.11</\1>#<\1>\2</\1>#' \ -e '$a\' > "mmlspark-$V.pom"
zip "mmlspark-$V.zip" "mmlspark-$V.jar" "mmlspark-$V.pom"rm "mmlspark-$V.jar" "mmlspark-$V.pom"
-
https://spark-packages.org/package/Azure/mmlspark version: X.Y git commit sha1: 0123456789012345678901234567890123456789 license: MIT License maven coordinates: EMPTY (later: com.microsoft.ml.spark:mmlspark_2.11) file:
rm "mmlspark-$V.zip" -
Clean up the redundant tags (X.Y-1.9:non-plus images, X.Y:plus images)
-
Update the version here: https://github.com/Azure/aztk/wiki/PySpark-on-Azure-with-AZTK
-
Advertise Release