LDAP 0.14.0

[PVince81]

When taking care of a task (and marking as done), please add your name to the task!

Reason

• Add network timeout Add network timeout #324
• Allow avatars to be changed by users if not provided by LDAP - #188
• Remove PHP 5.6 support - #388
• LDAP configuration is now stored JSON encoded - #393 reverted for this release
• Clean up Application initialization code - #396
• Remove unused use statements - #399 #400
• Do not return unavailable users - #12
• Fix paging when limit is used - #315
• Reuse existing LDAP accounts if available Reuse existing LDAP accounts if available #165
• Replace magic numbers with constants Replace magic numbers with constants #435
• Log bind errors Log bind errors #436
• Simplify connection: Get rid of init method Simplify connection: Get rid of init method #437

QA

• Create QA Milestone
• Move items from development to qa @davitol
• Create release branch with the format "release-0.14.0" @patrickjahns
• Create "0.14.0 Testplan" @davitol Tracking Testing Results for v.0.14.0 #446
• Test and document in testplan => Final "Go" from QA (set 'QA-ready' label) @davitol

Documentation

• Changes in the docs needed?

Marketing

• Ping RocketChat channel #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)
• Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (final release date unknown)

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 @davitol

Final

• Create github tag for final 'v${version}' on release branch
• Build and sign final tarball from github tag 'v${version}' (see
  handbook for how to build)
• Upload as Github release using changelog entries
• Smoke test tarball (at least install + enable) @davitol

Publishing

• Upload tarball to marketplace (see handbook for details)
• Publish tarball for customers (see handbook for details)
• Send mail to release-coordination with link to this ticket and to the changelog

Post-release

• Rename QA milestone to '$version'
• Add a new 'Unreleased' section in CHANGELOG.md and add release 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

[PVince81]

• clarify change of behavior:
  • config is now JSON, is this ok for support ? => ok Config to json #393 (comment)
  • "do not return not available users" need better wording, evaluate if admins need to be notified to double check their LDAP filters to avoid potential service disruption

@jvillafanez @cdamken @pako81 FYI

[PVince81]

• might want to branch off old tag to avoid PHP 5.6 deprecation that early

[pmaier1]

We added #165 to the reasons. Please include this PR @micbar.

[micbar]

@VicDeo Assigning you and adding to the tasks for next week.

[VicDeo]

"do not return not available users" need better wording, evaluate if admins need to be notified to double check their LDAP filters to avoid potential service disruption

what about "Validate group members against user filter"? If I'm not mistaken this is exactly what #12 does

[davitol]

@micbar user_ldap-0.14.0RC1 tarball is QA-ready

[phil-davis]

Note: when we try to "merge release-0.14.0 branch back to master" we are going to have to be careful, because actually we do not want to merge back:
PR #449 "hotfix" that was just to keep some compatibility ffor this release with core 10.2.1
PR #466 the last commit that disables running phan in CI (phan runs just fine in master)
and ...?