Answers.Body: <p>If you go to the Extension page eg <a href="https://civicrm.org/extensions/civivolunteer" rel="noreferrer">https://civicrm.org/extensions/civivolunteer</a> then you should see a RELEASES section near the bottom which states what version of CiviCRM the extension is known to work for. This may be obvious, but your question doesn't explain what you have already done to check.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-11T13:02:19.907Z
Answers.Text: Thanks, Pete.  I should have been more descriptive.  I was asked to re-post the question apart from a previous two-part question and should have provided more context.
Answers.UserDisplayName: Angela
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-10T21:08:03.597Z
Answers.LastActivityDate: 2015-08-10T21:08:03.597Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>The best practice for upgrading is to upgrade a copy of your site on a "staging" or "development" server.  That's a good time to test your extensions to see if they work.</p>
  
  <p>Short of testing the extension, I don't know that there's a good way to ensure an extension works.  However, you can:</p>
  
  <ul>
  <li>Read the code, if you know how.  If it's all (or almost all) using API calls rather than BAO calls, you're probably safe.</li>
  <li>If you DO determine it to work well, post an issue on the ticket tracker for the extension (usually on Github) saying you tested it successfully with the latest version.</li>
  </ul>
  
  <p>There's a volunteer extension review team, and their job mainly covers reviewing new extensions, not existing ones - but if there were more people, we could do this sort of testing!</p>
  
  <p>With regard to this particular extension - it's mostly BAO calls, not API calls - but there's so little code, I'd be pretty surprised if it didn't work as-is on version 4.6.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-10T21:13:25.293Z
Answers.LastActivityDate: 2015-08-10T21:13:25.293Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>What is the best way to determine whether an extension is likely to be compatible with a contemporary Civi version rather than just not updated to reflect as much?</p>
  
Tags: <extension>
Title: How can I determine if an extension is compatible with a new Civi version?
ThreadText: # How can I determine if an extension is compatible with a new Civi version?
  
  (Asked by: username_0 on 2015-08-10)
  
  What is the best way to determine whether an extension is likely to be compatible with a contemporary Civi version rather than just not updated to reflect as much?
  
  **Tags:** extension
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2015-08-10. Score: 5 | Accepted answer
  
  The best practice for upgrading is to upgrade a copy of your site on a "staging" or "development" server. That's a good time to test your extensions to see if they work.
  
  Short of testing the extension, I don't know that there's a good way to ensure an extension works. However, you can:
  
  * Read the code, if you know how. If it's all (or almost all) using API calls rather than BAO calls, you're probably safe.
  * If you DO determine it to work well, post an issue on the ticket tracker for the extension (usually on Github) saying you tested it successfully with the latest version.
  
  There's a volunteer extension review team, and their job mainly covers reviewing new extensions, not existing ones - but if there were more people, we could do this sort of testing!
  
  With regard to this particular extension - it's mostly BAO calls, not API calls - but there's so little code, I'd be pretty surprised if it didn't work as-is on version 4.6.
  
  
  ---
  
  ### Answer by username_1 on 2015-08-10. Score: 5
  
  If you go to the Extension page eg <https://civicrm.org/extensions/civivolunteer> then you should see a RELEASES section near the bottom which states what version of CiviCRM the extension is known to work for. This may be obvious, but your question doesn't explain what you have already done to check.
  
  > **Comments:**
  > **username_0**: Thanks, Pete.  I should have been more descriptive.  I was asked to re-post the question apart from a previous two-part question and should have provided more context.  
  
  ---
  
  