> On Dec 8, 2018, at 10:04 AM, Stefan Seelmann <[email protected]> wrote: > > If time allows I'd suggest to follow the voluntary relocation. > > For Fortress, if you consider to merge the 4 repos into one, this would > be a good time now. Just create a new "directory-fortress" repo at > Gitbox [1] and merge the 4 into it, then request to delete the old > repos, so no relocation needed.
Trying to figure out how much work this is, and does it fit into my schedule for the next few weeks... We’ll call your recommendation option one. A new repo gets created, say directory-fortress, that would contain the four packages merged. That all seems pretty straight-forward. What else must be done — would a new pom be needed to drive the build/release of the four packages of the combined repo? In other words, does this change to combine the four into a single git project repo force us to also change the structure (and process) of the maven artifacts being built and released? Option two is to voluntarily relocate to gitbox, but not combine (yet). Option three is to delay migration until Feb's mandatory relo, which buys time to do the combine. Thanks —Shawn
signature.asc
Description: Message signed with OpenPGP
