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

[Sean Hall]

No build logic, but there's inherently changes to .vcxproj files and
packages.config when updating dependencies.

On Wed, Apr 28, 2021 at 1:47 PM Rob Mensching <rob at firegiant.com> wrote:

> > Should I hold off on submitting any more changes? I'm fixing more 32-bit
> assumptions which means updating basically all the repos.
>
> If you are just updating code then do continue. This has been a very
> challenging process and I don't want to hold up all coding. However, if you
> are changing build logic (appveyor.cmd, .targets, .props, .csproj,
> .vcxproj, etc.) outside of extensions then we should discuss because that
> is where significant merge conflicts will show up.
>
> I've done nothing in extensions yet, so changes there today are probably
> good. My dream is to get build dependent repos through Tools completed
> today.
>
> I am planning to go back and re-migrate all of the repos to pick up the
> changes since Saturday as soon as I get "dotnet tool install wix", wix
> build and WixToolset.Sdk.nupkg working. Then on to migrating extensions.
>
> I do not have solid estimates at this time as some things go fast and some
> things go very slow.
>
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean
> Hall via wix-devs
> Sent: Wednesday, April 28, 2021 8: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-highlig
> > hts/
> >
> > > 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/
>