builder: Generate commercial and community release notes separately

peter-b · peter-b · commit 125cbfbee7df · 2016-04-05T23:17:36.000+01:00
The release notes are actually the same, but this is the easiest way
to make sure that the release notes end up in both the community and
commercial editions' built guides folders.
diff --git a/buildbot.mk b/buildbot.mk
@@ -133,10 +133,12 @@ UPLOAD_MAX_RETRIES = 50
 ifeq ($(BUILD_EDITION),commercial)
   dist-docs: dist-docs-commercial
   dist-docs: dist-guide-commercial
+  dist-notes: dist-notes-commercial
 endif
 
 dist-docs: dist-docs-community
 dist-docs: dist-guide-community
+dist-notes: dist-notes-community
 
 dist-docs-community:
 	mkdir -p $(docs_build_dir)
@@ -153,11 +155,18 @@ dist-docs-commercial:
 	  --stage docs --edition business \
 	  --built-docs-dir $(docs_build_dir)/cooked-commercial
 
-dist-notes:
+dist-notes-community:
 	WKHTMLTOPDF=$(WKHTMLTOPDF) \
 	$(buildtool_command) --platform $(buildtool_platform) \
-	    --stage notes --warn-as-error
-	    
+	  --stage notes --warn-as-error \
+	  --built-docs-dir $(docs_build_dir)/cooked-community
+
+dist-notes-commercial:
+	WKHTMLTOPDF=$(WKHTMLTOPDF) \
+	$(buildtool_command) --platform $(buildtool_platform) \
+	  --stage notes --warn-as-error \
+	  --built-docs-dir $(docs_build_dir)/cooked-commercial
+
 dist-guide-community:
 	WKHTMLTOPDF=$(WKHTMLTOPDF) \
 	$(buildtool_command) --platform $(buildtool_platform) \
