[stable/*] bump dependency mariadb 1.0.3

[scottrigby]

PRs to review

• drupal #TBD
• ghost #TBD
• jasterreports #TBD
• jooma #TBD
• magento #TBD
• mediawiki #TBD
• moodle #TBD
• opencart #TBD
• orangehrm #TBD
• osclass #TBD
• owncloud #TBD
• phabricator #TBD
• phpbb #TBD
• prestashop #TBD
• redmine #TBD
• sugarcrm #TBD
• suitecrm #TBD
• testlink #TBD
• wordpress #TBD

Background

PRs opened using my dependency version bump utility script. See:

• Proposal: add dependency define command helm#1947
• feat(helm): add create command to 'helm dependency' helm#2041
• Proposal: Allow dynamic dependency override helm#2205

[scottrigby]

This one is on hold until #2004 is merged:

From @prydonius on Slack:

there is a PR for updating the storageClass pattern in MariaDB but it hasn't been merged yet. We should merge that first, and then update the other PRs for storageClassName to pull in the new mariadb before merging

[scottrigby]

This issue will also be updated to MariaDB v1.0.3:

From @mgoodness on Slack:

@scottrigby I merged MariaDB to v1.0.3 this morning. how do you want to handle the v1.0.2 dependency bump PRs?

Tl;dr, I'm going to close the 1.0.2 PRs, and reopen 0.1.3 equivalents, and edit this issue to point to those new PRs.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close