Hi Mickael and all the other people who worked hard to get to this point,
This is great, well done! I had a look at the gerrit and it is quite nice. It certainly looks familiar. And despite my concerns listed below, moving to Tycho seems fairly obviously the way forward.
There are a few questions I have:
- B3 is split into multiple files, this Tycho solution has everything in a single file (two actually, pom.xml and category.xml). This has two disadvantages:
1. Merge conflicts - this is probably not such a big deal as the tycho validation seems very fast (2 minutes!).
2. Tracking who is paying attention. Until now the rule was touch the .aggrcon file, which then was easy to identify with git log. Is this rule important going forward? I believe so, and if so can we agree on a simple standard for what this looks like? e.g. The <id> of the repository in the pom.xml should have the simrel version that it was contributed for in the id?
- Updating version number ranges. The b3 aggregator has a very useful "fix versions" action that can set all the version ranges quickly and accurately. Is there some way to make this easier with Tycho?
- The gerrit today only has a subset of the parts of CDT that are in simrel.aggr/cdt.aggrcom (the only contribution I looked at closely). AFAICT only the items that are categorized are present in category.xml. Where do uncategorized features end up? Similar question about uncategorized bundles. I could add them all to a new category if needed.
BTW I don't know what other features of b3 may be important - but I don't know what this was: "sending emails for example wouldn't be available anymore." That is something I have not heard of.
Thanks,
Jonah