By "publish a slice" do you also mean to ask it to be integrated into Pharo4? The general issue is that every new fix for the released Pharo40 has the *chance* of introducing some other problem, or adversely affecting someone else's idea of how the system should operate. Even with minimal quaility assurance for a release it takes effort to integrate fixes, so each needs to be evaluated for impact. So the options for Pharo 4 are: 1. Continually integrate fixes as they arise ==> ++effort 2. Continually integrate critical fixes only, hold all others for the next point release. 3. Hold all fixes for next point release. I don't see this as a critical fix :), so you'd be asking for (1.), when probably (2.) should be the rule. Now I had the idea that fixes for a release that were not immediately integrated might be published as a "hotfix" - taking Microsoft's terminology for an update fixing a specific issue without having gone through full quality control with all other fixes, so kind of "use at own risk". I'm not sure if that was popular or the best way to go about it. Possibly just adding "hotfix" in the mcz file name would provide enough to find them by filtering. cheers -ben On Thu, Jun 11, 2015 at 2:47 AM, Paul DeBruicker <pdebruic@gmail.com> wrote:
Hi
I've hacked together an implementation of format on accept & display.
I know someone is redoing that functionality to better suit future needs.
Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness?
Thanks
Paul