Answers.Body: <p>I'd like to build out more infrastructure for this.</p>
  
  <p>I've started an <a href="https://github.com/civicrm/civicrm-core/pull/13298" rel="nofollow noreferrer">Extension Compatibility List</a> which so far has the ability to blacklist an obsolete extension (my original use-case was for merging an extension into core), but it could be extended to blacklist a version of an extension with known bugs or security flaws.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-12T15:54:00.833Z
Answers.LastActivityDate: 2019-02-12T15:54:00.833Z
Answers.UserDisplayName: Coleman
Answers.Body: <p>Maybe a blog post / mailing list announcement? I've seen this type of thing happen before both with civi and elsewhere, and there's been a blog post / mailing list announcement made. Here's one example:
  <a href="https://civicrm.org/blog/dave-greenberg/do-not-use-v42x-upgrades-using-drush-possible-data-loss" rel="nofollow noreferrer">https://civicrm.org/blog/dave-greenberg/do-not-use-v42x-upgrades-using-drush-possible-data-loss</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-11T19:17:31.313Z
Answers.LastActivityDate: 2019-02-11T19:17:31.313Z
Answers.UserDisplayName: Demerit
Body: <p>On Friday one of the extensions, summaryfields popped up showing there is an upgrade available.  Well, for many, this upgrade causes all the civi menus to go away.  So while people should never ever apply an upgrade to production without first doing it a test environment, it happens and they are left scrambling to resolve it, (disable the extension).</p>
  
  <p>I'm pretty sure the folks who released the upgrade tested it and it worked in their environment, but apparently something got missed.</p>
  
  <p>The question is when something like this happens what's the best way to alert people not apply this upgrade?  Is there a way to "unpromote" it?</p>
  
  <p>(An issue was raised in github for this last Friday.)</p>
  
Tags: <extension><upgrade><summaryfields>
Title: What is the best way to raise awareness of a extension upgrade that breaks core fuctionality, e.g. all the menus went away?
ThreadText: # What is the best way to raise awareness of a extension upgrade that breaks core fuctionality, e.g. all the menus went away?
  
  (Asked by: username_0 on 2019-02-11)
  
  On Friday one of the extensions, summaryfields popped up showing there is an upgrade available. Well, for many, this upgrade causes all the civi menus to go away. So while people should never ever apply an upgrade to production without first doing it a test environment, it happens and they are left scrambling to resolve it, (disable the extension).
  
  I'm pretty sure the folks who released the upgrade tested it and it worked in their environment, but apparently something got missed.
  
  The question is when something like this happens what's the best way to alert people not apply this upgrade? Is there a way to "unpromote" it?
  
  (An issue was raised in github for this last Friday.)
  
  **Tags:** extension, upgrade, summaryfields
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-02-12. Score: 3
  
  I'd like to build out more infrastructure for this.
  
  I've started an [Extension Compatibility List](https://github.com/civicrm/civicrm-core/pull/13298) which so far has the ability to blacklist an obsolete extension (my original use-case was for merging an extension into core), but it could be extended to blacklist a version of an extension with known bugs or security flaws.
  
  
  ---
  
  ### Answer by username_2 on 2019-02-11. Score: 0
  
  Maybe a blog post / mailing list announcement? I've seen this type of thing happen before both with civi and elsewhere, and there's been a blog post / mailing list announcement made. Here's one example:
  <https://civicrm.org/blog/dave-greenberg/do-not-use-v42x-upgrades-using-drush-possible-data-loss>
  
  
  ---
  
  