[wix-devs] Repo Reorganization II: Segmented Mono-Repo

[Sean Hall]

The BootstrapperCore repo was archived and moved into the Burn repo.

The readme in the https://github.com/wixtoolset/integration repo should
give a couple of strategies to test local changes, and has bundle tests.

On Wed, Apr 28, 2021 at 1:48 PM Hoover, Jacob <Jacob.Hoover at greenheck.com>
wrote:

> Currently everything builds, but I am trying to figure out how to actually
> generate a bundle to test with.
>
>
>
> There are a few changes.
>
>    1. Just changing RSM -> Registry requires no External changes
>    2. Wanting to expose a new API to allow a Bundle to ask about a
>    related bundles variables requires:
>       1. Dutil: butil adding new methods
>       2. Engine interface changes to get the BA->Engine->MSG->Engine and
>       back
>
>
>
> I’ve locally built dutil, burn, Bal.wixext, balutil, BootstrapperCore, etc.
>
>
>
>
>
>
>
> *From:* wix-devs <wix-devs-bounces at lists.wixtoolset.org> *On Behalf Of *Sean
> Hall via wix-devs
> *Sent:* Wednesday, April 28, 2021 10:51 AM
> *To:* WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> *Cc:* Sean Hall <r.sean.hall at gmail.com>
> *Subject:* Re: [wix-devs] Repo Reorganization II: Segmented Mono-Repo
>
>
>
> > If you have changes to a micro-repo, best to let me know what
> repositories you are working in so we can coordinate getting your changes
> committed before the migration of those micro-repos.
>
> What does https://github.com/wixtoolset/UnifiedTest1/pull/5 mean? Should I
> hold off on submitting any more changes? I'm fixing more 32-bit assumptions
> which means updating basically all the repos.
>
> Jacob, what is the status of your preview.0 issue? What kind of changes are
> you having to make outside of Burn? Are your dutil changes all new
> functionality, so technically could be submitted to the Burn repo first and
> moved to dutil later? I don't want to make it any harder for you to push
> your changes.
>
> On Thu, Apr 8, 2021 at 2:41 PM Rob Mensching via wix-devs <
> wix-devs at lists.wixtoolset.org> wrote:
>
> > I am finally preparing the "segmented mono-repo" (a single repository
> with
> > top-level directories for each component of the WiX Toolset), as per
> >
> https://www.firegiant.com/blog/2021/3/4/wix-online-meeting-207-highlights/
> >
> > > We agreed in principle that we could recombine the WiX v4 micro-repos
> > into one mono-repo, with each former micro-repo as a top-level directory.
> > What remains as an exercise for the reader is how we can still accomplish
> > the goals of enforced code layering with the ability to "build the world"
> > and get a single change throughout multiple projects atomically.
> >
> > To maintain the history in each micro-repo, I will first commit a
> > top-level directory that matches the name of the micro-repo and move all
> > the micro-repo's content under that top-level directory. This (redundant)
> > top-level directory in the micro-repo will be its "segment" in the
> > mono-repo. Introducing the segment in the micro-repo allows me to merge
> > into the mono-repo with all the history from the micro-repo.
> >
> > I have a bit of final experimentation to complete before I start
> > committing top-level directories. If you have changes to a micro-repo,
> best
> > to let me know what repositories you are working in so we can coordinate
> > getting your changes committed before the migration of those micro-repos.
> >
> > ____________________________________________________________________
> > WiX Toolset Developer Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> NOTE: This email was received from an external source. Please use caution
> when opening links or attachments in the message.
>