Revision as of 17:03, 9 August 2016

Schedule

• October 21, 2016: The Eclipse Science 2016 Release

Summary

Based on March 16, 2016 email from Jay Jay Billings

At our March, 2016 Annual meeting in Reston, we decided that we would have a release of a subset of Science Working Group Projects.

The release will be called The Eclipse Science 2016 Release.

This is similar to the the simultaneous release for Eclipse Eclipse. Each participating project would release their work at the same time as a separate release. Eventually, we might create a workbench that would combine projects, but that is out of scope for October, 2016.

This "release" will be a coordinated release in which all participating projects. If possible, each participating project will release on Neon.

Todo items:

1. prepare a working version of their product that can be dubbed release X.Y.Z.
2. complete all IP (See the IP team's work queue), Release Review and other Foundation requirements.
   1. On May 6, Sharon Corbett wrote and stated that the CQs for the following products likely be done in time: Ice - 2 CQs, Triquetrum - 10 CQs, EAVP - 1 CQ. January has no CQs. There was no mention of ChemClipse.
3. all artifacts for participating projects are released at the individual project sites and through links at science.eclipse.org.
4. do whatever else Wayne Beaton says we have to do. ;-)

Participating projects

• Todo:
  • Please add or remove your project here (in alphabetical order)
  • Linking to Eclipse Wiki pages and GitHub or Bugzilla issues is preferred.
  • Each project should consider
    • determining a release name (0.1?) (See below)
    • Collecting up IP issues, perhaps in a GitHub or Bugzilla issue
    • When ready, asking for release review.

Having a project listed here is a commitment to consider the possibility of releasing at the same time. Listing a project as part of the release need not be considered cast in stone.

• ChemClipse
  • ChemClipse Release Version: 0.7.0
  • ChemClipse IP, release review (Search https://dev.eclipse.org/ipzilla/query.cgi for Component: technology.chemclipse):
    • ChemClipse
    • Apache Commons Math 3.5.0 [1] (approved)
    • ConcurrentLinkedHashMap 1.4.0 [2] (approved)
    • EJML 0.27.0 [3] (approved)
    • Javassist 3.19.0 [4]
    • jna-platform-4.1.0.jar Version: 4.1.0 (PB CQ 9292) [5]
    • JSR305 1.3.9 [6] (rejected)
    • OrientDB 2.0.9 [7]
    • SWTChart 0.9.0 (PB CQ 8009) [8]
    • SWTXYGraph 2.1.0 [9] (withdrawn, became part of Eclipse)
    • Snappy Java (Xerial) 1.1.16 *SUBSET* [10]
    • Maven repository for IP-approved libraries/artifacts
    • Process for managing/providing IP-approved Maven artifacts
  • ChemClipse IP, other requirements:
    • Discuss how we can migrate our data import converters to Eclipse. Reading various data formats is essential for the ChemClipse project.
• EAVP
  • EAVP Release Version: TBD
  • According to 7/29/16 email from Jay, ICE will release against January.
  • EAVP IP, release review and other requirements Search https://dev.eclipse.org/ipzilla/query.cgi for Component: technology.eavp):
    • EAVP Initial Contribution
• ICE
  • ICE Release Version: TBD
  • According to 7/29/16 email from Jay, ICE will release against January.
  • ICE IP, release review and other requirements (Search https://dev.eclipse.org/ipzilla/query.cgi for Component: technology.ice)
    • VisIt Java Client - Approved
    • ICE Geometry Editor JavaFX conversion - Approved
• January
  • January Release Version: TBD
  • January IP, release review and other requirements (Search https://dev.eclipse.org/ipzilla/query.cgi for Component: technology.january): TBD
    • As of 8/9/16, the initial contribution CQ (11665) had been entered (and fixed) for January.
    • 7/29/16 Email from Jonah, updated with IP CQ status:
      • "I need to submit piggyback for a few things for January, I am not sure whether some of these have global approvals already:"
        • #11787 ANTLR runtime (approved)
        • 11788 Guava Guice (I think, com.google.inject package) (approved)
        • #11781 slf4j (approved)
        • #11789 Apache log4j (approved)
        • #11786 glazed lists (approved)
        • #11782 Apache Commons Lang Version: 3.1.0 (PB Orbit CQ6123) (approved)
        • #11783 Apache Commons Lang Version: 2.6 (PB Orbit CQ6450) (approved)
        • #11785 Apache Commons Math 3.5.0 (PB Orbit CQ10384)(approved)
        • #11784 Apache Commons Math Version: 2.1.0 (PB Orbit CQ4874) (approved)
        • Jama (Jay is not sure if this is in Orbit) (Jonah wrote: "Jama is only in the MANIFEST and the current code does not depend on it.")
      • Jonah wrote: "The rest are on orbit, but some are in the "new" orbit that does not have an official release yet, and therefore no retained builds. The orbit folk are hard at work on that at the moment: https://dev.eclipse.org/mhonarc/listsN/orbit-dev/msg04524.html"
• Triquetrum
  • Triquetrum Release Version: GitHub #71: Triquetrum First Release: 21st October 2016
  • Triquetrum Initial Contribution CQ - Approved
  • Triquetrum IP: GitHub #70: Triquetrum CQs
  • Triquetrum release review and other requirements: TBD
  • Jonah's work on integrating Python scripts from Java via XML-RPC has been submitted as CQ11664
  • the DRMAA group supports adding Java DRMAA API (v1 and v2) source bundles in Triquetrum (+ the impls we will migrate from DAWN&Passerelle for SGE and SLURM). Erwin would like to have that available with the release as well, but this still needs to be done.
  • There are a couple of open issues that are still important to get implemented/resolved to have sufficient scope in the workflow editor. (especially related to hierarchical modeling)

Release Versions

Eclipse has guidelines about Release Version Naming:

• Eclipse Project Handbook: Release
• Version Numbering

Releases and IP CQs

https://wiki.eclipse.org/Development_Resources/HOWTO/Incubation_Phase says:

"Interim Releases. Incubation Phase projects may make releases. All major and minor releases must go through a Release Review."

Release Review says:

"Intellectual Property"

"Before you can consider a Release Review, all of the relevant CQs must be approved by the Eclipse Legal team. We cannot schedule a Review before the Legal team has completed their work. If you are waiting for CQs, please review where your CQs are, and when they are scheduled to be reviewed, in the IP team work queue."

On March 21, 2016, Wayne Beaton described the release process for projects in incubation:

"Projects can do releases while in incubation."

"All CQs for code/libraries that are included in the release bits must be closed/approved by the IP Team prior to the release."

"In the time leading up to the release, you can and should distribute milestone builds that includes code/libraries that the IP team has granted checkin approval for. These are not official releases, and should be annotated as such (e.g. 0.7M2)."

"I recommend that the Science Working Group make a master list of all the open CQs that are required for the coordinated autumn release that we can present to the IP Team along with your last question. This should be a relatively easy query if we have a list of participating projects. Giving the IP Team a clear picture of what needs to be accomplished is the best way of getting that question answered."