"IMHO, they are nowhere near close enough to ready to join Kepler."
That's essentially where I'm at also after digging around. There's a lot of ends that need to be tied still and not much time. The best course of action would be to try again in Kepler+1 time frame.
On Wed, Feb 6, 2013 at 9:34 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
Some observations.
XWT has a build that they're calling 1.0
The two bundles that I checked in their update site does not have
about.html files.
The Feature contains an old SUA (2005). Also references update
sites, and the Ganymede update site in particular.
secondaryUpdateSiteName=Ganymede Discovery
Site
There is no license in the feature.
AFAICT XWT uses a Buckminster-based build. They do not do appear to
be signing anything or using pack200.
There is no apparent download site, and no information on the
website indicating how to obtain builds. There is virtually nothing
(other than information that I've provided) on the project page.
I think that it was last year that we (okay, I) decided that any
project participating in the train had to have done at least one
release review prior to the uber release review. There is no
evidence that they intend to do this. In fact, there is little
evidence that they have done any due diligence to understand what is
required of release train participation.
IMHO, they are nowhere near close enough to ready to join Kepler.
Wayne
On 02/06/2013 03:31 PM, Chris Aniszczyk wrote:
Before I formally do this request Yves, can you point me towards
the project page and any older releases?
I see that the portal metadata is a bit out of date for the
project:
Since we have started the migration from e4 in
technology
August last year, we just complete now. The build is
accessible via this
URL http://download.eclipse.org/xwt/updates/
now. We’d like to join the Kepler Simultaneous
Release. On behalf of project
lead, I ask you kindly to lobby the Planning Council.
Please feel free to contact me if you need further
information.
-------------------
Please request the Planning Council Exception
Process[1] to
authorize XWT be integrated to the M5 build as well.