Answers.Body: <p>In terms of Extensions, and we (Fuzion) have contributed a fair few of them, I think it is fair to say that in our case, since all our clients are still on 4.6.x, we simply have not had cause to see what breakages might happen with 4.7.</p>
  
  <p>We build extensions with the long-term in mind and since Eileen is very much part of the team outside of core that is helping with that long-term view (and building API etc) i would expect our extensions to be as future-proofed as was possible at the time of the original build.</p>
  
  <p>It can be really helpful to the community if you and others can help push these community assets forward by doing some testing of Extensions on 4.7 and reporting back via their git repository as to how much the fail/succeed.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T02:16:32.993Z
Answers.Text: Thanks for the Information, I will post another question about getting my data and settings out before downgrading
Answers.UserDisplayName: Zeak Smith
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T01:33:28.560Z
Answers.LastActivityDate: 2016-03-09T01:33:28.560Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>In general, 4.7 is a "development" release. 4.6 is a "long term support (LTS) release". Most people would recommend 4.6 (or even 4.4!) for very stable websites, and only using 4.7 if you need the latest features or are developing for the future.</p>
  
  <p>As an extension contributor myself, there's a reasonable functionality jump between 4.6 and 4.7, so it may be some time until every extension is on there, and some may never get there. It depends on the extension and the developers who maintain them.</p>
  
  <p>Unfortunately, there is no way to "downgrade". Your best options are to:</p>
  
  <p>1) Manually download and install the extensions, put them in the extensions directory, and then test them. They will probably mostly work, but you will need to do this testing yourself.</p>
  
  <p>2) Contact the developers of the key extensions, asking them for a timeframe of when they will be supporting 4.7</p>
  
  <p>3) Hire a freelancer or agency to update them to 4.7 for you. I would be more than happy to do this - <a href="http://civifirst.com" rel="nofollow">http://civifirst.com</a>, or you could look for a partner agency at <a href="http://civicrm.org/partners-contributors" rel="nofollow">http://civicrm.org/partners-contributors</a>.</p>
  
  <p>4) If you do decide to move to 4.6, you can easily export and import your configurations and data. If you find yourself needing to do this, do ask here in a different thread.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T02:14:44.993Z
Answers.Text: Thanks for the advice, I did not realize that 4.7.3 was more a developer release, we are going for stable as possible so if the main herd is going with 4.6 then we will do the same
Answers.UserDisplayName: Zeak Smith
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T05:57:25.313Z
Answers.Text: Difference of opinion. I don't agree with JohnFF's assessment re 4.7 as a 'developer' version. It is the version the civi core team provide as the default download. And I certainly would not be recommending 4.4.x as it is uncertain if all security issues will be addressed for that release.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T06:07:48.017Z
Answers.Text: i wanted to 'edit' the above as i shouldn't assume it is John's assessment.  he may well be quoting from other sources/discussion. But if that is the commonly held view, then I think the core documentation should be clearer about that. Certainly nothing as such is stated eg https://civicrm.org/blogs/yashodha/civicrm-470-is-out
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T11:46:11.330Z
Answers.Text: I might clarify here: "developer version" might have been the wrong phrasing:
  It isn't an LTS version. It contains up to date latest features but is in flux and is liable to change lots and soon!
  LTS versions are much less transient.
  When I said "for the future" I meant for a long project likely to be released not imminently.
  I thought 4.4 was still being supported WRT security features? Is that not the case?
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-09T00:54:01.820Z
Answers.LastActivityDate: 2016-03-09T00:54:01.820Z
Answers.UserDisplayName: JohnFF
Body: <p>I am a complete CiviCRM noob I am the ICT adviser to a small non-profit Paramedic service. We are going to be using CiviCRM to replace a ancient filemaker database.</p>
  
  <p>I thought I was doing the right thing and installing the latest version of CiviCRM but it seem that just about none of the extension are compatible with 4.7.3</p>
  
  <p>Am I missing something should I have installed 4.6.14 instead, if so is there a way to downgrade without having to start again?</p>
  
  <p>I would not be to concerned but much of the features we are looking for are only covered by extensions</p>
  
  <p>thanks in advance</p>
  
  <p>Zeak    </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-09T05:58:24.907Z
Comments.Text: Why not be specific about the Extensions you have in mind.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-09T06:04:23.297Z
Comments.Text: BTW i opened this ticket here to try and crowdsource more info about which extensions are known to work on 4.7.x http://civicrm.stackexchange.com/questions/10280/which-extensions-are-you-using-with-4-7-which-do-not-yet-state-they-have-a-4-7-r
Comments.UserDisplayName: petednz - fuzion
Tags: <upgrade>
Title: 4.7.3 Vs 4.6.14
ThreadText: # 4.7.3 Vs 4.6.14
  
  (Asked by: username_0 on 2016-03-09)
  
  I am a complete CiviCRM noob I am the ICT adviser to a small non-profit Paramedic service. We are going to be using CiviCRM to replace a ancient filemaker database.
  
  I thought I was doing the right thing and installing the latest version of CiviCRM but it seem that just about none of the extension are compatible with 4.7.3
  
  Am I missing something should I have installed 4.6.14 instead, if so is there a way to downgrade without having to start again?
  
  I would not be to concerned but much of the features we are looking for are only covered by extensions
  
  thanks in advance
  
  username_0
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: Why not be specific about the Extensions you have in mind.  
  > **username_1**: BTW i opened this ticket here to try and crowdsource more info about which extensions are known to work on 4.7.x http://civicrm.stackexchange.com/questions/10280/which-extensions-are-you-using-with-4-7-which-do-not-yet-state-they-have-a-4-7-r  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-03-09. Score: 3 | Accepted answer
  
  In general, 4.7 is a "development" release. 4.6 is a "long term support (LTS) release". Most people would recommend 4.6 (or even 4.4!) for very stable websites, and only using 4.7 if you need the latest features or are developing for the future.
  
  As an extension contributor myself, there's a reasonable functionality jump between 4.6 and 4.7, so it may be some time until every extension is on there, and some may never get there. It depends on the extension and the developers who maintain them.
  
  Unfortunately, there is no way to "downgrade". Your best options are to:
  
  1) Manually download and install the extensions, put them in the extensions directory, and then test them. They will probably mostly work, but you will need to do this testing yourself.
  
  2) Contact the developers of the key extensions, asking them for a timeframe of when they will be supporting 4.7
  
  3) Hire a freelancer or agency to update them to 4.7 for you. I would be more than happy to do this - <http://civifirst.com>, or you could look for a partner agency at <http://civicrm.org/partners-contributors>.
  
  4) If you do decide to move to 4.6, you can easily export and import your configurations and data. If you find yourself needing to do this, do ask here in a different thread.
  
  > **Comments:**
  > **username_0**: Thanks for the advice, I did not realize that 4.7.3 was more a developer release, we are going for stable as possible so if the main herd is going with 4.6 then we will do the same  
  > **username_1**: Difference of opinion. I don't agree with username_2's assessment re 4.7 as a 'developer' version. It is the version the civi core team provide as the default download. And I certainly would not be recommending 4.4.x as it is uncertain if all security issues will be addressed for that release.  
  > **username_1**: i wanted to 'edit' the above as i shouldn't assume it is John's assessment.  he may well be quoting from other sources/discussion. But if that is the commonly held view, then I think the core documentation should be clearer about that. Certainly nothing as such is stated eg https://civicrm.org/blogs/yashodha/civicrm-470-is-out  
  > **username_2**: I might clarify here: "developer version" might have been the wrong phrasing: It isn't an LTS version. It contains up to date latest features but is in flux and is liable to change lots and soon! LTS versions are much less transient. When I said "for the future" I meant for a long project likely to be released not imminently. I thought 4.4 was still being supported WRT security features? Is that not the case?  
  
  ---
  
  ### Answer by username_1 on 2016-03-09. Score: 2
  
  In terms of Extensions, and we (username_1) have contributed a fair few of them, I think it is fair to say that in our case, since all our clients are still on 4.6.x, we simply have not had cause to see what breakages might happen with 4.7.
  
  We build extensions with the long-term in mind and since Eileen is very much part of the team outside of core that is helping with that long-term view (and building API etc) i would expect our extensions to be as future-proofed as was possible at the time of the original build.
  
  It can be really helpful to the community if you and others can help push these community assets forward by doing some testing of Extensions on 4.7 and reporting back via their git repository as to how much the fail/succeed.
  
  > **Comments:**
  > **username_0**: Thanks for the Information, I will post another question about getting my data and settings out before downgrading  
  
  ---
  
  