PMC Meeting minutes

Meeting Minutes

August 17, 2022 - Alex, Tom, Lars

• API removal simplification
  • Use the @Deprecated(forRemoval=true, since="release_in_which_the_API_was_marked_for_deletion")) annotation and Javadoc for new API removals for bundles using Java 11 to mark API for removal, an extra entry in the removal document from https://github.com/eclipse-platform/eclipse.platform.common/blob/master/bundles/org.eclipse.platform.doc.isv/porting/removals.html is not necessary anymore
  • Keep the removal document for cases in which the bundle is below Java 11 or for other special which do not fit into the Java code
  • If appropriate the @noextend @noreference and @noinstantiate Javadoc annotation should be added to the class
  • After 2 years of announced deletion, the API can be removed
  • Javadoc generates far more detailed list of forRemoval API which can be seen at http://help.eclipse.org/latest/topic/org.eclipse.platform.doc.isv/reference/api/deprecated-list.html#forRemoval
  • Agreed by all present PMC members

Example:

 * @noextend This class is not intended to be subclassed by clients.
 * @noreference This class is not intended to be referenced by clients.
 * @noinstantiate This class is not intended to be instantiated by clients.
 * @deprecated Use
 *             {@link org.eclipse.core.databinding.conversion.text.NumberToStringConverter}
 *             instead, which does not use {@code com.ibm.icu} as that package
 *             is planned to be removed.
 */
@Deprecated(forRemoval = true, since = "4.16")

....

• Merge of repositories
  • Overall positive effect for future work in Equinox
  • Simplifies releng work significantly
  • Merge of repositories will continue after the September release
• September release looks good, no big regression

August 10, 2022 - MQ, Jay, Alex, Tom, Lars

• Performance issue with Equinox startup in currently in analysis https://github.com/eclipse-equinox/equinox/issues/93
• I-Build is now using Java 17, platform is still requiring Java 11
• Discussion about platform move to Java 17, currently it is not planned to require Java 17 in the platform
  • Should be based on features in the Java language
  • M2e already requires Java 17 and Tycho plans to move to Java 17

2022-07-20 - Alex, My, Jay, Tom

• Publish meeting minutes

  • Publish today's minutes to PMC mailing list for openness.
  • Look into finding a "permanent" place to post minutes starting with some of the coming meetings.
  • https://github.com/eclipse-platform/.github/wiki looks like the best place so far.
  • Move old minutes too?

• De-Orbitization of Platform

  • Effort started after last release issues with custom mapping
  • Do as much as possible for this release
  • Upstream improvements - BouncyCastle, Lucene, etc. will have to happen before more switches can happen
  • Some libraries (e.g. JUnit 4.x) will stay from Orbit as long as they are shipped as Maven Central doesn't have them as OSGi bundles
  • Cross-project notification email need (Jay)
  • Already sent by Mickael, projects are building using Maven for years and projects have to move to using Maven libraries directly so in a way it's simplification of the process (Alex)
  • If there is unclear case/need for more explanation we need exact questions to act on

• Tycho OSGi Connect usage

  • FYI very promising effort to simplify our main build tool (https://github.com/eclipse/tycho/pull/1152)
  • Connect is very specific API for very tight problem zone so hopefully it works for the Tycho use case (Tom)