Release Mailchimp 1.3

Hi Peter,

We are excited that you're motivated to contribute to MailChimp because there are lots of issues that are needing work. So, I thought I would take a few minutes to explain our development process and give you some thoughts about the best ways to spend time to have the most impact on making MailChimp a great module.

The best thing to do is to work directly on issues marked active. Issues that are marked active are ones that need code written for them, and jumping in and writing patches there is huge. This is the single most important thing you can do to help.

Issues marked "Needs review" need the patches reviewed for coding standards, tested that the problem still exists, and tested that the patch indeed fixes the problem. Finally, patches marked "Reviewed and tested by the community" are ready for Amy to commit to the Dev branch. Once the dev branch becomes substantial enough, we tag and push a release. We are very careful with this step.

As patches reach the "reviewed and tested stage", we commit them and roll releases for everything that is ready. Many of the issues you've tagged here are still in the "active" state and will not be included in a release until the other steps in the process have been completed first. Some of them might be done in a day or two, but others might take months. I'm going to close this ticket so that months in the future, people are not confused about which features are in a release and which don't make it. For each release, you can see the complete release notes of everything in that release: https://www.drupal.org/project/mailchimp/releases/8.x-1.1

Let me know if you have any questions!
~Greg