>> >> Can 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 > <http://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? > 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#n25 <https://git.eclipse.org/c/simrel/org.eclipse.simrel.tools.git/tree/promoteUtils/makeVisible.sh#n25>
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.3F <https://wiki.eclipse.org/SimRel/Simultaneous_Release_Cycle_FAQ#Why_do_we_use_composites_anyway.2C_if_there_are_potential_problems_with_them.3F> Cheers, Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
