Re: [cross-project-issues-dev] Thanks for M3, on to M4!

[Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>]

From past experience the more repos the more confusion over what goes where and how long it is supposed to be there.

The extra repos are for a specific scenarios, though.  The communities that are trying to track them down are probably doing it deliberately and are trying "something else".  The main indigo repo, though, get's simplified and only has one version of everything in it.  That's a big plus for the early adopters.

Perhaps (specific scenarios) but for people just trying to live "near" the edge its a bit of an ask to get them to update every milestone.  You see it as "I want to compare with M2" but they see it as "we are shipping internally next week and have tested against M2".  Those folks might be considered special and told to use a different repo that had more milestones but in my experience that confuses people.  Certainly I have in the past been confused by all the repos flying around and in theory I have a chance of knowing what's going on :-/

It appears that the repo is a composite of the different milestone repos, perhaps the webmaster can exclude from mirroring the Mn-1 and Mn-2 "sub"-repos?  Its a bit of work but the settings only need to be tweaked once every 6 weeks or so.

Because the main repo says the subs exist, wouldn't this put the system in a state where the repo served up from the mirror would be discarded from p2 as invalid (it has child repos not on disk)?

I'm talking about the artifact repos. I'm pretty sure there is a way of configuring sub or reference repos such that they don't have to all be co-resident.  Certainly we'd have to try this to ensure the approach works.

Jeff