Merge pull request #7164 from IQSS/7046-dataverse-5-release-notes

7046 dataverse 5 release notes
IQSS · Aug 17, 2020 · 63a9a7c · 63a9a7c
2 parents 4d0bef6 + 12bb8fc
commit 63a9a7c
Show file tree

Hide file tree

Showing 22 changed files with 318 additions and 214 deletions.
diff --git a/doc/release-notes/4529-download-by-dataset.md b/doc/release-notes/4529-download-by-dataset.md
diff --git a/doc/release-notes/4813-allow-duplicate-files.md b/doc/release-notes/4813-allow-duplicate-files.md
diff --git a/doc/release-notes/4977-facet-sort-setting b/doc/release-notes/4977-facet-sort-setting
diff --git a/doc/release-notes/5.0-release-notes.md b/doc/release-notes/5.0-release-notes.md
diff --git a/doc/release-notes/5093-7133-datacite.md b/doc/release-notes/5093-7133-datacite.md
diff --git a/doc/release-notes/6505-zipdownload-service.md b/doc/release-notes/6505-zipdownload-service.md
diff --git a/doc/release-notes/6545-solr-var-meta.md b/doc/release-notes/6545-solr-var-meta.md
diff --git a/doc/release-notes/6558-validate-files-on-publish.md b/doc/release-notes/6558-validate-files-on-publish.md
diff --git a/doc/release-notes/6634-primefaces-8.md b/doc/release-notes/6634-primefaces-8.md
diff --git a/doc/release-notes/6684-buttons b/doc/release-notes/6684-buttons
diff --git a/doc/release-notes/6895-payara-release-note b/doc/release-notes/6895-payara-release-note
diff --git a/doc/release-notes/6896-relpub-astro.md b/doc/release-notes/6896-relpub-astro.md
diff --git a/doc/release-notes/6918-publishing-lock.md b/doc/release-notes/6918-publishing-lock.md
diff --git a/doc/release-notes/6938-analytics-reload b/doc/release-notes/6938-analytics-reload
diff --git a/doc/release-notes/6956-shib-attribute-character-set-conversion.md b/doc/release-notes/6956-shib-attribute-character-set-conversion.md
diff --git a/doc/release-notes/6959-html-codebook.md b/doc/release-notes/6959-html-codebook.md
diff --git a/doc/release-notes/6961-payara-upgrade.md b/doc/release-notes/6961-payara-upgrade.md
diff --git a/doc/release-notes/6970-ip-addresses-behind-proxy b/doc/release-notes/6970-ip-addresses-behind-proxy
diff --git a/doc/release-notes/6980-datacite-reservation-upgrade.md b/doc/release-notes/6980-datacite-reservation-upgrade.md
diff --git a/doc/release-notes/7040-project-moves.md b/doc/release-notes/7040-project-moves.md
diff --git a/doc/release-notes/7189-tou-i18n.md b/doc/release-notes/7189-tou-i18n.md
diff --git a/doc/release-notes/README.md b/doc/release-notes/README.md
@@ -5,7 +5,7 @@ doc/sphinx-guides/source/developers/making-releases.rst documents the official p
 - As a developer, I want to express in my pull request when an addition to the release notes will be necessary.
 - As a developer, I want to be aware of changes that should be made to my dev environment after a pull request has been merged. These could be Solr schema changes or curl commands to reload metadata blocks, for example.
 
-# release-notes directory process
+## release-notes Directory Process
 
 - Create a Markdown file named after your branch (assuming your branch starts with an issue number as requested in doc/sphinx-guides/source/developers/version-control.rst) such as "5053-apis-custom-homepage.md".
 - In the file you created, give instructions for non-SQL upgrade steps that must be taken to run the branch in your pull request. Examples include Solr schema updates or reloading metadata blocks. (SQL updates are handled separately as indicated in doc/sphinx-guides/source/developers/sql-upgrade-scripts.rst.)