From: Bill Anderson <bill@immosys.com>
Ok, we seem to be expressing a need to differentiate changes that occur without source modificcation (and server restart/refresh), and those that occue via source code change. Otherwise, we would just call them patches and be done. :)
Actually, I'm wondering if there actually is a need to differentiate (via jargon) whether zope needs to be restarted or not...
oringinally, I porposed CorePatchHot and CorePatchCold for differentiating the two in this tree. Since you, Brian, have expressed a dislike for hot (I can understsand your argument, but do not agree with the conclusion), I now offer a slight change:
Online CorePatch Offline CorePatch
Wait -- I thought (based on the thread) that hot vs. cold was a measure of 'severity' or 'urgency'? You seem to be saying it's 'restart' vs. 'no-restart'?
For those with a secret librarian bend <0.75 wink>, one could further categorize these into:
CorePatch (or ProductPatch) Offline/Online Enhancement/Addon/Fix
So... how do hotfixes or security alerts fit into this scheme?
PS. It occurs to me some may not care for the OCP and OPP abbreviations.
Especially since it's not clear if the 'O' is Offline or Online... Still, CorePatch/ProductPatch seems the right direction, as does the subcategories...