Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Science WG/2016 Release

< Science WG
Revision as of 13:47, 29 July 2016 by Cxbrooks.gmail.com (Talk | contribs) (Removed redundant TBD section)

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.


Release Versions

Eclipse has guidelines about Release Version Naming:

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."

Retrieved from "https://wiki.eclipse.org/index.php?title=Science_WG/2016_Release&oldid=408216"

Back to the top