RC2 == R if everyone sends a +1. That's the reason why they are never published, but they are available for final testing - see Dani's mail or the announcement on epp-dev.
Thanks, Markus On Sun, 15 Dec 2019, 20:06 Matthias Sohn, <matthias.s...@gmail.com> wrote: > I can't find the RC2 packages, are they already available ? > Can't find them here > https://www.eclipse.org/downloads/packages/release/2019-12/rc2 > > -Matthias > > On Fri, Dec 13, 2019 at 4:11 PM Daniel Megert <daniel_meg...@ch.ibm.com> > wrote: > >> The Platform cannot envision all the ways it is used. We do what we can >> to test. So, as long as you test your stuff against all the milestones and >> then don't file bugs after RC2 - fine. >> >> Dani >> >> >> >> From: Greg Watson <g.wat...@computer.org> >> To: Daniel Megert <daniel_meg...@ch.ibm.com> >> Cc: Eclipse Cross Project Issues < >> cross-project-issues-dev@eclipse.org>, eclipse.org-committ...@eclipse.org >> Date: 13.12.2019 15:11 >> Subject: [EXTERNAL] Re: [cross-project-issues-dev] >> [eclipse.org-committers] Use Milestones/RCs To Test and Run >> Sent by: cross-project-issues-dev-boun...@eclipse.org >> ------------------------------ >> >> >> >> Projects have enough on their plates testing their own code, let alone >> testing the platform. This seems to be a deficiency in the regression >> testing of the platform, and should be handled by the platform team IMHO. >> >> Greg >> >> On Dec 13, 2019, at 5:23 AM, Daniel Megert <*daniel_meg...@ch.ibm.com* >> <daniel_meg...@ch.ibm.com>> wrote: >> >> It would be great if everyone could at least test or even better, run on >> the latest milestone/RC. Platform got a stop ship bug for 4.13 and one for >> 4.14 reported after RC2. The 4.13 bug was introduced in M3 and the 4.14 bug >> in M1. So, there would have been enough room to find the bugs earlier. >> >> Of course the Platform team does exactly that but everyone has its own >> patterns how to work and hence, unfortunately did not detect those bugs. >> >> Thanks to everyone who helps with testing! >> Dani >> _______________________________________________ >> *eclipse.org* <http://eclipse.org/>-committers mailing list >> *eclipse.org-committ...@eclipse.org* <eclipse.org-committ...@eclipse.org> >> https://www.eclipse.org/mailman/listinfo/eclipse.org-committers >> >> IMPORTANT: Membership in this list is generated by processes internal to >> the Eclipse Foundation. To be permanently removed from this list, you must >> contact e...@eclipse.org to request removal. >> _______________________________________________ >> 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 >> >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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
_______________________________________________ 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
