[MacPorts] #63981: Avoid Breaking Changes

[MacPorts]

#63981: Avoid Breaking Changes
-------------------------+--------------------
 Reporter:  ztroop       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:               |       Port:
-------------------------+--------------------
 This is a ticket around port release management improvements. I'd like to
 discuss some points raised in:

 https://github.com/macports/macports-
 ports/commit/c4e8bb15818ee2f0debe47b8e9bf5b4574a61c09

   Is there a way to revert this without causing another major disruption?
 This change has broken node14, wangle, watchman and all their dependants.

 Our builds broke because node14 failed to install.

   We knew that moving to openssl3 by default would expose some ports that
 would need pegging back to 1.1. This is not a surprise, or a problem. Just
 do it.

 I think it's reasonable to have some expectation of stability around a
 popular package management tool. A casual attitude towards breakage is a
 little concerning to say the least. My question in this ticket, if we can
 anticipate a potential breakage... Can we not plan or coordinate fixes
 before negatively affecting users?

-- 
Ticket URL: <https://trac.macports.org/ticket/63981>
MacPorts <https://www.macports.org/>
Ports system for macOS