Answers.Body: <p>In general, extensions marked as compatible with 4.6 will usually work with 4.7 as well. It may be that the extension author just hasn't had a chance to test it and tag a new release for 4.7. I recommend you:</p>
  
  <ol>
  <li>Install the extension and try it out</li>
  <li>Notice if it works correctly or not. Gather specific details of anything that may be amiss.</li>
  <li>File an issue on the extension's github page noting your findings so that the maintainer can either fix the bugs or else tag a release as-is for 4.7.</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-09T07:57:40.270Z
Answers.Text: Thanks. I will try the extension out and see if it works or not.
Answers.UserDisplayName: Sudesh
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-07T15:23:16.787Z
Answers.LastActivityDate: 2016-12-07T15:23:16.787Z
Answers.UserDisplayName: Coleman
Body: <p>Can I install the latest Mailchimp extension on Civi 4.7.10 (Wordpress)?
  Are there any comparability issues?</p>
  
Tags: <extension><4.7.10><mailchimp>
Title: Mailchimp extension compatibility with CiviCRM 4.7
ThreadText: # Mailchimp extension compatibility with CiviCRM 4.7
  
  (Asked by: username_0 on 2016-12-07)
  
  Can I install the latest Mailchimp extension on Civi 4.7.10 (Wordpress)?
  Are there any comparability issues?
  
  **Tags:** extension, 4.7.10, mailchimp
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-12-07. Score: 1 | Accepted answer
  
  In general, extensions marked as compatible with 4.6 will usually work with 4.7 as well. It may be that the extension author just hasn't had a chance to test it and tag a new release for 4.7. I recommend you:
  
  1. Install the extension and try it out
  2. Notice if it works correctly or not. Gather specific details of anything that may be amiss.
  3. File an issue on the extension's github page noting your findings so that the maintainer can either fix the bugs or else tag a release as-is for 4.7.
  
  > **Comments:**
  > **username_0**: Thanks. I will try the extension out and see if it works or not.  
  
  ---
  
  