Science WG/2017 Release
- Early August, 2017: Get logo guidelines to Torkild (For details, see [| Issue #253: Develop Guidance For Triquetrum Logo]
- October 10, 2017: The Eclipse Science 2016 Release
Based on the Eclipse Science 2016 Release and on email from Tracy from June, 2017:
> At the SWG unconference in Toulouse, there was unanimous agreement that we should have a 2nd Science simultaneous release, following on from our successful one last year .
> The release will be scheduled for October 2017, with a proposed date of 10th October 2017. This would be 2 weeks before Eclipsecon Europe and once again use this release and conference as momentum to promote the latest of our great features.
> To start with, could the project leads who are happy to participate in this release please respond to this email to confirm the participation of their project in the simultaneous release.
The release will be called The Eclipse Science 2017 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.
Question: do we want to try to create a workbench that would combine projects, or is this out of scope for October 2017? (Based on the Eclipse Science 2016 Release)
This "release" will be a coordinated release in which all participating projects. If possible, each participating project will release on Oxygen.
- prepare a working version of their product that can be dubbed release X.Y.Z.
- complete all IP (See the IP team's work queue), Release Review and other Foundation requirements.
- all artifacts for participating projects are released at the individual project sites and through links at science.eclipse.org.
- do whatever else Wayne Beaton says we have to do. ;-)
- 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.
See The Eclipse Science 2016 Release for possible material
- Chemclipse (6/23/17 email from Philip Wenig)
- Need an offset +2, cause ChemClipse depends on Eclipse EAVP. So, Eclipse EAVP needs to be released first.
- Eclipse EASE
- Christian wrote on ease-dev: "Sounds good, as discussed on this lest few weeks ago I anyway plan to have a release ready for ECE '17"
- Eclipse EAVP (Needed by Chemclipse) (6/27/17 email from Robert Smith)
- Jonah wrote: "Similarly, EAVP may need a +1 over January. However, keep in mind that Eclipse SimRel does not have +X for every dependency (if they did I think the estimate I once saw would be 20+ days, plus infinity as there are circular dependencies!)"
- Eclipse January (6/23/17 email from Jonah Graham)
- Rich Beans (6/23/17 email from Matt Gerring)
- TeXlipse (6/23/17 email from Torkild U. Resheim)
- Triquetrum (6/23/17 email from Erwin De Lay)
- Erwin wrote: "Feeling optimistic after the January workshop in Toulouse, I'm considering trying out a first January integration in Triquetrum as well for the Science release. So we would be +1 over January as well then."
- Triquetrum 0.2.0
- TBD: 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.
Eclipse has guidelines about Release Version Naming:
Releases and IP CQs
"Interim Releases. Incubation Phase projects may make releases. All major and minor releases must go through a Release Review."
Release Review says:
"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."