It's sufficient to add both provided p2 repository URLs to the list of available software sites (preferences > install/update > available software sites):
http://build.eclipse.org/technology/epp/epp_build/kepler/download/20140220-0320/repository/ http://download.eclipse.org/releases/maintenance/ Then you can hit 'Check for Updates' and you should get a message about available updates soon. This method should work with all Kepler packages (btw... it works with older versions of Eclipse, too). You don't need a p2 composite repository or anything else. Regards, Markus On Fri, Feb 21, 2014 at 4:58 PM, Beth Tibbitts <[email protected]> wrote: > David, > I'd like to test > >...at least that "SR1" levels can be updated to "SR2" ... and to do that > you might need to (re)read .. > > ...But I can't find enough info on the referenced links that says how to > assemble a "pseudo composite" to test updating e.g. from SR1 to SR2. It > says to look in epp-dev. Looked there. I'd assume that would work to use > "check for updates" on an SR1, and it would find the SR2 updates. > I googled a bit too. Perhaps I used to know how to do this a long time > ago, but can't reassemble the directions now. > > Point me to some directions, and I'll very gladly update the very useful > https://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ > > Thanks for all your help keeping us all straight. > > > > ...Beth > > Beth Tibbitts > [email protected] > > > On Fri, Feb 21, 2014 at 8:49 AM, David M Williams < > [email protected]> wrote: > >> I'm sure everyone knows that final builds are done ... but we always wait >> a week before formally releasing. This is partially to give one last chance >> to test for serious regressions. (If found, In most cases, we'd encourage >> projects to simply provide "patch features" on their own sites, if >> possible, but recognize that in some rare few cases a complete rebuild is >> required ... such as something can not install or "update" correctly due to >> cross-project issues). >> >> So be sure to test at least that "SR1" levels can be updated to "SR2" ... >> and to do that you might need to (re)read >> >> >> http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_staging_repository.3F >> >> and see EPP note for EPP repo locations >> >> http://dev.eclipse.org/mhonarc/lists/epp-dev/msg02938.html >> >> (the idea is to effectively "simulate" what will become a composite repo >> next week, that has three children, Kepler, Kepler SR1 and Kepler SR2.) >> >> A second thing to do is to prepare your final sites and pages. You can >> begin any time to move code to their "final locations" ... as long as you >> can, and know how, to "leave invisible". For "how to" see >> >> http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#How_is_a_final_build_made_.22invisible.22_until_release.3F >> (We encourage it to be done "early" so that the largest artifacts can be >> well mirrored during the week, before the actual "release day" when >> everyone makes things visible). >> >> Also don't forget to archive any old releases, if you can, and/or clean >> up interim builds, so that mirrors can more easily "hold" all the new >> stuff. >> >> Lastly, some projects may need to update their documentation on Eclipse's >> "info center". See >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=408828 >> but also seems to be some issue with it, besides merely updated docs? See >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=428730 >> (I'm not sure what the issue is). >> >> Much thanks ... good luck ... ask here if questions or problems. >> >> >> >> _______________________________________________ >> 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 > >
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
