Done.

The ReleaseBuilder update is ReleaseBuilder.merge-dtl.191 and the
update map is update-dtl.437.mcm.

Dave

On Tue, Jan 22, 2019 at 11:44:10AM -0500, David T. Lewis wrote:
> Backporting ReleaseBuilder into the squeak52 update stream requires
> adopting the four changes in ReleaseBuilder-mt.194, while skipping the
> other changes in 191, 192, and 193.
> 
> In order to prevent file name conflicts between trunk and squeak52,
> I propose saving the new version in squeak52 with the name
> ReleaseBuilder.merge-XXX.191, and making a new update map to point
> to ReleaseBuilder.merge.
> 
> If there are no objections I will make those changes soon.
> 
> Dave
> 
> 
> On Tue, Jan 22, 2019 at 04:32:57PM +0100, Marcel Taeumel wrote:
> > Yes, we should backport the new version of ReleaseBuilder to squeak52 and then update the CI script on GitHub to make use of "ReleaseBuilder prepareProcesses" and "ReleaseBuilder saveAndQuit", which would then produce a repaired release image.
> > 
> > Kernel-mt.1211 is not needed for it. Only ReleaseBuilder-mt.194
> > 
> > 
> > Best,
> > Marcel
> > Am 22.01.2019 16:22:29 schrieb David T. Lewis <lewis at mail.msen.com>:
> > On Tue, Jan 22, 2019 at 07:10:27AM -0600, marcel.taeumel wrote:
> > > Here is an overview of the usual suspects:
> > >
> > >
> > >
> > > Best,
> > > Marcel
> > >
> > 
> > That looks very good, thank you for cleaning it up.
> > 
> > Should the changes go into the squeak52 stream also?
> > 
> > Dave
> > 
> > 
> 
> > 
> 
>