|Re: [cross-project-issues-dev] Can we please stop using composite repos?|
_______________________________________________AFAIK, it comes from the simrel process of "making visible" the repository to the world (after the quiet / mirroring time). See code comment in https://git.eclipse.org/c/simrel/org.eclipse.simrel.tools.git/tree/promoteUtils/makeVisible.sh#n25Can the composite only include the current/latest version, or can someone educate me as to the value of having multiple versions?
It's a really good question. It just seems to be a "habit" to compose multiple children, usually with some restriction on the number of children, e.g., the most recent n children. But personally, just to make everything faster for the client and less overhead for the download.eclipse.org server, I would prefer to use a repo with a single child with the most recent version.
So what prompted everyone to have this habit?See also this FAQ entry https://wiki.eclipse.org/SimRel/Simultaneous_Release_Cycle_FAQ#Why_do_we_use_composites_anyway.2C_if_there_are_potential_problems_with_them.3FCheers,Mikaël BarberoTeam Lead - Release Engineering | Eclipse Foundation📱 (+33) 642 028 039 | 🐦 @mikbarberoEclipse Foundation: The Platform for Open Innovation and Collaboration
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top