Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and Outlook for Indigo RC3

Here we are beginning +2 day ... and what a difference a day makes! Much
better. We are almost a release candidate.

ep's been updated
riena's back in.
windowbuilder is back in.
Everyone is "re-enabled"! Yay!  (except for the
org.eclipse.pde.api.tools.ee.fragments, which is not expected until RC4 --
final build -- per bug 362103)


PTP has taken care of their missing legal files (Thanks!)
This leaves only Papyrus to fix this blocking issue.
http://build.eclipse.org/indigo/simrel/reports/layoutCheck.txt
Papyrus team, can this be fixed for RC3? Please?
(If you need help, or don't understand why they are missing be sure to
ask).
Do you have a bug open on yourselves yet?

There's five features with old or non-standard license files (not sure if
this is a regression from SR1, or not, but deserves a look by effected
teams?)
http://build.eclipse.org/indigo/simrel/reports/licenseConsistency.html
      Features with different license:
      =======================
      org.eclipse.jubula.feature.launch.java.feature.group
      org.eclipse.jubula.feature.launch.rcp.feature.group
      org.eclipse.riena.build.feature.core.sdk.feature.group
      org.eclipse.riena.build.feature.samples.sdk.feature.group
      org.eclipse.riena.build.feature.sdk.feature.group

There are some "suspicious" mis-use of same-bundle-but-different qualifier.
http://build.eclipse.org/indigo/simrel/reports/nonUniqueVersions.txt
In many cases, this will be harmless, functionally, just uses extra disk
space, but there are cases were it could be harmful or lead to inadequate
testing ... only you can tell. And many of these do not come from Orbit.
Below are some of the cases that jump out at me, but there are a few others
in the full nonUniqueVersions report.


javax.activation (3? How'd we end up with 3 different versions! :)
		 1.1.0.v201005080500
		 1.1.0.v201105071233
		 1.1.0.v201108011116

org.pushingpixels.trident
		 1.2.0.v20110609-1700
		 1.2.0.201106090835

[I could be wrong ... but suspect these involving
'org.eclipse.persistence*' involve some lack of coordination between
EclipseLink and Webtools?  :( ]

org.eclipse.persistence.asm
		 2.3.2.v20111125-r10461
		 2.3.1.v20111014-r10236
org.eclipse.persistence.core
		 2.3.2.v20111125-r10461
		 2.3.1.v20111014-r10236
org.eclipse.persistence.jpa.jpql
		 1.0.1.v20111014-r10236
		 1.0.1.v20111125-r10461
org.eclipse.persistence.jpa.jpql.source
		 1.0.1.v20111014-r10236
		 1.0.1.v20111125-r10461
org.eclipse.persistence.moxy
		 2.3.2.v20111125-r10461
		 2.3.1.v20111014-r10236
org.eclipse.persistence.jpa
		 2.3.2.v20111125-r10461
		 2.3.1.v20111014-r10236
org.eclipse.persistence.antlr
		 2.3.2.v20111125-r10461
		 2.3.1.v20111014-r10236

So, not much to get to RC3 and then from there to RC4 ... well, except for
the little matter of everyone fixing their project's bugs and
regressions! :)

As always, test early, test often ... keep us posted ... and let us know if
questions.

Thanks,





From:	David M Williams/Raleigh/IBM@IBMUS
To:	cross-project-issues-dev@xxxxxxxxxxx,
Date:	02/06/2012 01:12 AM
Subject:	[cross-project-issues-dev] Status and Outlook for Indigo RC3
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx




Nag note ...

Here we are, at beginning of RC3 +1 day, and a few questions and
reminders ...

Has Eclipse ("the platform") contributed for RC3 yet?

I notice the contribution file says
M20120127-0800
but there is an M build from
M20120201-1336
which "sounds like" its closer to RC3, but, I do not know the intent.

I ask mostly on behalf of Riena project, which I have re-enabled, and I
expect that to fail, as they will need to prepare a build that "matches
exactly" the platform build, so I thought best to ask, and maybe they can
avoid doing it twice in same week?

I have also re-enabled windowbuilder. I am not sure if that pack.gz issue
has been fixed yet, but if you need help, be sure to ask.

There is still one missing (disabled) feature,
org.eclipse.pde.api.tools.ee.fragments, which if I understand bug 362103,
it will not be back in until the final build (RC4).

Remember that PTP and Papyrus still have "missing legal files",
http://build.eclipse.org/indigo/simrel/reports/layoutCheck.txt

>From the "non unique version numbers" reports
http://build.eclipse.org/indigo/simrel/reports/nonUniqueVersions.txt
It appears some projects are not using the latest Orbit repo ... or else
(worse) are not using Orbit at all, as they should be.
For Indigo SR2, please use the Orbit repo from
http://download.eclipse.org/tools/orbit/downloads/drops/R20120119162704/

Thanks,





_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev





Back to the top