Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [science-iwg] Science release, target platform and Orbit version

A couple of thoughts...

You don't have to build solely on Oxygen just because you are pulling from a new drop of Orbit. We pull from multiple releases of Orbit for ICE to get the bundles that we need. So I would say release primarily on Neon, but with your extra few bundles from the new repo too.

As far as timing goes, the reviews take only a couple of weeks, so your freeze date couple be as late as October 1st or so. The bigger problem at the moment is that the Ptolemy dependencies still haven't been approved through the CQ process, right? We can't even do the reviews if we don't make it through that process.

Jay


On Aug 17, 2016 4:55 PM, "Christopher Brooks" <cxh@xxxxxxxxxxxxxxxxx> wrote:
I think the Python work is really important.  I have a strong distaste for Python's whitespace policy, but I realize that Python has excellent mind share in the scientific community.  Supporting the Python interface would increase the usefulness and visibility of our work.

I'd like to see Triquetrum include this work, and if that means that Triquetrum needs to build on the Oxygen M2 Orbit, then that's ok with me.

I'm not sure about the timing, but I would not mind keeping our target dates as is and slipping them as necessary as we get closer.

_Christopher

On Wed, Aug 17, 2016 at 1:50 PM, Erwin de Ley <erwin.de.ley@xxxxxxxxxx> wrote:
Dear all,

I've been spending some time (learning how to) adding the Apache XML RPC and WS Common Utils to the Orbit project, and finally seem to be ready with that. The gerrit review should be ok now and the merge will be done in the coming days

This is a prerequisite for a clean Triquetrum target platform that also must support the Java->Python integration via an XML-RPC bridge (extracted from DAWN and contributed by Jonah).

Now the main issue :
- the analysis RPC stuff to provide a bridge to Python needs those (4) bundles as dependencies
- it should be part of our Triquetrum release, within the Science release
- Orbit will only offer those bundles in an Oxygen M2 milestone build, sometime in september (or I can request to promote a nightly build sooner)
- we'll be on the Mars.x (or Neon if multiplatform builds can be made to work)  as principal target platform


So this could be a problem both in :
- timing, as we would like to finish our work sometime mid September to allow sufficient time for all reviews etc
- and in "version"? I.e. do we allow to depend on Orbit for Oxygen for our builds/releases?

What would be the best approach?

regards

erwin

_______________________________________________
science-iwg mailing list
science-iwg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/science-iwg


_______________________________________________
science-iwg mailing list
science-iwg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/science-iwg

Back to the top