> My expectation was that this kind of error should have been checked during the aggregation build.
My guess is that EPP features "add" relationships and dependencies that are not represented in aggregation builds. I think less of a problem in past when nearly everyone was doing "maintenance only" in service releases. Now that several projects are doing 'minor' releases in SRs, those projects need to better coordinate their contributions and/or perhaps there is a way we can add some EPP features to aggregation the builds directly, so the issues are found "earlier"? I think the way we do it now is perfectly equivalent ... it is just in two stages instead of one and might make it harder for people to "see" relationships/breakages in their own b3 aggregation editors. Which leads me to remind everyone of what I wanted to have said later today :) ... now that some projects are increasing minor versions in SRs, it will be more important than ever that we all test "update scenarios" ... going from SR1 to SR2, or even updating from SR0 to SR2. Besides both CDT and Linux Tools doing minor releases, I know that EGit has gone from 3.0.x to 3.2x from SR1 to SR2! I did test a simple update for that case and it and worked fine ... but, EPP packages are where it will matter most. I suspect there are others doing minor updates? But I don't have a list. There should be "release reviews" for anyone doing minor releases in an SR (but some of them, such as for EGit, and Linux Tools would have happened last month ... so do not know of an easy way to "see all reviews" from previous SRs. Perhaps easiest if those projects doing minor releases just let us all know here on cross-project list? Or perhaps Wayne could educate us on how to query for releases review over a period of several months? As a reminder, some basic steps on how to do "update" tests are spelled out in http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_staging_repository.3F Hope that helps ... 5 PM is coming up fast! :) Lucky this RC1 is a "warm-up", but please try to have RC2 in shape to be true "release candidates" ... i.e. very near "final". Thanks! From: Markus Knauer <[email protected]> To: Jeff Johnston <[email protected]>, Doug Schaefer <[email protected]>, Eclipse Cross Project Issues <[email protected]>, Date: 01/22/2014 09:37 AM Subject: [cross-project-issues-dev] Kepler SR2 - Linux - CDT - Problem Sent by: [email protected] Hi all, maybe you can help me solving this problem... the EPP build for Kepler SR2 RC1 is broken because of missing dependencies in the maintenance p2 repository. In particular there are some CDT features that require a specific version of Linux bundles. Either something in the CDT contribution is broken, or something from Linuxtools (???) is missing... <unit id='org.eclipse.cdt.platform.feature.group' version='8.3.0.201401210350' singleton='false'> <requires size='29'> ... <required namespace='org.eclipse.equinox.p2.iu' name='org.eclipse.cdt.core.linux.x86' range='[5.2.0.201401210350,5.2.0. 201401210350]'>... But there's only... <unit id='org.eclipse.cdt.core.linux.x86_64' version='5.2.0. 201309180223'> Maybe it fixes itself later today when all +3 contributions are in... in that case sorry for the noise. My expectation was that this kind of error should have been checked during the aggregation build. Thanks, Markus_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
