Skip to content

Commit

Permalink
minor tweaks #8763
Browse files Browse the repository at this point in the history
  • Loading branch information
pdurbin committed Jun 13, 2022
1 parent 59d3697 commit 47d416b
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions doc/release-notes/5.11-release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ See also Issue #8191 and PR #8308.

### Muting Notifications

Users can control which notifications they receive if the system is [configured to allow this](https://guides.dataverse.org/en/5.11/admin/user-administration.html#letting-users-manage-receiving-notifications). See #7492.
Users can control which notifications they receive if the system is [configured to allow this](https://guides.dataverse.org/en/5.11/admin/user-administration.html#letting-users-manage-receiving-notifications). See also Issue #7492 and PR #8530.

## Major Use Cases and Infrastructure Enhancements

Expand Down Expand Up @@ -127,7 +127,7 @@ Due to a code change introduced in Dataverse 5.6, calls to the native API withou

## Complete List of Changes

For the complete list of code changes in this release, see the [5.11 Milestone](https://github.com/IQSS/dataverse/milestone/103?closed=1) in Github.
For the complete list of code changes in this release, see the [5.11 Milestone](https://github.com/IQSS/dataverse/milestone/103?closed=1) in GitHub.

For help with upgrading, installing, or general questions please post to the [Dataverse Community Google Group](https://groups.google.com/forum/#!forum/dataverse-community) or email [email protected].

Expand All @@ -139,7 +139,7 @@ If this is a new installation, please see our [Installation Guide](https://guide

0\. These instructions assume that you've already successfully upgraded from Dataverse Software 4.x to Dataverse Software 5 following the instructions in the [Dataverse Software 5 Release Notes](https://github.com/IQSS/dataverse/releases/tag/v5.0). After upgrading from the 4.x series to 5.0, you should progress through the other 5.x releases before attempting the upgrade to 5.11.

If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. Use `sudo` to change to that user first. For example, `sudo -i -u dataverse` if `dataverse` is your dedicated application user.
If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. Use `sudo` to change to that user first. For example, `sudo -i -u dataverse` if `dataverse` is your dedicated application user.

In the following commands we assume that Payara 5 is installed in `/usr/local/payara5`. If not, adjust as needed.

Expand All @@ -160,7 +160,7 @@ In the following commands we assume that Payara 5 is installed in `/usr/local/pa
3\. Start Payara

- `service payara start`

4\. Deploy this version.

- `$PAYARA/bin/asadmin deploy dataverse-5.11.war`
Expand Down

0 comments on commit 47d416b

Please sign in to comment.