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

Difference between revisions of "Eclipse/PMC"

m (typo)
(243 intermediate revisions by 9 users not shown)
Line 1: Line 1:
 
= Documents =
 
= Documents =
−
 
 
Some documents written and/or used by the PMC:
 
Some documents written and/or used by the PMC:
  
Line 8: Line 7:
 
= Meeting Schedule =
 
= Meeting Schedule =
  
−
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every wednesday at 10.30am EST'''.
+
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every Tuesday at 11.00am EST'''.
  
 
= Meeting Minutes =
 
= Meeting Minutes =
  
−
'''September 23, 2015''' - Dani, John, Alex, Martin
+
'''May 22, 2018''' - Alex, Tom, McQ, Dani
−
* Dani: '''JDT Core''' - Co-lead going to step up
+
* EPL 2.0
−
* Dani: '''API Removal Discussion'''
+
** Still working with foundation on whether we can gradually move to 2.0
−
** Q1: When do we actually delete API? What's the benefit compared to the pain that we cause ?
+
* Will we be supporting updates from release to release in the new 3 month release cycle?
−
*** Example TableTreeViewer : Continue having the API doesn't hurt, there's no significant benefit removing it
+
** Yes, unless we explicitly indicate otherwise.
−
**** Alex: TableTree was completely broken for 2-3 years ... keeping such components that don't work properly lowers the quality
+
** To simplify this, we should have a "latest" update site
−
**** Dani: But it's deprecated, no promise of working ... if it works for those who use it, it's fine ?
+
** We need to make this simpler for users, but not get in the way of the EPP, OOMF, etc.
−
**** John: EMF example - they have something generic across all JFace, regardless of whether it works or not; CDT could update easily
+
** Alex to write this up in more detail
−
*** Example of methods that don't do anything any more or do wrong things -- those should be removed
+
** Dani reminded us that there had been a previous discussion in the planning council
 +
* Project leads have updated Photon plans
 +
** Dani will be updating the overall plan; PMC to comment on bug 529640
 +
* Dani also working on release review and IP log
 +
** PMC members to approve once it's ready
 +
* As previously discussed our first milestone will be called "M2"
  
−
** Q2: '''How to deal with the versions?'''
 
−
*** Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
 
−
**** Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
 
−
**** For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
 
−
**** Plugins who don't care recompiling may have to live with ClassNotFoundException
 
−
**** Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
 
  
−
** John: '''Announcement''' When thinking about removing something, we should announce that far and wide and ask for feedback
+
'''May 15, 2018''' - Alex, Tom, McQ, Lars, Dani
−
*** Martin: But which channel is as effective as actually removing it ? There's always who don't actually listen...
+
* GDPR
−
*** John: Still, giving a possibility to listen is important. Agree that mentioning in the release docs is not enough.
+
** audit did not report any issues on our project pages
−
*** Dani: When making a release, also send message with a link to the removals page (for all removals that are planned)
+
* Opening development for 4.9
−
** John: Mechanisms for maintaining binary compatibility while only breaking source compatibility (but it's a lot of work!)
+
** Will branch RC2 and update master with required Releng work
−
*** Dani: Agree, in this case better just leave it in there
+
** master will be open after RC3
 +
* EPL 2.0
 +
** No plans to do anything for 4.8
 +
** Lars will look into it
 +
** Ideally we gradually move to 2.0
  
−
** Alex: What to do next time, can we remove more stuff ?
 
−
*** Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
 
  
−
** John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
+
'''May 8, 2018''' - Dani, Alex, Tom, McQ
−
*** Eg release but without all the deprecated at certain well-known point in time eg every 3-5 years
+
* GDPR
 +
** Eclipse Project collects no information from the users on the project websites
 +
** The Error Reporting tool, might be impacted
 +
** Also possibly bugzilla <-- Do we need to delete bugs older than some retention period?
 +
** Impossible to remove emails from all git repos (because of cloning)
 +
** We need to be sure to respond to requests from the foundation
 +
* Jetty
 +
** 9.4.10 is in latest build, and help system is working
 +
** they made the dependencies that were problematic optional
  
−
** '''Summary:''' Essentially do what we did, plus more communication upfront, allow people to respond before deletion happens (to avoid churn)
 
−
*** Committers still need to be able to delete stuff when they find it necessary.
 
−
*** Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
 
  
−
* Alex: '''Bumping the minimum GTK version again'''
+
'''May 1, 2018''' - cancelled due to public holiday in most Europe
  
  
−
<hr/>
+
'''April 24, 2018''' - Dani, Lars, Alex, Tom
−
'''September 16, 2015''' - John, Martin
+
* Target environments
−
* John: '''API Removal Discussion'''
+
** We will keep Java 8 and 10 and remove java 9 from the list
−
** No urgency now -- changes have been reverted for now, and scheduled for 2017
+
** remove JVMs as soon as they run out of support from target environments  - AGREED
−
** Updating the major of a bundle knowingly breaks everyone/most adopters
+
* javax.annotation
−
*** In the past, breaking changes have often been small enough to work without increasing the major
+
** Version  shipped is quite old, should we update it to newer version
−
*** One can argue that removing TableTreeViewer is big enough to warrant updating the major
+
** Update to latest standalone release to be tried
−
** Versioning packages has not been done in the past due to the huge upcoming maintenance effort when starting to do so
+
** Alex to try to drive this through
−
** "Release Version" is decoupled from "bundle versions" already (and may move to date-based versions eg "2016.1" with rolling updates moving forward
+
* Notify cross project about removal of ee modules from the JVM
−
** --&gt; will have more discussion next week
+
** People don't follow Java 11 work so will probably be surprised when things start to fail so we better try to spread the information
 +
** Dani will send a link to the JEP containing detailed information
 +
* Contribution guidelines
 +
** Do not open bugs for simple changes and cleanups
 +
** Actual bug fixes to be split from cleanups in separate patches so the bug commit is straight on the topic
 +
** Dani will update the wiki
 +
* Cancel May 1st call - public holiday in Europe
  
−
<hr/>
 
−
'''September 9, 2015''' - Dani, Alex, Martin, John, McQ
 
−
* John: '''Planning Council Updates'''
 
−
** 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
 
−
** Mid December rather than end to avoid churn, so this one is a little shorter
 
−
** Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
 
−
** McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
 
  
−
* Software is getting more important - would be good to better support multicore
+
'''April 17, 2018''' - Dani, Alex, McQ
 +
* On Java 11...
 +
** We are actually shipping the javax annotation support
 +
** Java 11 is working in 4.8, but isn't in 4.7.x
 +
*** Tom Watson is investigating why it is not working 4.7.x
  
−
* John: '''IntelliJ change in licensing / sales model'''
 
−
** Many eclipse-positive comments on the announcement blog
 
−
** Possibility putting Money on Eclipse Development may become interesting for companies in this context
 
  
−
<hr/>
+
'''April 10, 2018''' - Tom, Dani, Lars, Alex
−
'''September 2, 2015''' - Dani, Alex, Martin, John
+
* Discussed {{bug|533390}}: Eclipse does not launch with Java 11
−
* Dani: '''EclipseDay India''' on Saturday, 200 attendees wanted to join, hat to cut to 150
+
−
** Keynote by Mike Milinkovich - large Community
+
  
−
* Dani: '''Policy for and Mars.2'''
 
−
** Do we want to stick to the "Service" model or allow feature updates ?
 
−
** Mars.1 winding down -- sticking to "Critical Fixes Only" for that
 
−
** Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
 
−
** Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
 
−
*** Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
 
−
*** Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed
 
  
−
'''August 26, 2015''' -  
+
'''April 3, 2018''' - Tom, Dani, Mcq, Lars
−
* Dani/Alex/Martin can't join (traveling)
+
* 4.7.3a update
 +
** Delivered RC2 on Saturday, so we could fix some badness in handling Java 10 "var" support (tl;dr: rename appeared to allow you to affect "var" as if it were a type (but would not have modified the code))
 +
** Currently think we're done
 +
* Naming milestones
 +
** As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1".
 +
** We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming.
  
−
<hr/>
 
−
'''August 19, 2015''' - Alex, Dani
 
−
* nothing to discuss
 
  
−
<hr/>
+
'''March 27, 2018''' - Tom, Dani, Mcq, Lars, Alex
−
'''August 12, 2015''' - John, Dani
+
* Java packages for configured Java in workspace
−
* John asked whether we run on Windows 10
+
** Equinox no longer provides hard-coded information about execution environments.  In the past this information was used at runtime for describing the running execution environment within the OSGi Framework. Other usecases outside the Framework started uses the Java profile data from Equinox.  Equinox no longer has any need for the hard-coded information so no longer provides it.
−
** Dani: yes, the team already tested on it a few weeks ago. Runs smoothly one bug so far. Browser widget works despite new browser (Edge)
+
** JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
−
** ''Martin (added after the meeting): A CDT update is needed to keep the Terminal from hanging (see {{bug|474327}}, will release with Mars.1). Got some duplicates already. Workaround is switch the Win10 Console to "Legacy Mode".''
+
** JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
−
* Dani would like to get plan feedback by Friday EOD
+
** See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=531642 531642] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=532773 532773]
 +
* SWT clean-up
 +
** Lars reviewed the removal of Windows XP.  Built binaries locally on Windows.
 +
** Found a form data issue deleted some code that was still used
 +
** Tom - Unit tests didn’t catch the issue.  Concerning?
  
−
<hr/>
+
--> Update from Lars after the call: Later testing did show that this is a bug already existing in Eclipse. 4.7 and master and not related to the patch
−
'''August 5, 2015''' - McQ, John, Dani, Alex, Martin
+
−
* PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
+
−
** adding another release before Christmas might be a next step - even if Platform contributes identical bits
+
  
−
* Dani: '''[[Eclipse/Mars Retrospective]]'''
+
** Lars did review and test
−
** Move more components to Tycho build? (Would still need Ant to test against final build/bits)
+
** Dani - put all the code in the branch and produce a build and ask windows community to test it
−
** Contribution Review Dates: joined by some components but not all
+
** Mcq - thinks it is a good idea
−
** Error Reporter: Interesting to look at top ten but the sheer number is too big
+
** Dani - create an official build for testing, not out of master with normal builds
−
*** John - based on Orion experience with similar error reporting :
+
** Lars - what is the risk of putting in master
−
**** Looking at changes in reported issues is more interesting than looking at reports themselves
+
** Dani - can do the build right away pre-CQ review approval.  Allows for more quick testing.
−
**** Reports help getting contributions (But, Dani finds that "just adding a null check" is often not what's desired for Java .. though helpful for Javascript)
+
** Alex, no need for a branch, can be a developer build we publish.  Alex will ask Leo to do this.
 +
* Jetty version
 +
** Jetty added non-optional dependencies on service-loader
 +
** Dani - got reverted, but old versions still caused Gerrit build issue
 +
** We don’t need the service-loader for our usage of jetty
 +
** jetty may be making a hard requirement on an implementation of server-loader (Aries spi-fly)
 +
** Can we move help off jetty? Will be a major undertaking.  Should figure out what it would me to do so.  Currently no interested contributer has stepped up to do the work to figure out what this would mean.
 +
** Equinox will still need jetty for the http service implementation. Perhaps things are more simple if this is an Equinox only dependency. Only pull in jetty if the http service implementation is needed and then pull in all of jetty and its dependencies.
 +
** No current plans or interested contributors for providing our own service-loader implementation.
 +
** Our build should start resolving the capabilities are requirements which would catch issues like this early in the build.
 +
** Alex - can we move latest tycho to get the capability/requirements meta-data.  No objections?  Alex will move forward.
  
−
* Dani: Foundation IP team doesn't require updating copyright notices per contribution any more (since that information is in git anyways)
 
−
** The Project has to agree
 
−
** Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
 
−
** Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
 
−
** Dani to sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02422.html request for voting]
 
  
−
* Dani: Switching to '''Jetty 9.3.x (which requires JRE 8)'''
+
'''March 20, 2018''' - Dani, McQ, Tom, Lars, Alex
−
** JRE 8 from Oracle (and also from IBM) exists for all Reference Platforms
+
* Dani: The IBM SWT team considers the Windows XP removal too risky and in addition has no capacity to look at that big change. Fine if someone else looks at the removal. The type changes will have to wait after Photon (too risky). Lars will ask Conrad and Alex will also look at the patches.
−
** Except Solaris, because we only support Solaris 32-bit and the JRE only exists as 64-bit
+
* Databinding generification should be done early 4.9, too late for Photon.
−
** But the Plan for Neon is to have 64-bit Solaris support
+
* Dani: Eclipse support for Java 10 will be merged to the official branches starting Wednesday. A Marketplace entry for 4.7.3 will be made available once 4.7.3 is released. The first official release with Java 10 support is 4.7.3a scheduled for April 11.
−
** New Language features in Java 8 are adopted, contributors would like to start using Java 8
+
−
** McQ: In the past, staying on older Java was desired to enable more widespread use ... today, this argument does not seem valid any more, in fact likely more contributions / community is enabled by moving to Java 8
+
−
** Dani: Only concern is some "non reference" Platforms like HP-UX might not have JREs initially; but that's OK as long as the reference platforms are good
+
−
** '''AGREEMENT''' to move to JRE 8 and allow projects to use Java 8 in their code.
+
  
−
* Dani: Looking for a contributor for SWT improvements for GTK3
 
  
−
* Martin: '''libwebkitgtk-3 on Ubuntu 14 forcing GTK 2''' not working ?
+
'''March 13, 2018''' - Dani, McQ, Tom
−
** Alex: Using libwebkitgtk-4 which is much more stable, but not implementing the full SWT API
+
* Alex had troubles to join; Lars still in vacation
−
** Most distros don't ship libwebkit for gtk-2 any more since it's not supported upstream any more and has many security issues
+
* Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
 +
** ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project
  
−
* Alex: '''Build SWT at the Foundation'''
 
−
** Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month
 
  
 +
'''March 6, 2018''' - McQ, Tom, Alex
 +
* Short call without any interesting topics
  
−
<hr/>
 
−
'''July 15, 22 and 29, 2015''' -- no meeting
 
  
−
<hr/>
+
'''February 27, 2018''' - Lars, Dani, McQ, Tom, Alex
−
'''July 8, 2015''' - McQ, Dani, John, Martin, Alex
+
* JDT support for new Java releases
−
* John: '''Cross-Language Tooling Discussion''' on the eclipse.org-architecture-council and ide-dev mailing lists
+
** McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible
−
* decided to cancel the upcoming July meetings
+
** Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community
 +
* Dropping XP support
 +
** Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release
 +
** Mail to be posted to cross project by Dani to gather feedback
 +
** Alex: 1 week for gathering input on cross-project - '''AGREED'''
 +
** If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex
 +
** To be formally voted after the mail to cross-project
 +
* Release names
 +
** Version only, release names are irrelevant from Eclipse TLP side - '''AGREED'''
 +
* Inactive committers pruning
 +
** Lars: no access to committer emails so sending just to the mailing list
 +
** Wait 2 months for reply before action
 +
** McQ: ask foundation to send direct mails on behalf of the project, if foundation is not fine - remove committers directly
 +
** Alex: only public replies to the mailing list are accepted so people wanting to remain committers at least follow the mailing list
 +
* Tip of the day -
 +
** Lars: CQ approved, to be merged today/tomorrow
 +
** Alex: we should have it part of the build and part of the p2 repo for easy testing
 +
** Dani: unclear APIs to be removed and to be simplified so we don't end up maintaining useless parts
 +
* GTK 2 vs. 4
 +
** Alex: Gtk 4 release aiming at late 2018, it's big change in drawing so conflicts with Gtk 2 badly
 +
** Alex: Gtk 2 support to be removed in future one of the next 2 releases, whether Sep or Dec to be discussed later in the Photon release train
 +
** Alex: mail to cross project list around Photon M7 or RC when more information on both Gtk 4 release plans and SWT bugs will be known
 +
** McQ: what is our statement on supported Gtk version?
 +
** Alex: Statement should be: Once SWT switches to latest Gtk version as default, support for previous versions goes into deep maintenance mode but will kept until it starts hurting new development and support for the default version at which point to be removed.
 +
** To be discussed further.
  
−
<hr/>
 
−
'''July 1, 2015''' -- no meeting
 
  
−
<hr/>
+
'''February 20, 2018''' - Lars, Dani, McQ, Tom
−
'''June 24, 2015''' - McQ, Dani, Martin, Alex
+
−
* Dani: '''Java 9''' - <a href="http://marketplace.eclipse.org/content/eclipse-java%E2%84%A2-9-support-beta-mars">EAR Feature Patch</a> on the Marketplace NOW
+
−
** No JARs any more - JRE is doing things internally using "jimage" format; updated search etc to create projects and work against them
+
−
** If the Jimage filesystem provider isn't backported, one has to run the IDE on Java9 in order to code Java9
+
−
** Modules are just a list of packages (and can refer to other modules) - no real JSR describing the plan yet - seems like just a replacement of "Profiles" (and JARs)
+
  
−
<hr/>
+
* Dani: Update on 4.7 RC3
−
'''June 17, 2015''' - Dani, John, Martin, Alex
+
* Lars: Can we drop Windows XP support?
−
* John: '''Mars''' Platform in good shape for Mars - EPP respin for Error Reporting
+
** Lars: Big contribution comes in (https://bugs.eclipse.org/bugs/show_bug.cgi?id=531097), dropping XP support might be a good motiviation to contribute more also to other people. Removing lots of code including the version checks will also result in a cleaner code base for maintenance and might improve performance.
−
* Dani: '''Crashes with Java 8''' - Potentially will add to the online README
+
** Dani: IBM investigate if they officially drop XP
−
** Happens in the JIT, with latest Oracle Java 8 (with 8 Cores and very specific circumstances)
+
** Tom: Do we need support XP with the latest Eclipse version?
−
** See {{Bug|465693}} - Probably https://bugs.openjdk.java.net/browse/JDK-8078262
+
--> Pending on the answer of the IBM team, will be discussed in next weeks call
−
* Alex: '''XDG Application''' - looks like Docker but a similar idea
+
* Tom: OSGI CQs updated and approved for OSGi Service Platform 7.0 version
−
** Environment description of the runtime - helps specifying the line-up of library versions that we test against and use
+
−
** Big part of GNOME / GTK already pushing for it, might make sense to consider alignment
+
−
** GNOME working towards compiling with a really old compiler, such that the physically identical bits can run against a large set of distros
+
−
** See https://wiki.gnome.org/Projects/SandboxedApps
+
−
** But if you want to try it out please read https://blogs.gnome.org/alexl/2015/06/17/testing-rawhide-apps-using-xdg-app/
+
  
−
<hr/>
 
  
−
'''June 10, 2015''' - Dani, Alex, Martin
+
'''February 6, 2018''' - Lars, Dani, McQ
−
* Dani: 4.5RC4 looking good, no more fixes planned
+
* Lars: Can we mark MInput and MInputPart for deletion ({{bug|509868}})?
−
* Dani: Working on Java 9 feature patch
+
** Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references.
−
* Alex: PC discussing a change in the release train
+
*** McQ agrees
−
** Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
+
* Dani: [https://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00743.html Topic on ui-best-practices-working-group list]: Replace "..." with an ellipses Unicode character
−
** From Platform point of view, stability is key. Some key contributors not interested doing
+
** Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
−
** Martin: How to also cater to contributors who want their contributions released soon ?
+
−
*** Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
+
−
*** Or, open up a new "experimental" stream ?
+
−
*** Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
+
−
* Martin: Tested eclipse-installer (Oomph), looking really really good now
+
−
 
+
−
<hr/>
+
−
'''June 3, 2015''' - Alex, Dani, Martin, McQ, John
+
−
* Dani: '''Mars Endgame'''
+
−
* Dani: Please vote for release review
+
−
 
+
−
<hr/>
+
−
'''May 20, 2015''' - Dani, Alex, Martin, McQ
+
−
* Dani: '''Security Update''' - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
+
−
* Dani: '''RC2 Build''' - too many bugs assigned, Lars on Vacation, Dani will fill in
+
−
* McQ: '''Too Many Platforms Built?''' - Who's really hurt by "too many builds" ?
+
−
** Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).
+
−
 
+
−
<hr/>
+
−
'''May 13, 2015''' - McQ, John, Alex, Martin
+
−
* John, Dani - Mars Endgame looking good
+
−
* Alex - {{bug|465874}} Lucene 5 looking good, almost done - Ready to commit as soon as CQs are in and Mars+1 is open
+
−
* JDT for Java 9 - will need a wider discussion with EMO on make it easier to publish the work, e.g. in normal builds
+
−
 
+
−
<hr/>
+
−
'''May 6, 2015''' - McQ, Dani, Martin, John
+
−
* Dani: '''Java 9 timing''' - slight delay
+
−
* Dani: RC1 preps
+
−
** 2-day test pass went fine - 2 severe issues found, will be addressed
+
−
** Request to watch PMC mailing list for API exceptions and defect approvals
+
−
* John: '''PC Discussion on Release Cycles'''
+
−
** Multiple releases per year PLUS maintenance streams seems like overkill
+
−
** Consider an approach like Orion that just moves constantly forward
+
−
** Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
+
−
*** A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
+
−
*** Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
+
−
*** Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?
+
−
 
+
−
 
+
−
'''April 15, 2015''' - Dani, John, McQ, Alex, Martin
+
−
* Dani: '''Java 1.7 Changes'''
+
−
** Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
+
−
** Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
+
−
*** Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
+
−
*** Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
+
−
** Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
+
−
* Dani: '''Batik 1.6 update'''
+
−
 
+
−
<hr/>
+
−
'''April 8, 2015''' - Dani, Martin, Alex, John, McQ
+
−
* Dani: '''Batik''' - Platform is good, Train may need to update, perhaps updating one bundle only would suffice. John will follow up.
+
−
* Alex: '''SWT for GTK 3 News'''
+
−
** GTK port finally decoupled from X11 - it renders on Wayland now, can switch the renderer to a pure HTML one
+
−
** This opens up opportunities (but depends on hosts that have GTK).
+
−
 
+
−
 
+
−
<hr/>
+
−
'''April 1, 2015''' - McQ, Alex, Martin, Dani (Regrets: John travelling)
+
−
* Alex: '''GTK 3.16''' seeing issues again - fixed some crashes, but scrolling is still entirely broken
+
−
** SWT uses a number of things that GTK declares as "implementation detail"
+
−
* PMC approval on piggyback CQ's (AC question forwarded by John)
+
−
** Dani sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02332.html our position] to John in order to update the AC
+
−
 
+
−
<hr/>
+
−
'''March 18, 2015''' - Dani, Alex, Martin, McQ, John
+
−
* John: '''EclipseCon''' - Bigger this year due to LocationTech (750 attendees)
+
−
** Mark Reinhold keynote and "after-session" on Java 9
+
−
** Much interest in Orion JS tooling / editor, also on desktop
+
−
** Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
+
−
* Dani: {{bug|458730}} '''Mars Plan Update'''
+
−
* Dani: '''e4 project leadership''' approved by EMO
+
−
* Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list
+
−
 
+
−
<hr/>
+
−
 
+
−
'''March 11, 2015 - no meeting (EclipseCon)'''
+
−
 
+
−
<hr/>
+
−
 
+
−
'''March 4, 2015''' - Dani, McQ, Martin, John
+
−
* Dani: '''e4 leadership''' - Dani will volunteer to co-lead
+
−
* Dani: '''BREEs''' - documentation about how to pick the EE
+
−
** Recommending the "earliest generally supported JRE that provides the capabilities you need"
+
−
** Would like an URL on the page pointing to the most recent plan (talking to Wayne)
+
−
* John: '''greatfix contest'''
+
−
** Dani: Working well - some very small contributions but some also very large (eg Customize Perspective fixes)
+
−
* John: '''EclipseCon''' - numbers looking good; join Planning Council Breakfast as delegate for Dani
+
−
 
+
−
<hr/>
+
−
'''February 25, 2015''' - Dani, Martin McQ
+
−
* No topics
+
−
 
+
−
<hr/>
+
−
'''February 18, 2015''' - Dani, Alex, Martin
+
−
* Alex: '''Building Native Launchers'''
+
−
** Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
+
−
** Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
+
−
** Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
+
−
* Dani: Great initiative, but other (non-EF) builders must not be broken
+
−
** EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
+
−
* Alex is willing to spend time to get Linux builds running; but can't help with other architectures
+
−
** Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
+
−
* Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
+
−
** Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
+
−
** Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
+
−
 
+
−
* Alex: '''{{bug|459399}} - Policy for recommended minimum execution environments for bundles'''
+
−
** Dani: It works today
+
−
*** To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
+
−
*** To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
+
−
** Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
+
−
*** But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
+
−
*** Suggested BREE for new bundles has already been changed by Lars
+
−
* Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
+
−
* No conclusion so far (Alex and Dani disagree)
+
−
 
+
−
* Dani: '''e4 leadership'''
+
−
** Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier
+
−
 
+
−
<hr/>
+
−
'''February 11, 2015''' - Dani, Alex
+
−
* no topics
+
−
 
+
−
<hr/>
+
−
 
+
−
'''February 4, 2015''' - Dani, Alex, Martin
+
−
* Alex: With GTK-3.15.[345] , Eclipse is entirely unusable
+
−
** Alex has some dirty workarounds to make it start, but still many issues like trees not painted, ...
+
−
** Crash on startup identified to be GTK bug. Fix to be released in 3.15.6 https://git.gnome.org/browse/gtk+/commit/?id=edec64cda3d4518b4e87d5ea5d287d4570ba9933
+
−
* Dani: Working on Solaris 64-bit
+
−
 
+
−
<hr/>
+
−
 
+
−
'''January 28, 2015''' - Dani, Alex, John
+
−
* Dani: Switch Mac OS X 10.9 with 10.10 in Mars target environments
+
−
** No objections
+
−
* Alex: Looking for any Eclipse related activity @Fosdem
+
−
<hr/>
+
−
 
+
−
'''January 21, 2015''' - Dani, Alex, Martin, McQ
+
−
* Alex: '''Process for allowing non-committers extended bugzilla privileges (for bug triage)?'''
+
−
** Dani: Yes a process exists. Send bugzilla username to Dani.
+
−
* Alex: '''New resource for helping with SWT'''
+
−
* Dani: '''Platform/UI co-lead'''
+
−
* Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --&gt; IBM SWT Team considering to invest in getting patches in for 64-bit Solaris
+
−
 
+
−
<hr/>
+
−
'''January 14, 2015''' - Dani, Alex, Martin, McQ, John
+
−
* Dani: Update on Platform/UI Leadership: Daniel Rolka left IBM and for now has no time to contribute. He stepped down as co-lead and nominated Lars Vogel
+
−
* Dani: Solaris x86 64-bit support - patches exist, but no machine available. No luck to get one from Oracle or via Eclipse Foundation. We will not support Solaris x86 64-bit unless someone makes a machine available
+
−
<hr/>
+
−
 
+
−
'''January 7, 2015''' - Dani, Alex, Martin, McQ, John
+
−
* Dani: '''Platform/UI Leadership'''
+
−
* John: '''Git security issue''' - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP
+
−
<hr/>
+
−
 
+
−
'''December 17, 2014''' - McQ, John, Dani
+
−
* Platform UI leadership to be discussed in the next PMC call
+
−
* no call on December 24 and December 31
+
−
 
+
−
<hr/>
+
−
'''December 10, 2014''' - Alex, McQ, John, Dani, Martin
+
−
* Dani: {{bug|427768}} Mickael (Red Hat) - Nested Project support contribution to Common Navigator to better support Maven projects
+
−
* Dani: Red Hat also will wants to contribute making the Import easier {{bug|421930}}. First in the e4 incubator.
+
−
** Just import from a folder, and contribute project configurators via extension point (e.g. detect POM files, Makefiles, ...)
+
−
** McQ: Many complexities ... different users may want very different things to happen
+
−
*** McQ: Just point to a Git repo -- the Git repo has a little metadata file at the root which allows launching the apps that the repo had been intended for ... maybe just make the project tree(s) a little more self-describing
+
−
*** Is there a growing list of repos which already have that? - John: In the Java world, pom.xml is getting that ...  
+
−
*** Alex: .doap getting this (at least for Apache and GNOME projects - specifies at least the languages used)
+
−
* Web IDEs : McQ and others gone through a lot of analysis of Web IDE's
+
−
** Cloud9 has a much larger set of starting points ; in terms of the underlying core structure, Orion (and also Jay) are more interesting
+
−
** Orion has an extremely lightweight plug-in model: pieces coming from all over the world may look like all running on the server - nice infrastructure for building Community around it
+
−
** Orion + Flux could be a rival for anything out there
+
−
** Orion continues to push on the Core Coding experience - Orion Editor is on par or better than most desktop editors
+
−
* Vision: See [https://dev.eclipse.org/mhonarc/lists/platform-vision/msg00065.html Minutes on the platform-vision mailing list] ... Delivery will depend on people actually participating
+
−
 
+
−
<hr/>
+
−
'''December 3, 2014''' - Alex, Martin, Dani, John (McQ travelling)
+
−
* John: [https://dev.eclipse.org/mhonarc/lists/platform-vision/ Platform Vision] - How to turn that into actionable items, Wayne wants to present to the Board
+
−
* John: '''Performance tests''' running again since a couple weeks, now the graphs are also back again :)
+
−
** See http://download.eclipse.org/eclipse/downloads/drops4/I20141202-0800/performance.php
+
−
** Results are there but fingerprints currently missing
+
−
** Baseline is 4.4.0 at the moment (consider comparing against 3.x at some point)
+
−
** John: From experience, a single result isn't helpful, there's often weird anomalies from build to build ... need to look at trends over multiple builds, thus the graphs are really useful
+
−
 
+
−
<hr/>
+
−
'''November 26, 2014''' - Alex, Dani
+
−
* No relevant topics / decisions
+
−
 
+
−
<hr/>
+
−
'''November 19, 2014''' - Alex, Martin, Dani  (''McQ and John had issues dialing in'')
+
−
* Dani: '''Jetty 9''' - Upgrade has been done, but new versions coming out ... will probably update from Jetty 9.2.3 to Jetty 9.2.5. Probably 9.3
+
−
** WTP interested in newer Jetty version ... need to agree on a common version across the Release Train.
+
−
** Alex: New Jetty JSP compiler failing ... filed a bug, will want this fixed (Jetty working on it)
+
−
* Dani: '''{{bug|179924}} Request for ssh-agent''' - patch against Team from YMNK (JSch Committer)
+
−
** egit would contribute the agent, but would make more sense putting it in Platform (+1 from Martin, no objection from Alex)
+
−
* Equinox Declarative Services implementation - ProSyst stopped providing fixes, not responsive any more
+
−
** New specificiation (R6) from OSGi adding lot of features, cannot risk staying behind
+
−
** Suggestion to remove the ProSyst stuff and replace it with the Apache Felix implementation (used by IBM / WebSphere and others)
+
−
** Martin: How mature / stable is the Felix code ? Can we influence it ?
+
−
*** Dani: Very mature. Have more influence on Felix than on the Prosyst stuff ... through the IBM committers and others.
+
−
*** Alex agrees. Using some parts of Felix already.
+
−
* John (via Dani): '''Move e4 into Platform/UI''' - would like to start the review process next week.
+
−
 
+
−
<hr/>
+
−
'''November 5, 2014''' - McQ, Dani, Alex, Martin
+
−
* Eclipse Foundation greatbugs initiative - call into PMC
+
−
* Dani: EclipseCon Europe Report - met lot of people, best attended EclipseCon Europe ever :)
+
−
** IOT; IDE in the Web; are people moving away from Eclipse before the transition to Web can be completed ?
+
−
* Alex: Discussion with Christian Campo on scaling up
+
−
** Should better go into SWT ... but SWT has a reputation that it's hard getting a change in -- people prefer re-doing things their own than contributing :(
+
−
** Alex thinks this problem doesn't exist any more ... but how to fight this misconception ?
+
−
** John: Getting a change in may now be hard due to other reasons, eg lack of experienced committers
+
−
** Alex: Consider voting in new committers more easily if somebody is interested ?
+
−
* Alex: Difference between Eclipse and the Linux Foundation
+
−
** Linux Foundation doesn't provide anything that anybody can use directly (just a source tarball) --&gt; all users become "contributors" of some sort
+
−
** This leads to different expectations and has a number advantages (eg issues are reported to and worked on by member companies only)
+
−
 
+
−
'''October 22, 2014''' - Alex, Dani, McQ, John
+
−
* Platform plan update nearly done, will be released soon
+
−
* Orion release review is ongoing, release will be next week
+
−
* Brief discussion of new bug reporting tool and related bug [https://dev.eclipse.org/recommenders/committers/dashboard/#/dashboard/temp/e6leTB3gQy-zUZI-73KtRQ dashboard]
+
−
* PMC called '''canceled''' next week due to EclipseCon Europe
+
−
 
+
−
'''October 1, 2014''' - Alex, Dani, Martin, McQ
+
−
* Dani - In touch with Oracle regarding Solaris x86
+
−
* McQ - '''Platform UI''' tension between making Platform UI as stable as possible, versus new features
+
−
** Community forming for new contributions - that's great! - But takes committer's time; committers reduced to "productize and fix" is problematic
+
−
** how to get more contributions for bug fixes ?
+
−
*** Alex: What about saying "This release we only accept bug fixes" ? Or for some milestone, eg after M4 only accept bug fixes ?
+
−
*** Dani: Sounds great, but will the Community accept that ? - JDT BugBash did not work that well...
+
−
*** Dani to prepare a draft message
+
−
* Dani was in Bangalore - talked to Arun - good collaboration with Alex
+
−
** Hard to get new SWT developers (Sami moving away on RH side)
+
−
** Ideas to keep SWT relevant ... eg generate Browser based things
+
−
*** GTK3 supports running in a browser now... (just one label for now, but an interesting approach)
+
−
 
+
−
<hr/>
+
−
'''September 24, 2014''' - Alex, Dani, McQ, John, Martin
+
−
* John: '''SWT Binaries Repository''' has got too big
+
−
** Will prune old versions out of the git repository (which is only used internally) - "Release" drops will still be available from release builds.
+
−
** '''DECISION:''' OK to prune.
+
−
* '''SWT master still has sources for old Platforms''' like carbon and motif - cluttering up the source code
+
−
** '''DECISION:''' OK to remove references - source would remain in git for old branches, but not be visible in master any more.
+
−
* Dani: '''p2 and Equinox''' - no sign-off for M2, leaders stepping down ?
+
−
** consider moving p2 back into Equinox, and probably Equinox back into the Eclipse project ?
+
−
** John: Equinox committers not really knowledgeable about p2 ... still, with less than 3 active committers a threshold is reached (can't hold elections any more)
+
−
** Still there's a couple of people contributing, so there are knowledgeable folk around
+
−
** Dani: If there's committers committing code, they should also be responsible for sign-off
+
−
* Dani: '''Java 7 and Jetty 9'''
+
−
** Been using Jetty 8 for a while, now, there is Community Pressure upgrading to Jetty 9 but that requires Java 7
+
−
** Java 6 no longer getting public updates since February 2013
+
−
** John:Adoptions needed in the Help System when moving to Jetty 9 ?
+
−
*** Alex don't think so - been shipping Jetty 9 for over a year already; only required changing some dependencies.
+
−
*** '''ACTION ITEM: Alex offered to check this'''
+
−
* Alex: '''Drop all the Java 6 Platforms from the list of Reference Platforms?'''
+
−
** '''DECISION:''' Yes this needs to be done. Trying to support Java 6 won't buy any benefit at this point.
+
−
 
+
−
<hr/>
+
−
'''September 17, 2014''' - no meeting
+
−
 
+
−
<hr/>
+
−
'''September 10, 2014''' - John, Martin, Alex, Dani
+
−
* John: Mars having some build hickups due to removing Mac 32-bit builds
+
−
* John: Luna SR1 - almost done, respinning for 2 bugs in Equinox
+
−
* John: Cloud TLP (for Orion and others) - still on track for announcing end October
+
−
* Alex: Been busy with other stuff recently, back on the GTK version support discussion this week
+
−
** Martin: Many people will know what distro they have (or need), but not what GTK they have on there
+
−
*** John: Also running GTK on AIX, Solaris, Linux Power and other which are not moving up that fast...
+
−
*** Martin: Examples: RHEL 5.8 was GTK 2.10.4-21 ; RHEL 4.5 was at GTK 2.4.13-22
+
−
*** Popular distros would be Ubuntu LTS, RHEL, OpenSUSE
+
−
** Alex: Newer distros have up to 3 GTK versions installed, along with some means to switch between them, it's very confusing
+
−
** Eclipse is the only project that dynamically loads DLL's and tries to support a broad range ... others typically compile against a specific version
+
−
*** Most projects require GTK 2.24
+
−
** John: GTK versions are not really predictable ... between 3.04 and 3.10 there was a breaking change
+
−
** Alex: In every release there are small issues that we work around; and there's certain releases that are breaking stuff
+
−
** '''NEXT ACTION: Send E-Mail'''
+
−
 
+
−
<hr/>
+
−
'''September 3, 2014''' - John, Alex, Dani
+
−
* Dani: away next week and on/off the next two weeks due to travel
+
−
* Dani: RC4 next week. PMC please watch the PMC mailing list
+
−
** John: will be available and monitor the mailing list
+
−
* Dani: Oracle interested in providing access to a Solaris 64-bit machine {{bug|442266}}
+
−
* John: How/where to graduate the e4 tools
+
−
** the community wants to graduate this out of incubation
+
−
** initially proposed to create a separate project, but feels like adding too much overhead
+
−
** John: proposed PDE as home, then Dani suggested to use Platform UI
+
−
** Alex, Dani and John agree to suggest Platform UI as home for the e4 tools.
+
−
** John to send a note to Lars
+
−
* Alex: Limit supported number of GTK+ versions
+
−
** SWT currently has to support over 20 different version. This doesn't scale.
+
−
** Proposal: Bump min supported version with one minor release each release. Aka Luna has Gtk 2.10 as min, Mars would have 2.12 as min. Can consider even two minor releases (Mars requires 2.14) as this would keep the amount of supported versions the same as GTK releases one minor release every 6 months.
+
−
** Dani, John: this is too limiting. We tended to support the most possible. Newest versions might have too many bugs.
+
−
** All agree: we'd like to limit the amount of supported versions
+
−
** Alex to cast a poll via Eclipse Foundation, which versions are used by users and companies
+
−
 
+
−
<hr/>
+
−
 
+
−
'''August 27, 2014''' - cancelled
+
−
 
+
−
<hr/>
+
−
 
+
−
'''August 20, 2014''' - John, Alex, Dani
+
−
* Dani: new platform PowerPC 64-bit LE {{bug|441358 }}
+
−
** maintained by IBM
+
−
** will be added to 4.4.1 as early access
+
−
** Dani to send a note to cross-platform
+
−
* Dani: individual made patches to support Solaris 64-bit {{bug|442266}}
+
−
** we'd like to add it but don't have a machine to support it
+
−
** important because our current 32-bit Solaris build will become obselete since there's no 32-bit JRE for Java 7 and beyond
+
−
** Oracle should be interested since they provide both, Java and Solaris
+
−
** Dani to ask Oracle
+
−
 
+
−
<hr/>
+
−
 
+
−
'''August 13, 2014''' - McQ, Alex, Dani
+
−
* Dani: Any feedback for the [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_5.xml Mars plan]?
+
 
** McQ:
 
** McQ:
−
*** It does not cover Orion, but that is OK and like in previous release plans. Orion will most likely be moved to another top-level project soon.
+
*** Mac OS UI guidelines specify to use the ellipses character
−
*** We want to remove Mac OS X Universal 32-bit (all agreed)
+
*** SWT could do the right thing depending on the platform
−
* Dani: How to deal with requests to push our bundles to repo.eclipse.org {{bug|441530}}
+
* Lars: view menu, minimize and maximize buttons look bad to him. Would like to replace the view menu with ellipses
−
** Dani: OK for me but we won't do the work
+
** Dani: Would have to change all three together. View menu is always there and not indicating an overflow
−
** Alex: Maven needs the dependencies in the pom.xml. We don't want copy them from the manifest into the pom.xml and then maintain this. The pom should be updated when publishing the file into the Maven repo. Ideally by an automated task.
+
** McQ: Windows 10 also uses a triangle, but upwards. Current view menu is used and familiar to users for at least more than 10 years.
−
** Conclusion: all agree with this, i.e. we won't do the actual work and we won't "pollute" our pom files.
+
** Lars to file a bug report and send the bug number to the PMC
−
 
+
* McQ: Should discuss in one of the next meetings how JDT can handle the new release cadence for Java
−
<hr/>
+
** Dani: We will see how it goes with Java 11 (18.3)
−
'''August 6, 2014''' - McQ, Dani
+
* Dani: How will we name the milestones in our new new release scheme?
−
* Dani: Will provide initial Mars plan next week
+
** Consensus to start with M1 after each release.
−
 
+
** Up to planning council to decide the release naming convention. Lars: Would prefer year/month
−
 
+
−
<hr/>
+
−
'''No meetings in July'''
+
−
 
+
−
 
+
−
<hr/>
+
−
'''Jun 4, 2014''' - Dani, John, Martin, McQ, Alex
+
−
* Dani: '''RC4 Status''' looking good
+
−
** 1 bug in JDT, 1 bug in Debug and 1 in Platform/UI on Linux being investigated ("Show In" no longer working)
+
−
** Rest of the team working on docs
+
−
** Alex: On Ubuntu, might want to disable UBUNTU_MENUPROXY ... this is causing a lot of issues
+
−
* John: '''Went over the N&N''' ... number of things went in after M7 :)
+
−
** Dark Theme - Good story in place combining the old 3.x Presentation API with the new E4 (CSS) technology in a good way
+
−
 
+
−
 
+
−
<hr/>
+
−
'''Jun 11, 2014''' - Martin, McQ, Alex, John
+
−
* John: Eclipse Theming: When switching the OS Theme to dark, Eclipse should be aware
+
−
** Dark Theme is currently a tech preview
+
−
 
+
−
 
+
−
<hr/>
+
−
'''Jun 4, 2014''' - Dani, John, Martin, McQ, Alex
+
−
* Dani: '''RC4 Status''' looking good
+
−
** 1 bug in JDT, 1 bug in Debug and 1 in Platform/UI on Linux being investigated ("Show In" no longer working)
+
−
** Rest of the team working on docs
+
−
** Alex: On Ubuntu, might want to disable UBUNTU_MENUPROXY ... this is causing a lot of issues
+
−
* John: '''Went over the N&N''' ... number of things went in after M7 :)
+
−
** Dark Theme - Good story in place combining the old 3.x Presentation API with the new E4 (CSS) technology in a good way
+
−
 
+
−
 
+
−
<hr/>
+
−
'''May 28, 2014''' - Dani, Alex, Martin
+
−
* Dani: '''EOL'ing the Delta Pack''' - announce now, remove during Mars - it's been obsoleted by p2 functionality
+
−
** Alex: Some of the test suite relied on the delta pack, it caused issues, OK with removing (PDE tests would need to be cleaned up)
+
−
* Dani: '''Copyright Updates''' - tool is very slow since not ported from CVS properly, can run for hours
+
−
** John: Worth doing periodically but probably won't matter legally since copyright lasts for 7 years
+
−
** The change is not without risk (Dani: Could schedule after the release)
+
−
** McQ: Should consider updating the tool as part of that work
+
−
** Alex: Has a new intern, could use this as an opportunity to join
+
−
* Dani: '''RC3 status''' - last planned build - looking good, except for Platform UI, where the list of bugs is still long
+
−
* McQ: Discussions about a new Eclipse.org Web-based Toplevel Project
+
−
 
+
−
 
+
−
<hr/>
+
−
'''May 14, 2014''' - Dani, Alex, John, Martin
+
−
* Alex: SWT GTK3 and the Endgame Rules
+
−
* Dani: Luna Plan Update
+
−
* John: New Dashboard created by the EMO
+
−
 
+
−
<hr/>
+
−
'''May 7, 2014''' - McQ, Dani, Alex, John, Martin
+
−
* Martin {{bug|241957}} - GTK clipboard hang
+
−
** Alex: GTK guys recommended using the async API, but no time for more investigation
+
−
** McQ: Switching a sync API to async implementation underneath can be extremely messy (need to be aware of all possible events and event sources...)
+
−
** McQ: If there is an idea canceling the clipboard wait ... given that the issue occurs only rarely, even a hacky solution is better than nothing
+
−
* Dani: will do a plan update, hopefully this week
+
−
 
+
−
<hr/>
+
−
'''April 30, 2014''' - Dani, Martin, McQ
+
−
* McQ: '''WB4 perspective customization''' - has it caused any issues ?
+
−
** Martin: Dealing with detached views works differently (dragging a window fails - must drag the tab inside the window)
+
−
** Dani: Saved perspectives / windows are lost on an existing workspace when moving from 3.x to 4.x
+
−
*** Martin/McQ: When crossing the major version boundary, it is OK to lose state - it's not nice but acceptable
+
−
** Dani: The bigger problem is, that the whole "Perspective customization" dialog is still not working as expected
+
−
*** Martin: Agree with the concern, but the Perspective customization dialog wasn't ever great
+
−
*** McQ: If invest work here, rather make it good than bring back the previous status quo
+
−
*** Martin: Most customization done via plugin.xml / Java , don't expect end users to do a lot of customization themselves
+
−
* Dani: '''M7 status'''
+
−
** Defect triage under control - some items deferred to 4.5
+
−
 
+
−
 
+
−
<hr/>
+
−
'''April 23, 2014''' - McQ, Dani, John, Alex, Martin
+
−
* Alex - GTK2 or GTK3 as default - GTK3 it is
+
−
** GTK2 - more stable on old systems but no usable browser due to
+
−
*** xulrunner - latest version not supported by swt and latest distros don't even ship standalone xulrunner
+
−
*** webkitgtk - gtk2 version in maintenance mode, upstream consider dropping, really crashy See [https://lists.webkit.org/pipermail/webkit-gtk/2014-March/001821.html]
+
−
** GTK3 still has some drawing issues (fighting them one by one, but functionally everything is there)
+
−
** McQ: If neither state is really good, need to choose the option that's moving forward (switch to GTK3)
+
−
* Dani - '''Freeze Plan created'''
+
−
* John - '''Hackathon in London proposed by Ian Skerret'''
+
−
*
+
−
 
+
−
<hr/>
+
−
'''April 16, 2014''' - Dani, Alex
+
−
* no topics today
+
−
 
+
−
<hr/>
+
−
'''April 9, 2014''' - Dani, Martin, Alex
+
−
* Dani - '''Kepler SR2 and Java 8'''
+
−
** Planning Council: Can build and host the patches, but messaging must be clear as "SR2 with the patches applied". Still polishing words of the download pages.
+
−
** Not added to aggregate repo ... one-time package without any updates
+
−
** Feature patch available on Marketplace (for manual update) - for those starting from scratch they can now get "Kepler + Patch"
+
−
** Not convinced that the extra downloads were necessary (early adopters already had the patch, new adopters can also get Luna) ... but current approach won't hurt.
+
−
 
+
−
* John - '''Hard to review all incoming Platform/UI Contributions'''
+
−
** Dani tried to jump in on some issues like Icons
+
−
** Doubt that some of the work will really help bringing committers on board (such as the for loop conversion)
+
−
** Some of the initial contributors of very simple things have now grown into contributing real interesting things
+
−
** Getting more people involved in initial reviews (currently some 10 active committers, 4-5 fullday ones) - but mainly Eric and Paul review patches
+
−
 
+
−
<hr/>
+
−
 
+
−
'''April 2, 2014''' - Dani, Alex, John, Martin
+
−
* Dani - new GTK3+ issues
+
−
** crash/hang when SWT AWT bridge is used, also affects JavaFX ({{bug|431330}})
+
−
** problems with main menu ({{bug|419830}})
+
−
* Dani - '''Submitting the IP Log for the Java 8 Work'''
+
−
** Currently not qualified as a "release", only submitting the IP log.
+
−
* Dani - need to '''approve API changes for Java 8 in M7'''
+
−
** No API changes, only additions
+
−
** Used / tested by JDT Core / JDT UI
+
−
** ObjectTeams (Stephan Herrmann) was involved
+
−
** There were no objections i.e. changes were approved
+
−
* John - '''SWT over JavaFX'''
+
−
** EclipseCon: Steve Northover thought it was possible, just a lot of work
+
−
** Decide after Luna whether hosting in SWT or doing as a separate project
+
−
** Relationship to Tom Schindl's [http://www.eclipse.org/efxclipse/index.html e(fx)clipse project] ?
+
−
*** e(fx)clipse is more about tooling, not so much about rendering ...
+
−
*** Tom seems to have an alpha version, but not actively working on it
+
−
*** Seem to need some additional API in SWT - patch sits in Gerrit with nobody putting any attention at the moment. Details in {{bug|426243}}
+
−
*** Having this API in place would make the JavaFX port simpler
+
−
**** It look good but Alex has no idea whether it's the best idea and how acceptable on all platforms
+
−
**** John: May make sense in the next release, API can't be a near-term thing ... needs some backers who can invest significant time in it
+
−
*** Doug Schaefer is also pushing for JavaFX
+
−
 
+
−
 
+
−
<hr/>
+
−
'''March 26, 2014''' - John, Dani, Martin, Alex
+
−
* John - '''EclipseCon Update'''
+
−
** Slightly smaller than in the past, but VERY of positive attitude, LOT of excitement around Java 8 ... Oracle turned on the servers during one of the morning sessions
+
−
** IoT / M2M - lots of demos on Raspberry Pi, many new projects
+
−
** Very good content around Orion and Javascript, but a small crowd
+
−
** Great opening keynote from Mike Milinkovich on the history and future of Eclipse - mentioned Flux
+
−
** See also Blog Posts from [http://cdtdoug.ca/ Doug Schaefer] and [http://eclipsesource.com/blogs/author/irbull/ Ian Bull] as well as [https://www.eclipsecon.org/na2014/news/top-5-ian-bull top 5 from Ian]
+
−
* John - '''ARM port of GTK''' - any tracking items ?
+
−
** Bug exists for Launchers on ARM64 ; several other items too
+
−
** IBM PPC Little Endian port of SWT
+
−
** Test on less used architectures like Solaris? - similar to the Windows 8 case...
+
−
** Donating RHEL subscriptions to the Foundation was not accepted - John: Bug is open for having Hudson slaves run on other architectures
+
−
*** Example: {{bug|430698}}, {{bug|429237}}, {{bug|415757}}; {{bug|419855}} talks about running virtualbox images on a vserver
+
−
*** Denis is investigating some way running Hudson / HIPP instances on other hardware ... GTK3, Windows etc tests need other hardware
+
−
*** Check for cost of hardware, companies to donate it, and people to maintain it (Security patches!)
+
−
**** Alex could imagine RH signing up for some maintenance ... test machines could be entirely outside Eclipse.org infrastructure, isolated as their own sandbox
+
−
**** Hudson needs access though, thus need to be careful about security
+
−
* Alex - '''Java 8 vs Java 7''' currently can't build an Eclipse SDK when the build machine has only one of the JDK's
+
−
** In the past, it was possible to build with only Java 7 ... now, if I have Java 8 I cannot build (need Java 7 too)
+
−
** ==> Update on March 27 by Dani: this is {{bug|390889}} and we'll try to fix it for M7.
+
−
 
+
−
<hr/>
+
−
'''March 19, 2014''' - Dani, Alex, Martin, McQ
+
−
* McQ - '''Congrats on Java 8 Release''' to coincide with the Oracle release
+
−
* Dani - '''Windows 8 Support''' - any answer to John's E-Mail ?
+
−
** McQ struggles with calling it a supported platform when nobody tests it; all we need to make sure is that somebody uses it
+
−
** Send note to Wayne, the epp-dev list and cross-project
+
−
** Make it clear that running on Win8 is a useful contribution ... and we WON't put Win8 on supported platforms list if we don't get that confirmation
+
−
 
+
−
<hr/>
+
−
'''March 12, 2014''' - Alex, Martin, McQ, John
+
−
* GTK - SWT team discussions
+
−
* John - '''preparing for Java 8 release'''
+
−
 
+
−
<hr/>
+
−
'''March 5, 2014''' - John, Dani, Martin, Alex
+
−
* Dani: '''How to Avoid Spam in Gerrit''' - Bug in Bugzilla PMC bucket - consider offline
+
−
* Dani: '''Windows 8 Support'''
+
−
** Not listed in official plan
+
−
** No technical problem, but lack of resources - only 1 machine on the IBM team and that's a VM
+
−
** Add as supported Platform for Luna, or wait another year ?
+
−
** Most active development is on Linux and Windows 7 these days... agree with Dani that only active developer use helps finding real issues
+
−
** AI John: Send a note to eclipse-dev
+
−
*** Reaching out to Community to find an active user would be sufficient ... WPF or Win32 ? WPF is only a runtime target environment as of today.
+
−
* Dani: '''State of GTK 3+'''
+
−
** Not yet fixed on Eclipse side, but GTK found a bug on their side that is going to be fixed; not yet sure though if that will fix everything
+
−
** Launcher now has a fallback to GTK2 if it detects the partially supported GTK3 version
+
−
** Good collaboration after an initial warm-up phase ... Eclipse SWT considered an important-enough client to make fixes for
+
−
** Alex: Concerned about users with a GTK 3.8 distro that update to GTK 3.10 and get the fallback to GTK 2 activated which has crashes with autocomplete in the browser
+
−
** On GTK 3.9 or newer, Launcher falls back to GTK 2 but that port is pretty much unmaintained, several other problems in there ... but not falling back is even worse
+
−
** Should be fine once distros start picking up paint / clipping issue fix (the not-drawing fix is still pending on SWT side)
+
−
* Alex: '''GTK 3 in Mars'''
+
−
** Bump minimum required version to only use cairo and get rid of older calls - this causes confusion with GTK folk
+
−
** RHEL 5 would no longer work
+
−
** Thanks to SWT now requiring Java 1.5, can simplify the code wrt JNI
+
−
 
+
−
<hr/>
+
−
'''February 26, 2014''' - Alex, John, Martin, McQ
+
−
* John: '''Orion Release''' this week
+
  
−
* Alex: '''Eclipse on ARM64'''
 
−
** Launcher and swt at first
 
−
** Had ports for other architectures in source form in the past, risk to get stale but helps getting the ball rolling
 
−
** John: Quite a lot steps to make a new Platform real - constants in OSGi, ... - but can happen piecemeal eg only do SWT first
 
−
*** Martin: Would make sense to document the required steps for adding a new Platform while doing the job
 
−
*** At least, write up the TODO list - in order to make it easier the next time
 
−
** Should ask Tom Watson about OSGi constants
 
  
−
* Dani: Update on '''GTK 3+ issue''' - bug filed against GTK, working on a workaround for fallback but not yet finished
+
'''January 30, 2018''' - Alex, Lars, Dani, Tom
−
** Alex: Fix in GTK3 alone wouldn't work because SWT overrides GTK in that part
+
* General Updates (Dani)
−
** McQ: If SWT API can't be implemented on top of new GTK API any more, discussion needs to happen
+
** Shipped M5, still working some p2 issues
−
*** If SWT does something wrong, would need pointers to what they should be doing instead...
+
** RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates
−
*** Maybe a couple phone calls to talk through the technical details
+
** Discussion about the incubation for Java.  Ongoing thread in jdt-dev list https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00964.html.  The incubation features will be part of the release specification which implies they need to be implemented to be compliant.  Spend time putting them into a release only to pull out later if they don’t finalize.  Not clear there are tests added to the TCK.  Alex asks if this effects us for Java 10, no not for Java 10.  Java 10 only has local type reference, not huge delta of function from Java 9.  No incubation in Java 10.  But incubation may affect us for Java 11.
−
*** Don't fight over things ... figure out what's the right thing to do, and just do it  
+
* Info about infrastructure (Alex)
 +
** Foundation push to move to Jenkins.  Releng has moved, uncovered issues with rest API and token exchange … disabled for now for Jenkins.  Issue is being worked but only can be fixed once all is moved to Jenkins.
 +
** Platform HIPP moving to Jenkins tomorrow.  Will be some downtime, should be less than an hour or so.  May cause several issue.  Issues in non-standard jobs with multiple repos etc.  For Gerrit verifications should be fine.  Let Alex know if there are issues.  Alex to send a note when the migration occurs.
 +
** p2 issue is real.  Other issues are pressing (infrastucture/build).  Todor has a bug that he should be looking at. Not something happening in the past, but now the capabilities are being resolved. Issues happened with a hand crafted p2.inf file.  Hopefully will scope down the p2.inf files.  Alex to drive to determine if a respin is needed.
 +
** Need to monitor the p2 issue, determine how many are broken.  Cannot just break 100s of folks without serious consideration.  Why not revert?  Alex says it is not an option and we should do everything possible to fix.
 +
** Lars asks about nominating more committers, perhaps that were rejected in the past.  Now the Eclipse PMC can overlook the nomination process.  Work with existing contributors showing interest and look for opportunities to sponsor them for committership.
 +
* Tip of the day (Clippy)
 +
** See [https://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg08006.html Tips Framework]
 +
** Tip of the Day or (Clippy) in coming contribution … looking for integration M6?
 +
** Lars thinks it is worth it.  Dani disables such things by default, and also Lars. Alex find the function interesting. Others are also reviewing the patch. 
 +
** Lars is moving forward with it.  If it is very easy to disable and is stable on all platforms then it should be good.
 +
** Is there a concern about a solution that requires network … it doesn’t appear to be a concern.
  
  
−
<hr/>
+
'''January 16, 2018''' - Alex, Lars, Dani, Tom
−
'''February 19, 2014''' - Dani, Alex, Martin, John
+
* Native builds at eclipse.org status (Lars):
−
* Dani: '''Silenio to work on GTK issue?'''
+
** Dani: swt is done for some time already
−
* John: '''GTK testing at the Eclipse Foundation'''
+
** Dani: launchers after M5 is released to prevent breakage
−
* John: '''e4 ML discussion about graduating some tools'''
+
* GTK launcher changes (Alex):
−
** Model Editor, CSS Editor, CSS Spy, ...
+
** Changes to not rely on X11 atoms but on dbus ready for review
−
** Fairly late, but risk is rather low -- suggest putting into PDE
+
** Linux only as no other GTK platforms are currently built
−
** Dani concerns: No PDE committers available for handholding - and stuff is not polished; even Lars sees it in Luna+1
+
* Equinox CQs (Tom):
−
** John: These tools would only be used by people building RCP apps
+
** P2 capabilities patch from Todor and felix.scr update
−
** Martin: What is the goal of trying to graduate?
+
** Slow process risking M5
−
*** If it's just about getting more exposure, perhaps keep in incubation and add to the RCP EPP Package ?
+
** Alex: Ping Sharon asking for speedup if possible
−
** Alex would like adding new people / interested contributors to PDE
+
* Updates from Dani:
 +
** Photon plan update - BREE to be part of the build info
 +
** End game - Oxygen.3 and M5 - send to the list
 +
** Running tests against Java 9
 +
* Java 10 eclipse release (Dani):
 +
** Oxygen.3a or marketplace feature only - Agreement for oxygen.3a
 +
** Dani: Local Variable type inference support in a branch
 +
** Future releases - to be aligned with JVM releases if they prove to release on time
 +
* BREE updates recomendations
 +
** Dani: There are reasons to stay on older BREE
 +
** Alex: ease of getting jvm is the main concern here - if a contributor can't get jvm at that version easily we can't call it supported
  
−
<hr/>
 
−
'''February 5, 2014''' - McQ, Dani, Martin, Alex
 
−
* Dani: '''Confcall Numbers:''' Skype into the US tollfree; Alex use SIP
 
−
* Martin: Eclipse 4 vs Eclipse 3.x - will file defects
 
−
* Alex: Testing on modern Linux
 
  
−
<hr/>
+
'''Januar 09, 2018''' - McQ, Alex, Lars, Dani
−
'''January 22, 2014''' - John, Dani, Alex, Martin
+
* Updates from Dani:
−
* John, Alex: '''New GTK 3.10 breaking Eclipse on latest Fedora'''
+
** Ian Skerrett is leaving the Eclipse foundation
−
** Alex been looking at Browser
+
** Dani got nominated as committer representive
−
** Some Views not showing up - Silenio just back yesterday
+
* Planning council update
−
** Dani: For 4.4m5 and 4.3.2, will document issues in the README
+
** Dani: low participation in the last calls
−
*** Considered a fallback to "gtk2" support in the Launcher, but that was considered too risky
+
** Dani will talk with Melanie about it
−
*** Silenio might have a workaround ... OK if the new code can be added conditionally for GTK 3.10 only
+
** Input  required for the planning council for the API and feature freezes for the platform
−
* Dani: '''M5 Status'''
+
* API and feature freeze policy in platform
−
** Still many open bugs not triaged - component leads should triage earlier
+
*** Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build
 +
*** everyone agrees to Alex suggestion-> agreed
 +
* Alex: SWT linux currently uses X-Windows specific API, which does not work on Wayland. This will be moved to a DBUS API to open file and open URL
 +
* Dani: Plan update, biggest change is for the component plan
 +
** Equinox plan has been added
 +
** Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build
 +
* Launcher and natives build move from IBM to the foundation still in progress
 +
** ({{bug|528230}}) Build FileSystem native component on Eclipse Foundation Infra
 +
** ({{bug|528230}}) Build launcher on Eclipse Foundation Infra
  
−
<hr/>
 
−
'''January 15, 2014''' - McQ, Andrew, Dani, Martin
 
−
* Dani: Lakshmi (SWT Team) going on maternity leave - SWT still a decent team of 4
 
−
* Andrew: PMC Participation - Suggestion
 
  
−
<hr/>
 
−
'''January 8, 2014''' - Dani, Martin, Andrew, John, McQ
 
−
* Dani: '''API Freeze''' with M6 on March 7, but JDT cannot put Java 8 stuff in before (March 18) thus will have to ask for an exception
 
  
 
= Archive =
 
= Archive =
 +
* [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]]
 +
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 +
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]
 +
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]
 
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]
 
* [[Eclipse/PMC/Minutes 2012 | Archive of Meeting Minutes from 2012]]
 
* [[Eclipse/PMC/Minutes 2012 | Archive of Meeting Minutes from 2012]]

Revision as of 10:21, 23 May 2018

Documents

Some documents written and/or used by the PMC:

Meeting Schedule

The Eclipse Project PMC has a weekly phone meeting every Tuesday at 11.00am EST.

Meeting Minutes

May 22, 2018 - Alex, Tom, McQ, Dani

  • EPL 2.0
    • Still working with foundation on whether we can gradually move to 2.0
  • Will we be supporting updates from release to release in the new 3 month release cycle?
    • Yes, unless we explicitly indicate otherwise.
    • To simplify this, we should have a "latest" update site
    • We need to make this simpler for users, but not get in the way of the EPP, OOMF, etc.
    • Alex to write this up in more detail
    • Dani reminded us that there had been a previous discussion in the planning council
  • Project leads have updated Photon plans
    • Dani will be updating the overall plan; PMC to comment on bug 529640
  • Dani also working on release review and IP log
    • PMC members to approve once it's ready
  • As previously discussed our first milestone will be called "M2"


May 15, 2018 - Alex, Tom, McQ, Lars, Dani

  • GDPR
    • audit did not report any issues on our project pages
  • Opening development for 4.9
    • Will branch RC2 and update master with required Releng work
    • master will be open after RC3
  • EPL 2.0
    • No plans to do anything for 4.8
    • Lars will look into it
    • Ideally we gradually move to 2.0


May 8, 2018 - Dani, Alex, Tom, McQ

  • GDPR
    • Eclipse Project collects no information from the users on the project websites
    • The Error Reporting tool, might be impacted
    • Also possibly bugzilla <-- Do we need to delete bugs older than some retention period?
    • Impossible to remove emails from all git repos (because of cloning)
    • We need to be sure to respond to requests from the foundation
  • Jetty
    • 9.4.10 is in latest build, and help system is working
    • they made the dependencies that were problematic optional


May 1, 2018 - cancelled due to public holiday in most Europe


April 24, 2018 - Dani, Lars, Alex, Tom

  • Target environments
    • We will keep Java 8 and 10 and remove java 9 from the list
    • remove JVMs as soon as they run out of support from target environments - AGREED
  • javax.annotation
    • Version shipped is quite old, should we update it to newer version
    • Update to latest standalone release to be tried
    • Alex to try to drive this through
  • Notify cross project about removal of ee modules from the JVM
    • People don't follow Java 11 work so will probably be surprised when things start to fail so we better try to spread the information
    • Dani will send a link to the JEP containing detailed information
  • Contribution guidelines
    • Do not open bugs for simple changes and cleanups
    • Actual bug fixes to be split from cleanups in separate patches so the bug commit is straight on the topic
    • Dani will update the wiki
  • Cancel May 1st call - public holiday in Europe


April 17, 2018 - Dani, Alex, McQ

  • On Java 11...
    • We are actually shipping the javax annotation support
    • Java 11 is working in 4.8, but isn't in 4.7.x
      • Tom Watson is investigating why it is not working 4.7.x


April 10, 2018 - Tom, Dani, Lars, Alex

  • Discussed bug 533390: Eclipse does not launch with Java 11


April 3, 2018 - Tom, Dani, Mcq, Lars

  • 4.7.3a update
    • Delivered RC2 on Saturday, so we could fix some badness in handling Java 10 "var" support (tl;dr: rename appeared to allow you to affect "var" as if it were a type (but would not have modified the code))
    • Currently think we're done
  • Naming milestones
    • As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1".
    • We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming.


March 27, 2018 - Tom, Dani, Mcq, Lars, Alex

  • Java packages for configured Java in workspace
    • Equinox no longer provides hard-coded information about execution environments. In the past this information was used at runtime for describing the running execution environment within the OSGi Framework. Other usecases outside the Framework started uses the Java profile data from Equinox. Equinox no longer has any need for the hard-coded information so no longer provides it.
    • JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
    • JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
    • See 531642 532773
  • SWT clean-up
    • Lars reviewed the removal of Windows XP. Built binaries locally on Windows.
    • Found a form data issue deleted some code that was still used
    • Tom - Unit tests didn’t catch the issue. Concerning?

--> Update from Lars after the call: Later testing did show that this is a bug already existing in Eclipse. 4.7 and master and not related to the patch

    • Lars did review and test
    • Dani - put all the code in the branch and produce a build and ask windows community to test it
    • Mcq - thinks it is a good idea
    • Dani - create an official build for testing, not out of master with normal builds
    • Lars - what is the risk of putting in master
    • Dani - can do the build right away pre-CQ review approval. Allows for more quick testing.
    • Alex, no need for a branch, can be a developer build we publish. Alex will ask Leo to do this.
  • Jetty version
    • Jetty added non-optional dependencies on service-loader
    • Dani - got reverted, but old versions still caused Gerrit build issue
    • We don’t need the service-loader for our usage of jetty
    • jetty may be making a hard requirement on an implementation of server-loader (Aries spi-fly)
    • Can we move help off jetty? Will be a major undertaking. Should figure out what it would me to do so. Currently no interested contributer has stepped up to do the work to figure out what this would mean.
    • Equinox will still need jetty for the http service implementation. Perhaps things are more simple if this is an Equinox only dependency. Only pull in jetty if the http service implementation is needed and then pull in all of jetty and its dependencies.
    • No current plans or interested contributors for providing our own service-loader implementation.
    • Our build should start resolving the capabilities are requirements which would catch issues like this early in the build.
    • Alex - can we move latest tycho to get the capability/requirements meta-data. No objections? Alex will move forward.


March 20, 2018 - Dani, McQ, Tom, Lars, Alex

  • Dani: The IBM SWT team considers the Windows XP removal too risky and in addition has no capacity to look at that big change. Fine if someone else looks at the removal. The type changes will have to wait after Photon (too risky). Lars will ask Conrad and Alex will also look at the patches.
  • Databinding generification should be done early 4.9, too late for Photon.
  • Dani: Eclipse support for Java 10 will be merged to the official branches starting Wednesday. A Marketplace entry for 4.7.3 will be made available once 4.7.3 is released. The first official release with Java 10 support is 4.7.3a scheduled for April 11.


March 13, 2018 - Dani, McQ, Tom

  • Alex had troubles to join; Lars still in vacation
  • Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
    • ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project


March 6, 2018 - McQ, Tom, Alex

  • Short call without any interesting topics


February 27, 2018 - Lars, Dani, McQ, Tom, Alex

  • JDT support for new Java releases
    • McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible
    • Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community
  • Dropping XP support
    • Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release
    • Mail to be posted to cross project by Dani to gather feedback
    • Alex: 1 week for gathering input on cross-project - AGREED
    • If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex
    • To be formally voted after the mail to cross-project
  • Release names
    • Version only, release names are irrelevant from Eclipse TLP side - AGREED
  • Inactive committers pruning
    • Lars: no access to committer emails so sending just to the mailing list
    • Wait 2 months for reply before action
    • McQ: ask foundation to send direct mails on behalf of the project, if foundation is not fine - remove committers directly
    • Alex: only public replies to the mailing list are accepted so people wanting to remain committers at least follow the mailing list
  • Tip of the day -
    • Lars: CQ approved, to be merged today/tomorrow
    • Alex: we should have it part of the build and part of the p2 repo for easy testing
    • Dani: unclear APIs to be removed and to be simplified so we don't end up maintaining useless parts
  • GTK 2 vs. 4
    • Alex: Gtk 4 release aiming at late 2018, it's big change in drawing so conflicts with Gtk 2 badly
    • Alex: Gtk 2 support to be removed in future one of the next 2 releases, whether Sep or Dec to be discussed later in the Photon release train
    • Alex: mail to cross project list around Photon M7 or RC when more information on both Gtk 4 release plans and SWT bugs will be known
    • McQ: what is our statement on supported Gtk version?
    • Alex: Statement should be: Once SWT switches to latest Gtk version as default, support for previous versions goes into deep maintenance mode but will kept until it starts hurting new development and support for the default version at which point to be removed.
    • To be discussed further.


February 20, 2018 - Lars, Dani, McQ, Tom

  • Dani: Update on 4.7 RC3
  • Lars: Can we drop Windows XP support?
    • Lars: Big contribution comes in (https://bugs.eclipse.org/bugs/show_bug.cgi?id=531097), dropping XP support might be a good motiviation to contribute more also to other people. Removing lots of code including the version checks will also result in a cleaner code base for maintenance and might improve performance.
    • Dani: IBM investigate if they officially drop XP
    • Tom: Do we need support XP with the latest Eclipse version?

--> Pending on the answer of the IBM team, will be discussed in next weeks call

  • Tom: OSGI CQs updated and approved for OSGi Service Platform 7.0 version


February 6, 2018 - Lars, Dani, McQ

  • Lars: Can we mark MInput and MInputPart for deletion (bug 509868)?
    • Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references.
      • McQ agrees
  • Dani: Topic on ui-best-practices-working-group list: Replace "..." with an ellipses Unicode character
    • Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
    • McQ:
      • Mac OS UI guidelines specify to use the ellipses character
      • SWT could do the right thing depending on the platform
  • Lars: view menu, minimize and maximize buttons look bad to him. Would like to replace the view menu with ellipses
    • Dani: Would have to change all three together. View menu is always there and not indicating an overflow
    • McQ: Windows 10 also uses a triangle, but upwards. Current view menu is used and familiar to users for at least more than 10 years.
    • Lars to file a bug report and send the bug number to the PMC
  • McQ: Should discuss in one of the next meetings how JDT can handle the new release cadence for Java
    • Dani: We will see how it goes with Java 11 (18.3)
  • Dani: How will we name the milestones in our new new release scheme?
    • Consensus to start with M1 after each release.
    • Up to planning council to decide the release naming convention. Lars: Would prefer year/month


January 30, 2018 - Alex, Lars, Dani, Tom

  • General Updates (Dani)
    • Shipped M5, still working some p2 issues
    • RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates
    • Discussion about the incubation for Java. Ongoing thread in jdt-dev list https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00964.html. The incubation features will be part of the release specification which implies they need to be implemented to be compliant. Spend time putting them into a release only to pull out later if they don’t finalize. Not clear there are tests added to the TCK. Alex asks if this effects us for Java 10, no not for Java 10. Java 10 only has local type reference, not huge delta of function from Java 9. No incubation in Java 10. But incubation may affect us for Java 11.
  • Info about infrastructure (Alex)
    • Foundation push to move to Jenkins. Releng has moved, uncovered issues with rest API and token exchange … disabled for now for Jenkins. Issue is being worked but only can be fixed once all is moved to Jenkins.
    • Platform HIPP moving to Jenkins tomorrow. Will be some downtime, should be less than an hour or so. May cause several issue. Issues in non-standard jobs with multiple repos etc. For Gerrit verifications should be fine. Let Alex know if there are issues. Alex to send a note when the migration occurs.
    • p2 issue is real. Other issues are pressing (infrastucture/build). Todor has a bug that he should be looking at. Not something happening in the past, but now the capabilities are being resolved. Issues happened with a hand crafted p2.inf file. Hopefully will scope down the p2.inf files. Alex to drive to determine if a respin is needed.
    • Need to monitor the p2 issue, determine how many are broken. Cannot just break 100s of folks without serious consideration. Why not revert? Alex says it is not an option and we should do everything possible to fix.
    • Lars asks about nominating more committers, perhaps that were rejected in the past. Now the Eclipse PMC can overlook the nomination process. Work with existing contributors showing interest and look for opportunities to sponsor them for committership.
  • Tip of the day (Clippy)
    • See Tips Framework
    • Tip of the Day or (Clippy) in coming contribution … looking for integration M6?
    • Lars thinks it is worth it. Dani disables such things by default, and also Lars. Alex find the function interesting. Others are also reviewing the patch.
    • Lars is moving forward with it. If it is very easy to disable and is stable on all platforms then it should be good.
    • Is there a concern about a solution that requires network … it doesn’t appear to be a concern.


January 16, 2018 - Alex, Lars, Dani, Tom

  • Native builds at eclipse.org status (Lars):
    • Dani: swt is done for some time already
    • Dani: launchers after M5 is released to prevent breakage
  • GTK launcher changes (Alex):
    • Changes to not rely on X11 atoms but on dbus ready for review
    • Linux only as no other GTK platforms are currently built
  • Equinox CQs (Tom):
    • P2 capabilities patch from Todor and felix.scr update
    • Slow process risking M5
    • Alex: Ping Sharon asking for speedup if possible
  • Updates from Dani:
    • Photon plan update - BREE to be part of the build info
    • End game - Oxygen.3 and M5 - send to the list
    • Running tests against Java 9
  • Java 10 eclipse release (Dani):
    • Oxygen.3a or marketplace feature only - Agreement for oxygen.3a
    • Dani: Local Variable type inference support in a branch
    • Future releases - to be aligned with JVM releases if they prove to release on time
  • BREE updates recomendations
    • Dani: There are reasons to stay on older BREE
    • Alex: ease of getting jvm is the main concern here - if a contributor can't get jvm at that version easily we can't call it supported


Januar 09, 2018 - McQ, Alex, Lars, Dani

  • Updates from Dani:
    • Ian Skerrett is leaving the Eclipse foundation
    • Dani got nominated as committer representive
  • Planning council update
    • Dani: low participation in the last calls
    • Dani will talk with Melanie about it
    • Input required for the planning council for the API and feature freezes for the platform
  • API and feature freeze policy in platform
      • Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build
      • everyone agrees to Alex suggestion-> agreed
  • Alex: SWT linux currently uses X-Windows specific API, which does not work on Wayland. This will be moved to a DBUS API to open file and open URL
  • Dani: Plan update, biggest change is for the component plan
    • Equinox plan has been added
    • Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build
  • Launcher and natives build move from IBM to the foundation still in progress
    • (bug 528230) Build FileSystem native component on Eclipse Foundation Infra
    • (bug 528230) Build launcher on Eclipse Foundation Infra


Archive

Retrieved from "https://wiki.eclipse.org/index.php?title=Eclipse/PMC&oldid=425361"

Back to the top