Custom groups 0.5.1

[HanaGemela]

Reason

Release needed for:

• Allow user to add to group even when enumeration to group is imposed #293
• Validation for max allowed number of chars in custom groups name #291

QA

• Generate Changelog
• Create QA Milestone and set the description to $version
• Move items from development to qa
• Create release branch with the format "release-$version"
• Create "$version Testplan" 0.5.1 Test Plan #303

Documentation

• Changes in the docs needed? If so create issue in owncloud/docs.

Marketing

• Ping @owncloud/marketing
• Check/adapt info.xml stuff
• Check/adapt screenshot
• Blog post or other communication if applicable

Build

All actions to be done on the release branch from here:

• Bump version in info.xml (no version suffix)
• Check php version dependency in info.xml
• Check minimum ownCloud version dependency in info.xml
• Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

• Create github tag for 'v${version}RC1' on release branch
• Build and sign RC tarball from github tag 'v${version}RC1' (see
  handbook for how to build)
• Upload as Github release using changelog entries
• Test and document in testplan => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

• Check that no documentation issues are pending
• Rename last RC tarball to final
• Create github tag for final 'v${version}' on release branch
• Upload as Github release using changelog entries

Publishing

• Upload tarball to marketplace (see handbook for details)
• Publish tarball for customers (see handbook for details) - customer.owncloud.com and portal.owncloud.com
• Send mail to release-coordination with link to this ticket and to the changelog
• Copy email to rocket chat #updates channel

Post-release

• Rename QA milestone to '$version'
• Add a new 'Unreleased' section in CHANGELOG.md
• Make sure, the current changelog section has a date '$version - $currentDate' (ex: 3.1.5 - 2018-08-01)
• Create PR to merge changes back to the master branch with
  description "Closes #XYZ" with the release ticket number
• Close the milestone
• Ensure release template is up to date

[HanaGemela]

@davitol RC1 ready https://github.com/owncloud/customgroups/releases/tag/v0.5.1RC1

[davitol]

@davitol RC1 ready https://github.com/owncloud/customgroups/releases/tag/v0.5.1RC1

@HanaGemela Tarball is QA-ready