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"

(Meeting Minutes)
(Meeting Minutes)
(309 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 11: Line 10:
  
 
= Meeting Minutes =
 
= Meeting Minutes =
'''Noc 1, 2016''' - McQ, Sergey, Lars, Dani, Alex
 
** We agreed on the following changes:
 
1.) Create maintenance branch immediately after RC1 instead of after the release. Use the maintenance branch to produce the upcoming release.
 
2.) Eliminate all code freezes on the main branch for RC releases, except for 1-2 days after RC1 before the maintenance branch is created. Freezes to allow test
 
for milestone builds will still be applied (milestone freezes).
 
3.) We decided that we will only have ‘I’ like builds, using always signing.
 
  
'''Oct 18, 2016''' - McQ, Sergey, Martin, Dani, Alex
+
'''February 25, 2020''' - Dani, McQ, Tom, Alex
* Dani: '''PMC Approval for Sergey co-lead on Resources''' (Done)
+
* Dani: Created and sent Endgame plan
* Alex: '''Lucene Update'''
+
* Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
** Looking at updating to 6.x in Oxygen - CQs ongoing for Orbit - hoping to make M4
+
* Alex: SWT on Linux in 4.16 to require Gtk 3.20 to simplify CSS machinery and prep for GTK4
** Others like Mylyn, Pydev, ... use Lucene 5.x at this time; others consume the Platform
+
* Alex: ICU4J removal
** There is some potential breaking things but should be fine since multiple Lucene's in parallel can work.
+
** Dani: ICU4J reacts faster to changes and supports more features (new Japanese era)
** If an old pre-built help index can not be read, a new one is generated (Performance hit on the first run)
+
** Alex: It might but Eclipse fails at keeping up so current version shipped with Eclipse misses features that the JVM supports (latest CLDR)
** Dani: No issue, will also update Jetty in M4
+
** Dani: Asks for a proof that JVM is better that ICU
* Dani: Would like to open '''eclipse.jdt''' repository and corresponding sub-project to all JDT committers (currently only used for the JDT feature)
+
** Alex: Which metrics to be measured?
** The project is almost dead with only 2 active committers, since new JDT leads were not voted in
+
** Dani: Will check with ICU guy about that and whether it's still needed
** Changes to feature will be rare, and Dani agrees to review
+
 
** Allows to put the Oomph setup file into a shared place where all JDT committers have access
+
 
** PROPOSAL AGREED by all.
+
 
* EclipseCon Europe next week - Dani, Lars and Alex will be there - will '''cancel next week's meeting'''
+
'''February 18, 2020''' - McQ, Alex, Dani, Lars, Tom
 +
* Dani: need to work on IP Log, Release Review and Endgame Plan
 +
* Lars: ECF - will we update to the latest
 +
** Alex: is in the works. Scott needs to provide us with the update
 +
* Tom: Found an issue with JUnit 5 launching but not reproducible with latest I-build
 +
** Dani: File a bug if you have steps or contact Noopur directly
 +
* Dani: Update on X-builds and tags
 +
 
 +
 
 +
'''February 11, 2020''' - McQ, Alex, Dani, Lars, Tom
 +
* Alex: Infrastructure is very instable, how can be complain to the foundation?
 +
** Alex: Eclipse foundation server team not responding to complains and seem unclear about the source of the issue
 +
** Discussion about makes a stronger statement to the foundation about the bad state of the infrastructure
 +
** McQ: Suggestion to send a note as PMC to the foundation
 +
** Dani: First we should ask webmaster why this takes so long
 +
** Alex: Marketplace infrastructure is also in bad state
 +
*** Dead marketplace entries are not getting removed https://bugs.eclipse.org/bugs/show_bug.cgi?id=550713
 +
*** No clean contact person from the foundation
 +
*** Marketplace is also not Open Source hence we cannot fix thing ourself.
 +
 
 +
-> Alex to contact Denis and to cc the other PMC members
 +
 
 +
'''February 4, 2020''' - McQ, Dani, Tom
 +
* OSGi Spec talk
 +
** OSGi R8 Core will be done this year.
 +
** May be ready for 4.16, but no rush if it slips to 4.17
 +
** Will not put anything in master until spec is final which makes it more likely to be 4.17
 +
 
 +
 
 +
'''January 28, 2020''' - McQ, Alex, Dani, Tom, Lars
 +
* Ongoing saga of the EPP packages
 +
** Markus did it last week
 +
** PMC discussed possible futures here, but no conclusions
 +
** Discussion also happening at the board level
 +
* M2 is this week
 +
* Pushing for JUnit updates for M2
 +
 
 +
 
 +
'''January 21, 2020''' - Dani, Tom, Lars
 +
* Dani: EPP builds still missing, Dani contacted Markus Knauer to update EPP for M1, release train is at risk if nobody steps up
 +
* New test failures are investigated, action plan is to restart the test, if they still fails restart the machine and if the tests still fail, see if a revert fixes the test
 +
 
 +
 
 +
'''January 14, 2020''' - McQ, Alex, Dani, Tom
 +
* Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
 +
* Dani: Plan updated to remove Windows 7
 +
* Alex: Felix Dependencies for SCR done
 +
** confirm fix for {{bug|544571}}
 +
** releng disruptions during update, but recovered. More disruptions expected as we update dependencies for March release.
 +
** broken builds, need to get a list of issues. Seems to be more infrastructure issues. Need to report back to the foundation. Example, the signing issue that broken the respin.
 +
* Some discussion about gitlab option at foundation. {{bug|537913}}
 +
** What happens to gerrit work flow for review?
 +
** Would dropping bugzilla happen or can we migrate all issues?
 +
** Without migration it is a no-go for us
 +
** Currently no plans to move Eclipse project to gitlab at this time.
 +
 
 +
 
 +
'''January 7, 2020''' - McQ, Alex, Dani, Tom, Lars
 +
* Dani: Created initial 4.15 plan - please have a look
 +
* Dani: Created release record for 4.15
 +
* Dani: Sent a note to teams to create their 4.15 plan items/bugs
 +
* Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
 +
** Unanimous decision: Yes
 +
* Dani: Discuss (again, see below) resolution for stale bugs
 +
** We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
 +
** We will only auto/mass close existing stale bugs with notification turned off
 +
* Change rules about x-internal exports ({{bug|553709}})
 +
** Decision:
 +
** - Newly added internal packages should not use x-internal exports unless there are very good reasons
 +
** - For existing packages the x-internal export can be removed with PMC approval
 +
 
 +
 
 +
'''December 10, 2019''' - Alex, Dani, Tom, Lars
 +
* Dani: RC2a respin to be promoted today
 +
* Dani: 4.15 M1 approaching fast (January 10)
 +
* Dani: master is open
 +
* Dani: Version bumps done for now
 +
** Rebase if needed Gerrit makes it being able to push without version bumps and breaks next build
 +
** Tool needs improvement to collect all version bumps needed to make initial bumps faster
 +
* Dani: How to make milestones used more
 +
** Have latest and deny things that have been since M1 and no one reported till RC1
 +
** Consider having latest unstable aka milestone channel which can be used by users/integrators
 +
* Tom: Java 8 support dropped - no decision to be made now
 +
 
 +
 
 +
'''December 3, 2019''' - Alex, Dani, McQ, Lars
 +
* Dani: RC2 this week. Supposed to be the end of 4.14 for us.
 +
* Dani: Rules for exporting packages as outlined in [https://wiki.eclipse.org/Export-Package Export-Package] :
 +
** Background: {{bug|544977}}.
 +
** We need to discuss whether we want to relax those rules.
 +
** Tom to file a bug report.
 +
 
 +
 
 +
'''November 26, 2019''' - Alex, Dani, McQ
 +
* GTK minimum version being upgraded: 3.14 -> March; 3.22 -> June
 +
* Target environments upgraded for 4.14, PMC members please verify
 +
* Standalone SWT download was broken in M3; Fixed in RC1
 +
* Mac downloads are now being notarized
 +
* Red Hat team will help with release engineering work
 +
 
 +
 
 +
'''November 19, 2019''' - Tom, Alex, Lars, Dani
 +
* Bumping GTK minimum version for SWT
 +
** No bump has been done in the last 2 years
 +
** GTK 4 is starting to shape up.  In preparation we need to move up.  3.14 minimal version from 3.10 for March 2020 release.  Will allow styling to go through our CSS engine.  Will address many bugs because we override the behavior.  Allows us to remove dead code.
 +
** For June release move to 3.22 release directly.  Wayland is useless under 3.20
 +
** Will confirm with the SWT team that this is ok, will have an answer next week.  PMC agrees to proceed as long as the development team is OK with it.
 +
* Dani: Fighting with build
 +
** Orbit checksums were not redone in latest (working on fix)
 +
** Issues with Mac signing - been really unreliable {{bug|553205}}
 +
* Dani: No IPLog needed this release, will need to be at least every year and we will do it in March.
 +
* SWT patch for Windows, allows to theme the scrollbar.  Patch is stale now?
 +
** Can the team look at the patch and rework? We can review but likely not rework. {{bug|444560}}
 +
 
 +
 
 +
'''November 12, 2019''' - Tom, Alex, Lars, Dani
 +
* M3 next week
 +
** Many open bugs targeted for 4.14 M3 and 4.14
 +
** Request for contributors to act on them and retarget
 +
* Gerrit reviews
 +
** Dedicated time to spend on review patches from non-commiters and non-employees of IBM and Red Hat
 +
** Time still to be considered
 +
* Dani to check whether IP Log and review are needed for 4.14
 +
* Official build runs with Java 11 now
 +
** This is the runtime JVM used by the build system, nothing in the deliverables should require Java 11
 +
** Tools are catching up, reports had to be modified to work with it
 +
** If there is any issue noticed in deliverables, reports, download pages ... - please open a bug report and add Alex on cc
 +
* Pack200 (tom)
 +
** Test whether everything is fine if pack200 is gone is pending
 +
** Companies shipping only packed files will face issues
 +
** Ship alternative pack200 implementation? - better look at alternative compression if so critical
 +
** Build tools (e.g. reports generator) are using Pack200 classes directly, that would be a problem in the future
 +
** Drop packed files requirement for SimRel
 +
*** If/when contribution requires Java 14 it's the only feasible thing to do, to be clarified in requirements
 +
 
 +
 
 +
'''October 29, 2019''' - Tom, McQ, Alex, Lars, Dani
 +
* Dani
 +
** still working on the PPC64LE issue
 +
** EclipseCon was great, met lots of people, JDT team plans to do more reviews in the future
 +
*** Dani: missed Lars, Mickael, Andrey and others
 +
** Wayne and Markus might not continue to work on the release train, so this may end up an automatic process or a new working group may be founding another person
 +
* General discussion about unmaintained projects and how to deal with that
 +
 
 +
'''October 15, 2019''' - Tom, Alex, Dani
 +
* Shipped 4.13 M1 on time
 +
* Quickly discussed Wayne's plans to reduce his time for the Release Train
 +
* Next week EclipseCon (no Dani)
 +
 
 +
 
 +
'''October 08, 2019''' - Tom, McQ, Alex, Dani, Lars
 +
* PPC64LE machine
 +
** Downtimes experienced with current one and general warning that there might be more
 +
** McQ: how many downloads do we have?
 +
*** Dani: probably more in products rather than IDE downloads
 +
** PPC64LE workstation on the market (https://www.raptorcs.com/content/TL2DS1/intro.html) and Fedora looks into adding PPC64LE desktop spin
 +
* Jetty update test failures
 +
** Tom to ask Raymond to help us with it
 +
* 4.14 plan created
 +
** To be published once we gather the work items
 +
* Release record created
 +
* M1 this week
 +
* Gerrit submit
 +
** AGREED: Switch to "Rebase if Necessary"
 +
** Alex to take care of contacting admins to see change implemented
 +
 
 +
 
 +
'''October 01, 2019''' - Tom, McQ, Alex, Dani, Lars
 +
* Dani to look into plan and release record for 4.14
 +
* Stale bug reports should be closed as WONTFIX if there is not a response to the stale bug flag
 +
* Changes on Gerrit to allow fast-forward merges
 +
** deferred to next week
 +
 
 +
 
 +
'''September 24, 2019''' - Tom, McQ, Alex, Dani
 +
* discussed enabling fail on warnings on JDT projects
 +
** Dani to clarify with Roland
 +
 
 +
 
 +
'''September 17, 2019''' - Tom, McQ, Alex, Dani
 +
* Crash issue on win32 - respin done
 +
* Java 13 GA
 +
** marketplace entry works with M3 and onwards
 +
** merge into master starting
 +
* 4.13 GA
 +
** looks goods so far, packages are there
 +
** macos notarization still in process for EPPs
 +
 
 +
 
 +
'''September 10, 2019''' - Tom, McQ, Alex, Lars, Dani
 +
* Gerrits are failing
 +
** one failed because of missing version increase, some appear to be tooling issues
 +
** change went in to API tooling, which may fix it
 +
** do not merge failing gerrits
 +
* Many thanks to those who worked through the weekend to fix the Mac signing issue!
 +
 
 +
 
 +
'''September 3, 2019''' - Tom, McQ, Alex, Lars
 +
* Discussed status of RC3
 +
** This Friday for Platform - two known issues being looked at
 +
** {{bug|550672}} - Alex - Still no final solution to the problem.  May result in backing out fix to {{bug|548002}}
 +
** {{bug|550606}} - Tom - at first seemed like a major regression that could require a revert of fix to {{bug|548877}}.  Alex - has been determined to be a very limited scenario that we feel is not blocking the release and does not warrant reverting to fix.
 +
* Discussion of download stats.  Much improved over the past year and looks to be double what the Photon release was a year ago for the 2019-06 release.
 +
** Some thoughts on what has caused the increased interest. Lars - much work around quality and performance. Alex - a result of a broader community involvement and other development plugins for eclipse gaining popularity which drive Eclipse downloads.
 +
 
 +
 
 +
'''August 27, 2019''' - Tom, Dani, Alex, Lars
 +
 
 +
* Dani - Status update
 +
** RC1 this Friday for Platform - on track
 +
** Still working on Notarize Mac app ({{bug|549814}})
 +
* Dani on vacation next week, starting this Friday
 +
** ==> please watch out for approval requests for API and feature changes after RC1
 +
 
 +
* Lars - new filter icon ({{bug|465914}})
 +
** all agree to be willing to change the icon
 +
** Dani: not just a funnel, but maybe a combination of sieve and funnel, or a good sieve icon
 +
** Lars: will make some suggestion in the bug report
 +
 
 +
* Lars - compare panel orientation: should we change the default to what's in Gerrit? ({{bug|501752}})
 +
** Agreement to try in 4.14 M1
 +
 
 +
 
 +
'''August 20, 2019''' - Tom, Dani, Alex, Lars
 +
 
 +
* Dani - Status update
 +
 
 +
** Tests are looking good for M3
 +
** Dani team gave focus to new Search, found several UX issues, like shortcuts
 +
** NPE Bug in the JDT quick outline, got fixed and rebuild was triggered
 +
** Resource packs were donated by Redhat, IBM and vogella GmbH to platform, discussion how long it will take for the foundation to update
 +
** Dani to discuss the build infrastructure with the foundation
 +
 
 +
* Parallel activation for the IDE - Tom
 +
 
 +
** Tom stated that it will be very time consuming to enable this
 +
** Might cause lots of issues during startup, i.e. deadlocks or missing DI due to activation order
 +
** Result: definitely nothing we should just do, without seeing a clear benefit during startup and it would require lots of efforts to get this well tested
 +
 
 +
* Process removal of views - Dani /Lars
 +
** NavigatorView is deprecated but plugin.xml extension is not deprecated as we have no means of doing that
 +
** Suggestion from Lars: Announcement of removal now and mark for deletion
 +
** Suggestion from Dani: Replace the implementation
 +
** Alex: Adding it to the label of the view
 +
 
 +
Result: Send out send to cross that we want to delete the view, outdate the label with "Deprecate" and mark it for deletion.
 +
 
 +
Tom: Do we need a way to deprecate an individual extension? Discussion about and general agreement that this would not help clients.
 +
 
 +
'''August 13, 2019''' - Tom, Dani, Alex, Lars
 +
* Dani: Mass changes only up to M1?
 +
** Lars - If everyone agrees then post M1 changes can happen
 +
** Tom - What makes it a mass change?
 +
** Alex - doesn't see the need for timeline on guideline, just make it across the build
 +
** -1 review always blocks the merge until some agreement is made on the change
 +
** Committers are not required to have review and it is up to the committer to ask for a review
 +
** JDT has additional concerns because a branch is needed to do next Java release development.  Should just be a restriction for JDT to decide when mass changes can be made.
 +
** Resolution:
 +
*** Mass changes are requested not to be more than 50 files in general if they can be split up but ...
 +
*** Don't force it to be split for cases it is difficult to do so
 +
*** A committer can block a mass change (like any other change) with -1 if there are good arguments
 +
*** Don't restrict mass changes to specific milestones
 +
*** Cleanups are allowed at any time during development cycle
 +
*** Should reviewers be added?? 
 +
**** No adding reviewers is not required by committers
 +
**** Project leads should monitor Gerrit queues - PMC agreed
 +
* General discussion about JDT team changes with Java release cycle ...
 +
** expect large changes for Java 14 (e.g. Valhalla)
 +
* Alex - What happens when our dependencies require java 11?
 +
** Particularly for help, Lucene and Jetty
 +
* Lars - Fix in toolbar ({{bug|549898}}) that exposed another bug that is old
 +
** If not fixed do we need to revert original issue?
 +
* Dani talks about resource packs and possibility of companies donating resources to the Eclipse Project: https://www.eclipse.org/lists/eclipse.org-project-leadership/msg00181.html
 +
 
 +
 
 +
'''August 6, 2019''' - McQ, Tom, Dani
 +
* Dani: contributed I-build to M2 last Friday
 +
* Discussed [https://www.eclipse.org/lists/platform-dev/msg01793.html macOS 10.15 notarization process]
 +
 
 +
 
 +
'''July 30, 2019''' - McQ, Alex, Dani
 +
* Nothing to discuss.
 +
 
 +
 
 +
'''July 23, 2019''' - McQ, Tom, Dani
 +
* Nothing to discuss.
 +
 
 +
 
 +
'''July 16, 2019''' - Alex, Tom
 +
* Bouncycastle MessageDigets plugin inclusion (bug 541781)
 +
** Alex: Which feature should contain it so it's published?
 +
** Tom: Let's discuss on the bundle but usability of current equinox features is questionable.
 +
** Alex: Let's sanitize them in this case.
 +
** Tom: +1, we need to figure what the deprecation policy (if any) there is for features.
 +
* Merge of rt.equinox.bundles and framework git repos
 +
** Tom: still interested in it but very low priority
 +
** Alex: interested in it for the sake of rename of repos from rt.equinox to eclipse.equinox
 +
 
 +
 
 +
'''July 9, 2019''' - Dani, Tom
 +
* Dani: M1 this week. Looks good so far.
 +
* We will not suspend the calls during summer.
 +
 
 +
 
 +
'''July 2, 2019''' - Alex, Tom
 +
* General chat about bugzilla vs gerrit only workflow.  No binding decisions due to lack of quorum.
 +
 
 +
 
 +
'''Jun 25, 2019''' - Alex, Lars
 +
* General chat about state of affairs due to lack of quorum
 +
 
 +
 
 +
'''Jun 18, 2019''' - McQ, Lars, Tom
 +
 
 +
* The 1.5 minute start up time issue (Windows Defender) needs to be investigated
 +
** Is this related to the signing problem?
 +
*** Dani: No, see {{bug|548397}}
 +
** What do we have to do to be "blessed" by Microsoft?
 +
***Dani: Not sure this is the solution as we do not even know what the problem is
 +
* There is a perception that Eclipse on Windows is not as smooth/performant as Linux now
 +
** This is a bit troubling, since windows is still our most significant platform (by downloads)
 +
** Do we need to look for ways to increase participation in SWT on Win?
 +
* Do we need better coding pattern/style guidelines?
 +
** Particularly for "clean up" patches that touch a wide range of code
 +
***Dani: I think so, see [https://www.eclipse.org/lists/eclipse-pmc/msg03670.html Andrew's note to the PMC mailing list]
 +
 
 +
 
 +
'''Jun 11, 2019''' - McQ, Dani, Alex, Lars, Tom
 +
 
 +
* 2019-06 release
 +
** RC2 shipped on time
 +
** No pending request
 +
** Lars: Opening next release stream - felt too long due to amount of incoming gerrits. It's a nice problem to have but no change planned on the topic so far.
 +
* Gerrit down
 +
** Dani called webmaster, negotiated it to be made tier 1
 +
* Emeritus status for historical committers
 +
** Foundation is dropping the feature overall so no plans to nominate new people from the last group of removed committers
 +
* No bug report policy
 +
** Simple fixes do not require bug report
 +
** Dani: larger patches to require bug
 +
** McQ: reviewer should the have the right to request
 +
** Alex: requiring too many bugzillas is against young population used to github
 +
** AGREED - we stay as we are and reviewer has the right to ask for one if he feels the need
 +
* New committer process document - whoever has a comment to comment on the document
 +
* Modern eclipse
 +
** McQ: how to define what to work on without too much bias
 +
** Alex: new intern working on inline editing - an initiative to serve as example of modernization
 +
** AGREED - come up with list of things to work on
 +
** ACTION ITEM: Lars: to create initial document for list of things/initiatives
 +
* Dani not on call for the next 3 times (Eclipse Board meeting, manager training and vacation)
 +
 
 +
 
 +
'''May 28, 2019''' - McQ, Dani, Alex, Lars, Tom
 +
 
 +
* http client issue
 +
** should we ship old and new?
 +
** we initially decided to only ship new one.
 +
** ship old only gives ability to revert back, but still requires work on client
 +
** if a fix isn't available for using the new http client then we will consider shipping only the old one for 4.12
 +
** others can install the new http client if they want to try it out
 +
* message to Stephan
 +
** Note set, no additional information or status available
 +
* heading into RC builds for 4.12
 +
** end game plan created
 +
** finalizing the plan and closed after updating target environments
 +
* discussed {{bug|547011}}
 +
** decided to bump event bundle version to work around
 +
** need a new bug opened to enable us to detect this situation earlier
 +
* Major version increase on API removal discussion
 +
** announced API removals will not cause major version bumps
 +
** This potentially breaks others
 +
** We only do this on announced deprecations for 3 years.
 +
* Future of Eclipse IDE (McQ)
 +
** Power users for writing code.  A lot still use vanilla text editor ...
 +
** What is the value of the IDE in today's environment.  Deployment and monitor of applications is more important.
 +
** Are we not addressing the problems of today to make Eclipse the power tool of today.
 +
** Do we need support for new languages.
 +
** Language server help?
 +
** can we find some set of things to do to reduce friction to using Eclipse IDE?
 +
** remove notion of project natures?
 +
** asynchronous operations can help?
 +
** Make our lists of top things to do
 +
** get community involvement on prioritizing the list of important things to improve.
 +
* Alex out next week
 +
 
 +
'''May 21, 2019''' - McQ, Dani, Alex, Lars
 +
* Dani
 +
** M3 is this week, need to watch out for bugs and issues
 +
** New feature to make modal dialogs non-modal created a blocker but this has been fixed
 +
** Endgame plan will be send out by Dani by the end of this week
 +
** We only ship an HttpClient45 implementation with the latest ECF and no HttpClient4 anymore which may cause issue. Dani's team will send out a note tomorrow, Alex thinks that this should not create an issue
 +
** Release restrictions from the foundation are less strict for the next release (no IP log and release review for every release required anymore), we will follow this process
 +
* Discussion about Stephan Herrmann's email to the PMC and we need to check with Stephan
 +
** IBM may have an option to provide service releases
 +
** We should also look at the bug system to see what is important to the users
 +
 
 +
'''May 14, 2019''' - McQ, Dani, Alex, Tom
 +
* No complaints about our M2 delivery so far
 +
* M3 is next week
 +
** 200 bugs still open
 +
** People are just bumping them to the next milestone
 +
** Better to remove target milestone if you don’t actually believe it will be fixed by then
 +
* Jetty dev list note:
 +
** https://www.eclipse.org/lists/jetty-dev/msg03307.html
 +
** javax namespace stuff will move jakarta namespace
 +
** Jetty 9 and 10 will support what was there, but we will need to react at some point
 +
** Things in flux
 +
* Batik update — 4 of 5 CQs approved should be in for M3
 +
 
 +
 
 +
'''May 7, 2019''' - McQ, Lars, Dani, Alex
 +
* Gerrit verification jobs to give -1 on warnings
 +
** Dani: not easy, single file with warnings in Jenkins for all type of warnings
 +
** PMC is in favor of such solution but there are technical limitations to achieve it or it would require significant effort to get to warning free builds
 +
* ECF http client update
 +
** Dani: prefer to ship both old and new implementation, fine with new one only and reconsider
 +
** Alex: not in favor of shipping two implementations as that would make the testing harder, prefer to ship single one and that being the new one, reconsider if there is issue
 +
** ACTION: Dani to reply to Scott that Eclipse SDK will ship latest only and we would like to have it for testing purposes ASAP
 +
* Inactive committers
 +
** Dani: Notification sent and inactive committers that want to keep commit rights can do it now
 +
* 2019-06 M2
 +
** Dani: I-build delivered to M2
 +
* Dependency updates
 +
** Alex: Jetty is in progress to 9.4.18, permissions to publishing the version to p2 repo on behalf of Jetty project granted
 +
** Alex: Batik - work in progress
 +
 
 +
 
 +
'''April 30, 2019''' - McQ, Tom, Lars, Dani
 +
* M2 for us this week - will only contribute last good I-build - no real milestone week
 +
* Extend fast track for committers for all projects not just inactive ones
 +
** Tom: already following the proposed process
 +
** We can't force committers to accept a new committer (against EDP)
 +
** Unanimous decision to drop fast track program. Mentor/committer can propose any contributor if he can justify the nomination
 +
* Request for review on JDT mailing list
 +
** Wait for Stephan to respond for a day or two
 +
** Dani to contact Stephan if no response
 +
 
 +
 
 +
'''April 23, 2019''' - McQ, Alex, Dani, Tom
 +
* M1 train has been published but no official announcement was sent
 +
* Alex to update Jetty with latest security fixes
 +
 
 +
 
 +
'''April 16, 2019''' - Lars, Dani, Tom, McQ
 +
* M1 has shipped -- Lots of good stuff, see the N&N
 +
* Plan has been posted
 +
** Attempt to simplify the creation process, still WIP
 +
* Started working on identifying inactive committers
 +
** Inactive == haven't committed anything for 2 years
 +
* Looking at ways to ensure we have enough testing of new Java features
 +
** Main projects should run on widest ranges of versions, so can't just raise BREE there
 +
** Could add new test projects, and allow tests to be written with new constructs
 +
 
 +
 
 +
'''April 9, 2019''' - Alex, Dani, Tom, McQ
 +
* Dani
 +
** Lots of regressions Dani investigating
 +
*** cycle from tests (fixed)
 +
*** UI elements gone missing (fixed)
 +
** Get rid of the new index from JDT
 +
*** Needs lots of polish to get rid of bugs, but never showed performance improvements.
 +
*** Decided to disable the option to use it (code remains).  Open to others to help maintain.
 +
** Created initial 2019-06 (4.12) plan
 +
*** Still need individual plan bugs from leads (cough Equinox).
 +
** Created initial release record for 2019-06 (4.12)
 +
** Made a call for plan items for 2019-06 (4.12)
 +
** M1 this week
 +
*** Looks good so far.
 +
* Tom
 +
** Investigating parallel activation of bundles {{bug|540507}}
 +
* Alex
 +
** M1 fixes for SWT
 +
*** Fixes for other things in M1 some small regression in custom Linux environment.
 +
** M1 jsch update needed
 +
** Tom to Open bug for Apache Felix SCR update post M1
 +
** SWT issue
 +
*** SVG image support for Linux-only to start.  Need support for other platforms.
 +
*** Windows has a number of patches pending. (mostly cleanup patches?)
 +
*** Try to get more people on board for Windows support help.
 +
*** Ask for help on the platform list.  We have combined the projects and have more devs available to work on SWT if they are willing to help.
 +
*** For cleanup you need specific SWT knowledge.
 +
**** two types of cleanup - use quick fix from Eclipse - and real refactoring.
 +
** If we are to advance SWT development then we cannot continue with a single committer on a platform.  Need to promote the recruitment of new SWT committers.
 +
 
 +
 
 +
'''April 2, 2019''' - McQ, Dani, Lars, Tom
 +
* Planning for this release has started
 +
** Sub-projects need to have first cut of plan ready by a week from Friday
 +
* Also a week from Friday is our M1
 +
* Based on community feedback we will keep the update site for adding Java 11 support to the 2018-09 (4.9) release, the Marketplace entry remains removed
 +
 
 +
 
 +
'''March 26, 2019''' - McQ, Dani, Alex, Tom
 +
* Dani
 +
** Inactive committer cleanup progress.
 +
*** It is now harder.  Portal has been deactivated and the functionality to get inactive committers is gone.
 +
*** Looking to use some script originated by Lars for list of contributors.
 +
***  What is the timeline to be considered inactive again?  Ans. A year of inactivity will trigger the question.
 +
* Alex
 +
** Confirms that the new indexer has no value to Red Hat (see also March 5 and {{bug|544898}})
 +
** {{bug|545032}} Implement native ImageLoader (Linux only)
 +
*** Allows additional formats not previously supported to work with the native Linux implementation of SWT
 +
*** What kind of error message will be available on other platforms?
 +
*** Need to confirm the API doc is updated to indicate what formats are supported on what platforms. (Alex will take care of that in the javadoc)
 +
*** Has there been investigation into what later Java versions provide for image loading?
 +
**** No, could be done as part of investigating support on other platforms.
 +
*** Need to have an umbrella bug for the new functionality with additional children defects for the platforms that don't support the new formats. (Alex to open that)
 +
 
 +
 
 +
'''March 19, 2019''' - McQ, Lars, Dani
 +
* Dani
 +
** 4.11 on track - repositories and download page ready for tomorrow
 +
** Java 12 GA expected today
 +
** Will merge Java 12 work to master tomorrow or on Thursday
 +
** Will provide a Marketplace entry for Java 12 support for 4.11
 +
 
 +
 +
'''March 12, 2019''' - ???
 +
* Missing
 +
 
 +
 
 +
'''March 5, 2019''' - Tom, Alex, Dani
 +
* Dani
 +
** I will be away starting Friday and next week. No laptop ==> watch out for any 4.11 related issues
 +
** Tom, please update the status on the Equinox 4.11 plan
 +
** Tom: {{bug|544370}}: NoClassDefFoundError: org/apache/sshd/server/auth/AsyncAuthException from SshServ
 +
** {{bug|544833}}: Inactive committer cleanup for Platform for the 4.12 release
 +
*** Might be much more work since committer info from old portal is not available in the new PMI
 +
** Get rid of new indexer. Alex, not sure who from Red Hat mentioned it at EclipseCon Europe but there seemed to be interest to further work on this.
 +
*** Alex: Roland looked at it and could not see any benefit
 +
*** Current thinking: drop it, but Alex will double-check and report back in two weeks
 +
 
 +
 
 +
'''February 26, 2019''' - McQ, Tom, Alex, Lars, Dani
 +
* Dani
 +
** Issues with Mac signing
 +
*** McQ: we should ask the Foundation whether they can't set up a watchdog
 +
**** Dani: filed ({{bug|544915}})
 +
** Issues with JAR signing
 +
** Release on track
 +
** Prune inactive committers
 +
*** AGREED to do this like we did last year for Platform ({{bug|530200}})
 +
*** Lars for Platform. Tom for Equinox and Dani for JDT and PDE
 +
* Lars: move active committers to the list of contributors in the Acknowledgments
 +
** AGREED
 +
 
 +
 
 +
'''February 19, 2019''' - Tom, Alex, Dani, Lars
 +
* Lars: API removal announcement on cross project
 +
** AGREED: To send one mail per release for RC1 announcing all removals to reduce noise on the mailing list
 +
** In case of more important removal it can be announced individually.
 +
** Dani to open bugs for releases so it's handled properly.
 +
* Lars: Provisional API guidelines changes
 +
** Current approach with internal/provisional package names until API is stable is an issue because:
 +
*** It creates more work for maintainers to rename packages.
 +
*** It creates more work for adopters to change references once API is stable.
 +
** AGREED: Use the intended package name but mark it as x-internal until API is final. Lars will update the document.
 +
* Dani: End game plan posted
 +
 
 +
 
 +
'''February 12, 2019''' - Tom, Alex, Dani, Lars
 +
* Dani:
 +
** M3 next week.
 +
** Must start to work on IP log, release review and Endgame plan.
 +
* Alex: What's the future of ECF (not much happening there)? How feasible is it to replace ECF and HttpClient with new Java HTTP Client from Java 11?
 +
** Interesting to know, but unfortunately no resources to investigate this at the moment.
 +
* PMC decision regarding HttpClient for 2019-03: will ship what we have (4.5.5).
 +
 
 +
 
 +
'''February 5, 2019''' - Tom, Alex, Dani, Lars
 +
* Dani:
 +
** I-build contributed to 2019-03 M2, no complaints so far
 +
** Over 200 bugs for M3 with 2 weeks left, need to be looked at and target adjusted
 +
* Alex:
 +
** JIPPs are subject to update to new infra in the next few months. Releng JIPP is a matter of separate treatment.
 +
** As soon as most JIPPs (not Eclipse TLP only) are moved to new infra SWT will move to GTK 3.22 as a min version.
 +
** Sep 2019 release is the earliest possible for SWT GTK min version bump.
 +
* Tom:
 +
** equinox.framework and bundles git repositories merge
 +
** APPROVED if history is preserved
 +
** Alex: new name of repo should be eclipse.equinox.* not rt.equinox
 +
** After merge Alex takes renaming rest of equinox repos with webmaster
 +
* Lars: Fosdem
 +
** IDE and Free Tools room
 +
** Netbeans and IntelliJ talks and interest
 +
 
 +
 
 +
'''January 29, 2019''' - McQ, Tom, Alex, Dani, Lars
 +
* Alex: Java 11, should we move the build to Java 11?
 +
** Agreed to move the Tycho snapshots for testing and move back to Tycho stable after M3
 +
* Dani: This week is M2, we will contribute the Wednesday I-Build with some sanity checks
 +
* Dani: Having problems with the asynchronous JDT UI initialization {{bug|543935}}
 +
 
 +
 
 +
'''January 22, 2019''' - McQ, Tom, Alex, Dani
 +
* Alex:Felix SCR update
 +
** Tom: Orbit update to make felix.scr bundle imports non-optional
 +
** Missing compile warning in the first build - not clear why it happened
 +
* Tom: Equinox tests move from runtime git repo
 +
** Needed because tests are not run on gerrit and not findable for contributors
 +
** Alex: how easy it is to find which one are for equinox and which should stay in runtime repo
 +
** Tom: to open bug with details
 +
 
 +
 
 +
'''January 15, 2019''' - McQ, Tom, Alex, Lars, Dani
 +
* Dani
 +
** We shipped 4.11 M1 last Friday - no issue so far
 +
** Created release record for 4.11 (mandatory to be there by 4.11 M1)
 +
 
 +
* Lars: {{bug|543218}} was a severe regression in M1
 +
 
 +
* Tom
 +
** Chatter about update configurator {{bug|542706}}
 +
** Alex: update configurator still there but not hooked into Equinox/p2/PDE anymore
 +
** Alex and Lars to update the bug report
 +
 
 +
 
 +
'''January 8, 2019''' - Dani, ?
 +
* We had a meeting, no notes were taken
 +
 
 +
 
 +
'''December 18, 2018''' - McQ, Tom, Alex, Dani
 +
* Talked about potential release train delay due to JAXB - nothing we have to worry about
 +
* Next call on January 8
 +
 
 +
 
 +
'''December 11, 2018''' - Tom, Lars, Dani
 +
* Dani: 4.10 looks good, work for 4.11 is open for development
 +
* Dani: Will add Bugzilla milestones
 +
* Tom: Will update Equinox to Java 8 soon will need to support Java 8 for quite some time in the future
 +
 
 +
 
 +
'''December 4, 2018''' - McQ, Alex, Tom, Lars, Dani
 +
* Dani away on Thursday and Friday.
 +
** Please keep an eye on RC2.
 +
** Please watch the release review ({{bug|541666}}).
 +
* Dani: 4.10 on good track but investigating last minute {{bug|542090}}.
 +
* {{Bug|541689}}: What needs to be done to add OpenJDK on Windows as a reference platform?
 +
** We will add this for now, but for 4.11 we will query the community which runtimes are actually used and/or tested.
 +
** Alex: We need to specify from where the OpenJDK runtime comes from.
 +
* Tom: When do we push 4.10 to Maven central?
 +
** Dani: ask on Releng list.
 +
* Alex: Help Center issue. What's the state?
 +
** Tom will investigate this a bit more this week. Probably no fix for RC2.
 +
 
 +
 
 +
'''November 27, 2018''' - Alex, Dani, McQ, Tom
 +
* Mailing lists
 +
** Discussion on merging various mailing lists {{bug|541508}}
 +
** Merge all platform-x lists into one (platform-dev?) list, except the current platform-releng-dev will remain separate.
 +
** merge all jdt lists into one list (jdt-dev?) list.
 +
** Considered merging the equinox-dev and p2-dev into one list (equinox-dev?), will leave separate for now because the two groups still seem to have distinct topics to discuss (even if the traffic is relatively low).
 +
** What is the target usage of the lists?  For the user community to ask questions or for the developers to have discussions around development of Eclipse?  At this point the traffic is low and the PMC does not see a need to discourage usage by the user community to ask questions.
 +
** Before merging we need a way to have responses sent to messages sent to the old archived mailing lists which directs them to the new list.
 +
* Rules for freeze/endgame
 +
** Consider allowing the gerrit reviews to act as the way to record approval by a member of the PMC and/or project lead instead of requiring that to be flagged in the bugzilla.  If the gerrit review was done by someone other than a member of the PMC or project lead then there still needs to be some record in the bugzilla that the required approval of the PMC or project lead was done.
 +
 
 +
 
 +
'''November 20, 2018''' - Alex, Lars, Dani, McQ
 +
* Dani reminded the team to update plans so we can do release review
 +
* Dani working on IP review
 +
* M3 this week; then API/feature freeze next week; then one more week and we’re done
 +
* JDT Code Mining went in today; test!; disabled by default
 +
* Demonstrated proof of concept, empty shell running on GTK4 alpha
 +
* {{bug|541307}} needs to be investigated; could be a blocker for PDE or Equinox
 +
* Seems to be general consensus that code clean-up is more important than maintaining git blame usefulness
 +
** Ref: https://www.eclipse.org/lists/eclipse-pmc/msg03568.html
 +
 
 +
 
 +
'''November 13, 2018''' - Alex, Lars, Dani, McQ
 +
* Plan update 4.10 plan update 1 from Dani
 +
** As Foundation still provides only SLES 12 we might still have to list it
 +
** SWT team tests on SLES15
 +
** Details: {{bug|541074}}
 +
* Train name update from Dani: We can keep "our" Eclipse IDE name, foundation dropped the idea of adding an additional identifier to the "Eclipse IDE" brand.
 +
* jsch - Dani checked if preferences are used and could not find any usage, Dani did not yet contact Thomas as JGit did not make any progress in the area. Alex did update Equinox.
 +
* Cherry-pick as strategy in Gerrit
 +
** {{bug|541021}}
 +
** Dani does not like the idea and voted against it
 +
** Alex: Linux tools and CDT are using Cherry-pick
 +
 
 +
-> Everyone agrees that the build infrastructure is getting worse and that we should find ways to speed up the build, Dani will follow-up with the foundation on that
 +
 
 +
 
 +
'''October 30, 2018''' - Alex, Lars, Dani, Tom
 +
* Dani: Update on release train name
 +
** Foundation accepts "Eclipse IDE" as long as the scope is clear
 +
** Foundation can use another name when the Eclipse IDE is shown along with other IDEs, e.g. Che. Possible name could be "Eclipse Classic IDE"
 +
* Increase major segment when deleting deprecated API
 +
** Discussed last year on [https://wiki.eclipse.org/Eclipse/PMC/Minutes_2017 October 10, 2017] but did not make an official decision
 +
** Disruption would be huge
 +
** Today we decided unanimously that in general we will NOT increase the major version when removing deprecated API
 +
*** There might be cases/bundles where we might be more aggressive
 +
 
 +
 
 +
'''October 23, 2018''' - No meeting due to EclipseCon Europe
 +
 
 +
 
 +
'''October 16, 2018''' - Alex, Lars, Dani, McQ
 +
* We all agreed that at this point, the right thing regarding renaming the project is to do nothing.
 +
* Delivered 2018-12 (4.10) M1 on Friday. No feedback on that so far. Train to deliver this Friday.
 +
* Dani gave an update on the work for the EDP.
 +
* Alex together with Mickael will make sure that the Unconference session at EclipseCon will be split into interest groups after initial discussion.
 +
 
 +
 
 +
'''October 9, 2018''' - Alex, Lars, Tom, Dani, McQ
 +
* 4.10 plan and release record published
 +
* 4.10 M1 looks good, low number of bugs
 +
* Project naming - pushback in planning council and there will be no change until Eclipse Foundation provides the document describing the rules names should comply with
 +
* Performance tests
 +
** Lars: jdt.core performance tests not running
 +
** Dani: performance tests running (mostly) since Photon, most work done by Sravan
 +
** Dani: results look sane but need to be checked thoroughly for some time to ensure all the infra runs proper
 +
** Alex: SWT perf tests for 4.9 properly shown improvement in startup initialization
 +
 
 +
 
 +
'''September 18, 2018''' - Alex, Lars, Dani, Tom, McQ
 +
* Release looks ok, respin was required
 +
* EPL 2.0 conversion was done for the Eclipse SDK but not for the e4 sub projects
 +
** Lars: e4 repository have not been converted
 +
** Dani: JDT, Equinox, PDE and Equinox have been converted so the Eclipse SDK has been converted
 +
** Lars plans to convert the e4 spies
 +
** Dani will inform Wayne/ Webmaster about the EPL 2.0 migration of the Eclipse SDK
 +
* Alex suggests deleting the long dead e4 repository like e4 JDT (no commits for 5 years, they should be archived) -> Alex to announce on e4 mailing list
 +
* Lars reports that SAP might get more involved, he delivered a workshop for them and they have very skilled developers which hopefully will contribute to the platform.
 +
* Dani: JDT will create a common plan for its components under https://wiki.eclipse.org/JDT/Plan/4.10, similar to platform.
 +
 
 +
 
 +
'''September 11, 2018''' - Alex, Lars, Dani, Tom
 +
* Dani: 4.9 Review is done and passed
 +
** Release is looking good for final phase
 +
** RC2 is done - no planned changes left for 4.9
 +
** Moving on for 4.10
 +
* Alex: 4.9 is in good shape now
 +
** Had last minute issues that almost made us miss RC2 date.  Felix SCR change in qualifier caused meta-data to be regenerated because of an upgrade in Tycho.  Tycho now published generic OSGi capabilities.  This lead to cases where Felix SCR would get included without equinox.ds.  That lead to issues with activating Felix SCR.
 +
** Tycho is fixed now to handle starting of Felix SCR, worked around issue for 4.9
 +
** For 4.10 dropped 32-bit and gtk2 now
 +
* Tom: org.eclipse.equinox.ds to be removed.  Decided to keep equinox.ds in the repository as part of the Equinox SDK feature, but it will not be shipped as part of the Eclipse SDK features.
 +
** Need to make sure other areas can handle equinox.ds missing (e.g PDE)
 +
* Dani: Informs us if the team attending Eclipse Day and EclipseCon events.
 +
* Via email: Pinging robot for bugs will be activated for all subcomponents of the Eclipse top level project, as it is currently not possible to activate the robot for only a sub-component.
 +
 
 +
'''September 04, 2018''' - Alex, Lars, McQ, Tom
 +
* CQ in JDT was approved to create code duplication. Lars asked what caused that.
 +
** Delay in JDT review, biggest blocker is still not in JDT
 +
** Large change, agreed with Dani to get review priority review in 4.10 from the JDT team
 +
* Alex/Tom - 4.9 RC2 status
 +
** Looks good, no know bugs
 +
* Lars: Activate autoclose for Platform bugs?
 +
** Lars argues that platform and e4 has too many old bugs so people are not looking at them
 +
** McQ is against autoclose
 +
** Agreed by al to enable "Pinging the user if this problem still exists" for selected components (Platform/UI) and see how much feedback we get.
 +
** Email send to McQ, Tom and Alex if we could also add e4 to that pinging list -> all agreed to enable it also for e4 bugs
 +
 
 +
'''August 28, 2018''' - Alex, Lars, Dani, Tom
 +
* Reminder - RC1 this week, RC2 next week
 +
* Dani on vacation starting this Friday
 +
* Dani will submit the release review and IP log before going on vacation (Wayne approved this)
 +
** Alex will handle all things that come up with that
 +
* EPL 2.0
 +
** Lars: almost done - few pending patches
 +
** Alex: boring work - hopefully EPL 3.0 only on 10 years
 +
 
 +
 
 +
'''August 21, 2018''' - Alex, Lars, Dani, Tom
 +
* Reminder - M3 this week RC1 next week
 +
* Milestone discussion
 +
** M2 and M3 are too close together.
 +
** Delivering M1 and M3 instead provides better space for the development team.
 +
** M1 will be short, but still should give us 1 month time to deliver. 
 +
** For 4.10 we will try delivering M1 and M3 milestones.
 +
* Dani will look at submitting the release review and IP log early since he will be out during the week they are due.
 +
** Alex will cover if that cannot be done
 +
* EDP update - Arch council is making changes ... should ease some things. 
 +
** For example, decoupling the project review from a project release.  Project releases still will require IPLogs
 +
* Lots of bugs still open against 4.9.
 +
** Team needs to adjust milestones accordingly before 4.9 is done
 +
* Java 11
 +
** Work almost done to support Java 11.
 +
** Initial support will be delivered in Marketplace only (no 4.9a planned).
 +
** First official release with Java 11 support will be 4.10
  
<hr/>
 
'''Oct 11, 2016''' - McQ, Dani, Lars, Alex, Sergey
 
* Dani: '''Neon Update 2 Endgame Plan sent''' - thanks for the feedback
 
* Sergey: We should talk about our release process.
 
** McQ asked Sergey to start the discussion via e-mail
 
* McQ: What do you think about Devoxx and Eclipse Converge
 
  
<hr/>
+
'''August 14, 2018''' - McQ, Alex, Lars, Dani, Tom
'''Oct 4, 2016''' - McQ, Dani, Martin, Lars, Alex, Sergey
+
* Changing our test framework to use JUnit 5 always ({{bug|531057}})
* Dani: '''Neon Update 2 Endgame Plan''' - working on it
+
** In progress: suites are running, but some tests are aborting
* Dani: '''Release Review'''
+
** Reports should be fine in next build
** In the past, features were not announced - now for 4.6.2, features + release review must be in by RC1
+
* Release review and IP log will be coming soon
** Will do the minimum necessary / required by EMO, for Update Releases.
+
** M3 next week, then one week for RC1 and one week for RC2
* Lars: '''p2 merge into Equinox status''' -
+
** A lot of bugs in the backlog that need to have their milestone re-assigned
* Sergey: '''Logistics of dealing with Service Releases'''
+
* Once we get a few releases under our belt using the new process, we should do a retrospective looking at burn rates, quality, etc.
** Managing version increments is very fragile and error-prone
+
** The good news is we no longer have to maintain two streams and back port changes.
*** Discussion already happened, see {{bug|499164}} -- we'll not increment minor versions on backports even if API is added
+
* Support for J9 shared classes merged into Equinox
*** '''AI Dani''' send a note out to eclipse-dev again
+
** Will not update launcher to specify them for this release
** '''New & Noteworthy / Features for Update Releases:'''
+
** Need to provide doc on how users can specify the options themselves (via eclipse.ini)
*** If there's new features, there must be a New&Noteworthy for users (everyone agrees)
+
* McQ away for two weeks
*** What about doing two feature releases per year with one service release each ?
+
**** Dani: Not having features in "some" releases would defeat what the Community wanted
+
**** Alex thinks that allowing features every 6 months would calm down most demand for new features
+
**** PMC Review of feature backports worked fine so far
+
**** '''RESOLUTION''' Will not change the process before having it settle a bit
+
***** McQ would love to see a single development stream all the time ...
+
*** Would the Generic Editor be acceptable in a release before June 2017 ?
+
**** Tentatively yes, it's a separate bundle not affecting other code, it matters to the Community, so why not...
+
**** Martin: OK, but what about newly introduced API ... would it be declared "provisional" initially ?
+
**** Dani: There's no such thing as "provisional API". Teams who decide on backporting must also decide on API.
+
**** Sergey: CDT has done full feature release every quarter for some time now and hasn't screwed up API...
+
**** Martin,Lars,Sergey: What about marking "fresh" API as "@noreference under construction" until it's hardened...
+
***** McQ: Then declare APIs as official only once a year ?
+
***** Wouldn't want to tie to a yearly cycle again ... but then we're back to the Version Numbering discussion...
+
***** '''AI All''' continue discussion on mailing list or next week.
+
  
  
<hr/>
+
'''August 7, 2018''' - McQ, Alex, Lars, Dani
'''Sep 27, 2016''' - McQ, Dani, Lars, Alex + Sergey Prigogin (guest)
+
* Dani: outstanding plan topics:
* Discussion about PMC upstaffing
+
** Target platforms should use SLES 15 (instead of 12)
 +
*** Dani to talk to SWT team about this
 +
** Remove RHEL 7.4 (current is 7.5)
 +
*** all agree to this
 +
* McQ to send note about Windows 32-bit EOL
 +
* Alex: ASM breakage in master — issue in Orbit; should be in next iBuild
 +
* Dani: shipped M2 last week everything went well
  
<hr/>
 
'''Sep 20, 2016''' - Martin, McQ, Dani, Lars, Alex
 
* Resources Leadership - '''AI Dani''' reach out to Szymon
 
* PMC upstaffing: Focus on large installs; UI Freeze monitor, code cleanup, solid solutions, focus on code reviews
 
* Dani: '''Java 9 Moved to July 2017''' - AI Dani talk to the Planning Council, proposing an "Update 1" in July
 
** Better for consumers, available via "just update", though little bit extra work (CQ + Release Review)
 
** Schedule looks still aggressive when looking at specifications; need to keep the team motivated
 
* Dani: '''SelectionListener SWT Change''' - reverted for M2 since more clients were affected than expected
 
** Proposed change turned out to be source-incompatible - will look at a different approach
 
  
<hr/>
+
'''July 31, 2018''' - Dani, Tom, Alex
'''Sep 13, 2016''' - Dani, McQ, Lars
+
* Dani: For quality reasons, suggests to have an official M3 (August 24) since after RC1 (August 31) we will only have 1 week left
* Upstaffing the PMC
+
** all agree to this
* Build failures due to an SWT Change
+
* Dani: Initial 4.9 plan is ready but no feedback so far
  
<hr/>
 
'''Sep 6, 2016''' - Dani, Lars, Alex, Martin
 
* Dani: Thanks for approving Noopur
 
* Dani: Java Language Server Proposal - at the Foundation, will be called "JDT Language Server"
 
* Dani: RC4 - Fix for an Equinox p2 issue, only known issue being fixed, looking good
 
* Dani: Looking at the generic code editor, would prefer moving some things to M3 (talking to Sopot and Mickael)
 
* LTS: Market for paid fixes on old versions not quite as good as expected
 
* Release Reviews: When is a feature considered an "important feature" ?
 
** Important Features require a full release review thus lots of effort, avoided for Neon.1
 
** '''AI Dani''' discuss in Planning Council call tomorrow
 
  
<hr/>
+
'''July 10, 2018''' - McQ, Dani, Tom, Alex
<strike>Aug 30, 2016 - No topics</strike>
+
* 32 bit support
 +
** Harder to find 32 bit JVM
 +
** Devs are not supposed to work on 32 bit OSes anymore
 +
** Agreement to drop support for 32 bit but keep sources and build support for some period to give people time to bring it back
 +
* GTK 2.x support in SWT
 +
** Planned to be removed for 2018-12 release
 +
** Needed so GTK 4.x port can be started prior to 4.0 release so SWT needs a taken into account from GTK devs
 +
** Bugs are not being looked at for some time already and GTK 3 has been the default for years now.
 +
* 4.9 release
 +
** M1 is this week
 +
** Platform will contribute I-build with some basic testing but not the full milestone which is to be done for the only milestone which is to be delivered for M2 of the SimRel
  
<strike>Aug 23, 2016 - No topics</strike>
 
  
<hr/>
+
'''June 12, 2018''' - McQ, Alex, Tom, Lars
'''Aug 16, 2016''' - Dani, Martin, Lars
+
* RC4a looks good; hidpi fix is in place
* Dani will not always be available next two weeks (Eclipse Summit India and IBM Bangalore team visit)
+
** no plans for further builds at this point
** Please split the load on +1'ing backport/API requests - please do review the code and set the pmc+1 flag
+
* Dani: '''{{bug|498106}} Oxygen Plan'''
+
** Agreed by all so far, including removal of REL6 as a reference platform
+
** Individual subproject Wikis look pretty consistent now
+
** UNIX Platforms (Solaris,AIX,HP-UX) have been removed for M1
+
*** PPC-Linux Releng was also removed but accidentally (due to a hardware failure), will be restored for M2.
+
** No consensus on Ubuntu yet - will keep 14.04 in for now, consider taking out on the next update
+
* Dani: '''{{bug|499164}} Version Numbering for Neon.1'''
+
** The original "+5" or "+10" proposal showed some issues:
+
** Update with skipping would propagate to features; no tooling; no real benefit of semantic versioning
+
** '''AGREEMENT''' to keeping using the status quo for now ("allow small updates even with micro uprev only")
+
* Lars: '''p2 pending patches'''
+
** '''AI Dani''' send E-Mail to Tom - suggest reviews or merger p2 back to Platform
+
* Dani: '''{{bug|499399}} Eclipse Infrastructure Stability'''
+
** Denis is looking at it - maybe too many requests coming in ?
+
* Lars: '''e4 spy and wizard migration to PDE'''
+
** Dani: Are wizards e4 specific, or could they be used with JFace ?
+
** New SWT Layout Spy should go to SWT, rather then keeping in PDE's Build
+
** Some spies usable also in RCP Apps - for example the e4 model spy - 6 independent projects, dependency on emf.edit
+
*** Looks like a big extension to PDE -- consider some consolidation and cleanup (tests, String externalization, ...)
+
*** '''AI Lars''' to check if contributors would be willing to clean up as discussed, then moving into pde.ui would be fine.
+
<hr/>
+
  
'''Aug 09, 2016''' - Dani
+
'''June 05, 2018''' - McQ, Alex, Tom, Dani, Lars
* no one joined - had private conversation with McQ later
+
* Dani:
** '''guys, please announce when you can't join. I can make better use of my time than waiting for you in the call ;-) - thanks.'''
+
** Image limit for help should be increased? -> Not covered in the call
<hr/>
+
** Will most likely not be able to join the next call
 +
* Alex:
 +
** Support only last LTS version of Linux?
 +
*** Agreement to drop old LTS versions for 4.9 but not to change the target environment for 4.8
 +
** Dropping big Endian -> we all agreed to drop it, MQ found the email to cross, so we can remove it
 +
* Lars:
 +
** Update to EPL 2.0?
 +
*** change of about.html is trivial
 +
*** requires version updates of MANIFEST.MF and pom.xml
 +
*** Script for source update look good, Lars checked manually lots of files
 +
*** Coordindate with Jay or Noopur for the JDT UI update
 +
*** Dani suggested to announce such work via the mailing list so that everyone is aware of the work
 +
 +
** Only one N&N per release? -> Agreed to have one document per release
 +
** Do we get a name for Photon+1 -> Dani: Our SDK is called 4.9, splash screen will only be month year, planning counsil still discussing
 +
** Include Tips and Tricks in the SDK -> Not covered in the call
  
'''Aug 02, 2016''' - Dani, Martin, Alex
 
* Dani: New [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_7_draft.xml Oxygen Plan Format]
 
** '''AI Dani''' ask Denis about aggregating the Sub Wiki's into the master page
 
* Alex: SWT Fragments for ARM64 etc
 
** Tycho doesn't support auto-selecting fragments - in contact with Jan and Tobias
 
** Dani: Would like to revert changes - don't want to punish people who are not interested in fragments
 
** Not really an SWT problem, so editing .target files would be a clean solution
 
** Will probably go with empty (dummy) fragments without natives, as that's the simplest solution
 
* Dani: SWT team - Lakshmi going to Sweden, will not be available until end 2016
 
** Arun is mostly back, Sravan is now on Releng
 
** Need to push further on building at the Foundation!!
 
** Alex: Getting CentOS for building ... but test machines are on SLES11, which is too old, will need at least SLES12
 
*** Dani: Will need an owner at the Eclipse Foundation to ensure this proceeds ! Alex agreed to further drive this.
 
* Target Env: Dropping REL6 -- reference platform for testing will only be REL7 (though will continue to run on REL6)
 
** Reducing support level this year, in order to prepare for only supporting GTK3 next year
 
  
<hr/>
+
'''May 29, 2018''' - Alex, Tom, Dani
 +
* Dani:
 +
** Uploaded IP log
 +
** Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck
 +
** Finalized Photon plan
 +
** Sent Release Review material for approval to PMC mailing list
 +
** RC3 looks good so far
  
'''July 26, 2016''' - no meeting
 
  
'''July 19, 2016''' - no meeting
+
'''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"
  
<hr/>
 
'''July 12, 2016''' - McQ, Lars, Alex
 
* Dani: Hackathon summary
 
  
<hr/>
+
'''May 15, 2018''' - Alex, Tom, McQ, Lars, Dani
'''July 5, 2016''' - Lars, McQ, Alex, Dani, Martin
+
* GDPR
* Lars: SWT move to Java 8
+
** audit did not report any issues on our project pages
* Alex: Initial builds of GTK 2.24 for AIX - planning to bump minimum GTK version to 2.24
+
* Opening development for 4.9
** Will remove non-cairo drawing, this is where most of the breakage happens
+
** Will branch RC2 and update master with required Releng work
** Ubuntu 12.04: 2.24.10 / 3.4.5
+
** master will be open after RC3
** RHEL 6: 2.24.23-6
+
* EPL 2.0
** AIX, HP-UX, Solaris ? -- Oxygen will only focus on Linux, Windows, Mac
+
** No plans to do anything for 4.8
** Secondary Platforms: Not built on EF Hardware, but interested parties can contribute binaries
+
** Lars will look into it
** Trying to support Platforms which can't move up to modern GTK at a similar pace as Linux is hard
+
** Ideally we gradually move to 2.0
** '''AI Alex''' write up a message to the Community
+
* Lars: {{bug|486961}} extending the Eclipse Text Editor
+
** Dani: Text Editor must remain unchanged, but feel free to provide a new different code editor
+
** https://bugs.eclipse.org/bugs/show_bug.cgi?id=496114#c7
+
** Not against adding extension points ... but having the standard text editor adopt those is a no-go
+
* Dani: Build, and Hackathon
+
  
<hr/>
 
'''June 28, 2016''' - McQ, Martin, Alex
 
* Discussion about Language Server Protocol
 
** MS sponsoring hackathon in Zurich, Dani expected to go there
 
** The protocol has an Open Source license, but there is no Open Source Governance ... who owns the specification?
 
  
<hr/>
+
'''May 8, 2018''' - Dani, Alex, Tom, McQ
'''June 21, 2016''' -  
+
* 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
  
<hr/>
 
'''June 14, 2016''' - Dani, McQ, Martin, Lars
 
* McQ: '''Mattermost / Slack''' for communication
 
** not much different than newsgroup or IRC, but very dynamic when everybody is on it
 
* Lars: '''Master is Open'''
 
** Dani: Simple story - if we do need an emergency build we would create the maintenance branch on demand based on the tag
 
** Only limitation: We can't update the parent pom's at this time
 
** Don't have tools to check if the MANIFEST.MF needs to update - only API Tooling for API changes, but nothing for micro changes ({{bug|360703}}) is open to improve that)
 
** We do have an alert if there's no version/source change but the binaries changed (e.g. due to a compiler update) but that's not in the workspace
 
* Lars: '''Upgrade SWT to Java 8 for Oxygen ?''' - to be decided by the SWT team, the PMC is OK with the update if the SWT team decide so
 
* McQ: '''Language API -- Overlap between Orion and Che''' (from [https://dev.eclipse.org/mhonarc/lists/ide-dev/ ide-dev] mailing list and {{bug|496114}})
 
** The protocol is pretty big, but well documented - looks like an improved version of Flux
 
** The protocol is generic, implementations need to be specific -- some implementations already ongoing (Javascript)
 
*** People start working on editors hooking up to the protocol -- does it make sense building a JDT Language Server ?
 
** The tricky part is, that the Che workspace model is very different than the Eclipse workspace
 
** How to create a small lightweight server that would scale -- one workspace per user may not scale
 
*** At the beginning, it would be less powerful than JDT today since context would be lacking
 
*** But the direction is very interesting ... though maybe too many people are implementing the same thing right now
 
* Dani: '''What goes into the Neon Update Releases'''
 
** as discussed on May 17 (see below): Must be in master first, consider for backport after that
 
** '''AI: Dani''' will prepare a note
 
* Dani: '''Using Sound in Eclipse'''
 
** Eric Rizzo uploaded a feature to provide different sounds for successful or failed JUnit tests (see {{bug|496003}})
 
** Martin: CDT has allowed sound for breakpoint actions since long
 
** Lars: Moving the Mylyn notification framework to Platform UI was on the plan already, now considered for Oxygen
 
** McQ: Every Platform has an OS-Level Notification system so '''that''' should really be leveraged
 
** Martin: Mylyn notifications can be "active", can OS notifications also be active ? - McQ thinks yes
 
** Could work on SWT implementation of host platform notifications in parallel to pushing down the Mylyn API
 
** Request on specific JUnit sounds not yet decided.
 
  
'''June 7, 2016''' - Dani, McQ, Alex
+
'''May 1, 2018''' - cancelled due to public holiday in most Europe
* no topics
+
  
<hr/>
 
'''May 31, 2016''' - Dani, Martin, Lars, McQ, Alex
 
* Dani: '''IP Log'''
 
** The tool did not work, but it was manually submitted and approved
 
** In previous years, some people wanted the IP Log to not be so publicly visible, so now only project leads can generate and submit it
 
* Dani: '''Release Review'''
 
** Reply to the public E-Mail with comments or +1
 
* Dani: '''Update Jetty to 3.9.3'''
 
** Consensus to update - Jetty team working on fixing their update site
 
* Dani: '''RC4 Status Update'''
 
** Cooling down - maybe 2 fixes from SWT, 1 in Platform/Text Search, and the approved doc fix for deprecating the mac command
 
  
<hr/>
+
'''April 24, 2018''' - Dani, Lars, Alex, Tom
'''May 24, 2016''' - Dani, Lars, Martin
+
* Target environments
* Dani: '''IP Log Generator''' - New version is unable to deal with Eclipse Project, Wayne is working on it
+
** We will keep Java 8 and 10 and remove java 9 from the list
* Dani: '''Release Review''' - Deadline next week (June 2)
+
** remove JVMs as soon as they run out of support from target environments  - AGREED
* Dani: '''Deprecation Request from Brian'''
+
* javax.annotation
** Command org.eclipse.ui.cocoa.fullscreenWindow -- all PMC agree on the deprecation although late, since it only affects docs
+
** Version  shipped is quite old, should we update it to newer version
* Dani: '''Copyright End Date'''
+
** Update to latest standalone release to be tried
** '''AGREEMENT''' to no longer require updating the end date (though committers are still ALLOWED to update it)
+
** Alex to try to drive this through
** Will no longer run the automated copyright tool (actually haven't run it the past 3 releases)
+
* Notify cross project about removal of ee modules from the JVM
** Will live with the source code notices being inaccurate / incomplete - the accurate state is in Git
+
** 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
** This is acknowledged to not be ideal, but the best compromise we can come up with since "bulk changes" are not OK
+
** Dani will send a link to the JEP containing detailed information
* Dani: '''Neon Status'''
+
* Contribution guidelines
** Java 9 launching - affects all Java consumers, not clear yet what Oracle will do, no plan changing Equinox/Launcher at this time
+
** 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/>
 
'''May 17, 2016''' - Dani, Lars, Martin, Alex
 
* Dani: '''{{Bug|475184}} Neon Plan Update 2'''
 
** Windows 10 and Ubuntu 16.04 will be added as "active" Platforms that people do work on
 
** SWT would like to remove Windows 8 and Ubuntu 12.04 from the list of reference Platforms
 
*** Alex: Ubuntu 12.04 has GTK 3.10 which is hard to support
 
**** Correction (Markus): Ubuntu 12.04 has GTK 3.4.2. Ubuntu 14.04 has GTK 3.10.8
 
*** Message is clear: "Supposed to run on older Platforms, but these are the primary ones" - including last 2 LTS ones
 
** Agreement to keep Windows 7 and remove Windows 8
 
** '''AI Dani''' to check if SuSE 11 is right (12 been out since 2 years)
 
* Dani: '''Copyright End Date''' - EMO: To be decided per project
 
** IBMers will have to continue updating the copyright end date, regardless of what other companies do
 
** Copyright tool: Only the person who made a change is allowed to update the Copyright notice
 
*** gray area: actually fixing the date can be considered a change
 
** Alex is in favor of consistency across the project
 
* Dani: '''Policy for Neon.Update Releases''' - What to allow in, which rules to apply on the endgame
 
** Martin: Fact is, that the Update stream is built less often, and thus also tested less often
 
** Rule: Any fix or feature must be in master first (and may be backported thereafter)
 
** Will want "some" features in Update, but probably not all of them - '''decision''': discuss feature by feature at PMC
 
** Stakeholder who's interested in a backport must send a quick note to the PMC (just like for API change requests)
 
** In case too many requests should come in, could still discuss updating the procedure
 
* Dani: '''Neon RC2 Builds Update'''
 
** Currently looking good, but latest Java 9 Launchers broke the Annotation support - investigating
 
** Quality generally looking good - "Stock GTK3" very stable now
 
** GTK3 on SuSE, Fedora looking much better than Mars (at least with a GNOME shell)
 
** Lars: {{bug|493477}} detached editors broken on GTK2 nominating for RC
 
  
<hr/>
+
'''April 17, 2018''' - Dani, Alex, McQ
'''May 10, 2016''' - Dani, Martin, Alex, McQ
+
* On Java 11...
* Dani: '''Policy for what should go into Neon.Update Releases'''
+
** We are actually shipping the javax annotation support
** Would like to be more flexible than in the past - discussion point for next week
+
** Java 11 is working in 4.8, but isn't in 4.7.x
* Martin: '''RHEL7 -- GTK3 versus --launcher.GTK_Version 2'''
+
*** Tom Watson is investigating why it is not working 4.7.x
** GTK2 rendering still much more reliable than GTK 3 - forced to release commercial software with the GTK2 fallback for now
+
*** Drawback: Even with MATE desktop using GTK2 (for accessibility), the Browser widget webkitgtk2 is not easy to get since not in the official repos
+
** Alex: Desktops are moving faster - adopting change very quickly - cannot keep up with the investment that the Community currently makes in SWT
+
*** Heavily limiting what we support looks like the only viable approach at the moment...
+
*** There's 2 big groups of bugs: (a) "Next" version of GTK, and (b) "Old" version like Ubuntu 13.04 which has 3.10 - can we limit support to "latest" ?
+
*** Martin: Need "LTS" Linux (RHEL 7, RHEL 6, Ubuntu 12, 14 - soon 16).  
+
** Alex: Gnome people have come up with a "Container environment" for GTK - could ship Eclipse that way ?
+
*** Limitations: Updates must come through this application - already using Gimp from such an environment
+
*** Might be able to deliver Eclipse that way next year (Oxygen)
+
  
<hr/>
 
'''May 3, 2016''' - Dani, Martin, Alex, McQ
 
* [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02598.html Brian's request on the PMC list]
 
** McQ: Why would we care about adding small enhancements in RC1 when we should focus on testing and critical fixes
 
** Dani: Two parts in the change - the original one (approvable), but another change also sneaked in (enable the prefix search) - not approvable
 
** Alex: People don't want to wait for getting in an improvement...
 
** McQ: OK for adding as feature to Neon.1 , but Neon.0 should be focused on bug fixes
 
** Keep in Gerrit for now - Neon.1 stream is typically opened when no new changes are expected. Rebasing is relatively easy from Gerrit.
 
** '''ACTION''' McQ to -1 and argue why.
 
  
* Alex: '''Update on Accessibility'''
+
'''April 10, 2018''' - Tom, Dani, Lars, Alex
** broken since GTK 3.8 where accessibility is no longer a module but shipped with GTK itself
+
* Discussed {{bug|533390}}: Eclipse does not launch with Java 11
** due to that, the way accessibility is implemented is totally different - no more factories - experimenting with possible approaches
+
** Discussing the addition of Eclipse to their test infrastructure, at a meeting a month from now
+
*** and even so, not sure how well accessibility is tested in GTK itself
+
** Launching with -gtk_version 2 is not a workaround, because the v2 GTK doesn't register as an accessible application in newer desktops !
+
  
<hr/>
 
'''April 26, 2016''' - Dani, Lars, Alex, Martin, McQ
 
* Mickael's API change request ... tried to address feedback from Markus but then got no additional feedback
 
* Alex: '''Accessibility''' - broken on recent GNOME and probably others
 
** Accessibility is important. Have reports from users who say "Eclipse works for them"
 
** McQ: Need to keep some focus and look at what we can do for Neon.1
 
* Alex: '''Platform.ui generification of project'''
 
** Dani: Won't get a consistent story when done piecemeal - needs to be done "per framework" and not necessarily "per plugin"
 
** McQ: It's a huge effort - enough by itself for one whole release !
 
** Dani: If a meaningful separate unit is found that can be done, but things like e.g. LabelProvider, ContentProvider and TreeViewer can't be done isolated
 
** Lars: If a smaller unit of generification work is possible, that's permitted when somebody signs up for the work and it has been discussed in the public
 
** '''ACTION Alex''' to prepare a message for review and then send that.
 
* Lars: '''Copyright discussion'''
 
** Not having the end date in the copyright notice makes the copyright invalid.
 
** The IP Advisory Board will discuss it again.
 
* Dani: '''Update on FEEP'''
 
** Paul not reached out yet
 
** A list now shows what's done or in progress - but no time
 
* Dani: '''Update on M7'''
 
** Last 4 builds failed due to infrastructure issues - Maven stuff could not be accessed
 
** Will try to enable cache on the build side and re-try until the cache is full
 
  
<br/>
+
'''April 3, 2018''' - Tom, Dani, Mcq, Lars
'''April 19, 2016''' - McQ, Dani, Martin, Alex (regrets: Lars)
+
* 4.7.3a update
* Dani: '''IP Stuff''' on Copyright Updates pinged the Lawyers but no update yet, need to wait
+
** 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))
* Dani: '''FEEP''' discussed on AC, People were sympathetic to our issues.
+
** Currently think we're done
** General direction that FEEP sponsored work is no different than other contributions
+
* Naming milestones
** Wayne took the Action Item setting up a meeting with Paul and interested parties.
+
** As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1".
** Website with ongoing FEEP still pending - Dani is tracking
+
** We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming.
* Dani: '''All PMC please review and +1 API requests''' when you find time
+
** McQ does review and typically ask question but not close enough to the code to +1
+
** '''AGREEMENT''' on "+0" votes to express "no objections but others should approve too
+
* '''Reviews vs. Features'''
+
** Alex: Badge System was quite successful at Fedora
+
  
<br/>
 
'''April 12, 2016''' - McQ, Dani, Martin, Lars, Alex
 
* Lars: '''Get rid of the Copyright Year Update Requirement'''
 
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485257#c13 bug 485257_c13] EMO: All information is in the git repos
 
** McQ: OK lifting the requirement but doesn't want wrong information in files .. get rid of all copyright years ?
 
** Dani: Replacing the end-date by "[see git]" might be an option
 
** '''ACTION''' McQ or Dani talk to IBM Legal, then decide next week
 
  
* Lars: '''{{bug|490012}} Remove Project Settings to force strictly compatible JRE'''
+
'''March 27, 2018''' - Tom, Dani, Mcq, Lars, Alex
** Example: When don't have admin rights on a customer machine, can't install anything
+
* Java packages for configured Java in workspace
** Dani: With the Gerrit Build Validation, the risk of getting unbuildable code is no longer there
+
** 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.
** Proposal: Project requests a particular JRE, but the workspace configures treating this as an error or warning
+
** JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
** '''DECISION''' to get rid of the strict error per project.
+
** JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
 +
** 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?
  
* Dani: '''{{bug|475934}} API Change on model processing order'''
+
--> 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
** Dani: Even if this fixes an issue, M7 is late in the game
+
** McQ: Does API specify the order of events? - No; only on internal method.
+
** McQ: Is this transparent to most consumers, or will 5% have to react in their code ?
+
*** Lars has a few customers hit by this, but had to do a few tricks to mitigate the issue;
+
*** Making the change won't break them, but they could now remove their workaround
+
*** Martin: Not a formal API change and feels like cleanup/polish - M7 as the "performance milestone" feels just right for this
+
** Dani: Can be convinced making the change now if it is widely announced; convinced that this will hit more people than helping
+
** '''DECISION''' to allow making the change and announce widely.
+
  
* Dani: '''FEEP and EMO Hiring Update'''
+
** Lars did review and test
** EMO working on website update to announce the work being done
+
** Dani - put all the code in the branch and produce a build and ask windows community to test it
** Didn't talk about the specific SWT issue around "FEEP should provide clean stuff rather than quick fix"
+
** Mcq - thinks it is a good idea
** Already agreed on hiring a person, communication will come in June/July
+
** 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.
  
* Dani: '''IDE-dev proposal'''
 
** People don't find our tips and tricks; suggestion to add to the welcome page
 
** Solstice L&F issue on old Browser
 
*** McQ: Eclipse is a developer tool, and developers run on current browsers ... OK if only old browsers are affected
 
*** OK if there is a way out (such as choosing a different Theme) - not blocking anyone.
 
  
<hr/>
+
'''March 20, 2018''' - Dani, McQ, Tom, Lars, Alex
'''April 5, 2016''' - McQ, Dani, Alex, Martin, Lars
+
* 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.
* Dani: '''FEEP Update'''
+
* Databinding generification should be done early 4.9, too late for Photon.
** Foundation pays Patrik Suzzi as a contractor to look at Platform bugs (triage, and fix)
+
* 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.
** Will focus on critical / blocker bugs initially, or bugs already tagged by committers for 4.6 M7 and 4.6
+
** Mickael Barbero still quite involved in Releng - Foundation looking for Releng replacement so Mickael can develop (already reviewed autosave - but might be on vacation at the moment)
+
* Dani: '''Solaris 32-bit'''
+
** Will provide Solaris 64-bit binaries, but stop building Solaris 32-bit with Neon
+
** Open question: what does this mean in terms of GTK versions ? (GTK3 would be nice)
+
*** Alex may start asking questions as soon as the binary fragments are in the repo
+
** McQ: Windows 32-bit is still active - future change probably tied to
+
* Dani: '''New Solstice Welcome'''
+
** Some issues with Logo, sometimes it's there sometimes not; Brian working on it, Solstice will become the new default in M7
+
** Currently, ONE product logo must work on all Themes - bad design - probably to be changed
+
** McQ: Do we mirror the welcome for BIDI ? (Dani thinks yes, saw bugs come along)
+
* Alex: '''FEEP Process Discussion (around Themed Scrollbars)'''
+
** "Scrollbar Theming": Contractor doing work without SWT committers knowing, and disregarding suggestions from the committers
+
*** Looks like the proper fix from committers was not even tried ?
+
*** It's OK putting adding a layer if it solves a problem ... but if the proper solution is suggested, it should at least be tried.
+
*** McQ: Accessibility - with 10000 items it's getting slow - should try the native way
+
** Lars: Transparency? - No insight on what FEEP's are actually ongoing
+
*** '''AI Dani''' send note to Wayne and Mike asking for location of FEEP Project List
+
*** '''AI Martin''' compare against AC's requested list, and put on agenda for the next AC call
+
** Lars: Styling is actually an important business driver!
+
** Alex: FEEP feels like "quick and dirty" is favored at the moment over sustainable solutions !
+
*** McQ: Perhaps a problem with the funding model ?
+
*** Dani: Lack of people who want to fix issues on the list of the AC ?
+
*** McQ: FEEP is still early - time to provide feedback now. Goal '''Transparency''' on what's done, and why design decisions are taken.
+
*** McQ: Who cares for StyledText - have Markus have a conversation with the submitter ?
+
**** Lars: We have no API for styling scrollbars (background, foreground) - Alex: '''THIS''' is what the FEEP should have adressed !
+
** Martin: Next step should be conversation with EMO about toplevel transparency, and basic guidelines ("sustainable solution over quick fix").
+
** Alex: Need something like JEP (Java Enhancement Process) for FEEP.
+
*** McQ: Agree this is what we want, but would it discourage submitters ? The lighter-weight the process the better...
+
** Alex: If anyone stepped in and did that work it's fine ... but such work sponsored via FEEP seems putting resources in a wrong direction.
+
* Lars '''Question: Google work on improved Type Hierarchy'''
+
** Main work is a new Index, Type hierarchy will be the first client, planned past Neon (contributor: Stefan Xenos).
+
  
<hr/>
 
'''March 29, 2016''' - McQ, Lars, Martin, Dani, Alex
 
* Lars: '''PDE Build in Maintenance''' - Officially state this ?
 
** PDE Build still works; and we're not yet in a position to replace it (it's needed for manual export)
 
** Alex: What about not quite declaring maintenance mode, but state something like "for a new project, you might consider Tycho or something else"
 
** McQ: '''DECISION''' Ensure that on the PDE Build Homepage, we clarify the relationship between PDE Build and other technologies (like Tycho)
 
* Lars: '''Integrate more projects into Platform UI?'''
 
** Having few commits on a component, or overlapping committer list, is not an argument for merging projects
 
** Arguments for merging would only be if existing committers struggle with handling incoming contributions (or if component leads want to get merged) ... but that's not quite the case right now. Being able to look at a component by itself has also some value.
 
** Alex: Being able to handle Team/UI would make sense for Platform/UI ... but not for the native resources
 
** '''DECISION''' to not merge projects at this time.
 
* Lars: '''Request for API Changes on eclipse-pmc mailing list'''
 
** McQ: OK for a single PMC member to +1 the obvious ones, but should do due diligence on API changes (eg ping consumers etc)
 
** Alex: OK for API Additions, but should discuss API changes
 
** Compromise: API change requests must be requested on eclipse-pmc mailing list; PMC members must "speak up" on the mailing list if they want an item discussed, otherwise any PMC member can just approve. '''AI Dani''' notify mailing list.
 
* Dani: 900 Bugs targeted Neon
 
** Need to move away from "just moving bugs from one milestone to the next"
 
  
<hr/>
+
'''March 13, 2018''' - Dani, McQ, Tom
'''March 22, 2016''' - McQ, Dani, Alex, Martin
+
* Alex had troubles to join; Lars still in vacation
* Dani: we shipped M6 on time. Watch out for API change requests on the PMC mailing list.
+
* Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
* Dani: public holiday on Friday (Good Friday) and/or Monday (Easter Monday)
+
** ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project
* Alex: gave an update on tests running on CentOS with GTK+ 3
+
* Discussion about Che
+
** McQ: Che still feels monolithic - unfortunate that the Eclipse Resource Model was not considered
+
** Dani: Preferences in Che vs. the IDE
+
** McQ: What would it take to unify Che, Orion and the Eclipse IDE ?
+
  
<hr/>
 
'''March 15, 2016''' - McQ, Dani, Alex, Martin
 
* Dani: '''Platform/UI got awarded as the Most Open Project :)'''
 
* Dani: Mention PDE/Build as in maintenance? - discuss next week when Lars is back
 
* McQ: Merge Subproject Committers Groups? - Membership based on expertise is important
 
* Dani: Test Failures due to hidpi work - not entirely done yet but looking good for M7
 
* Dani: Lots of failures due to "Widget Disposed" failures
 
** Gerrit tests didn't fail, probably sine the event timing on VNC is a little bit different than running manually
 
** Alex: VNC/Gerrit tests run on GTK2 whereas all the rest defaults to GTK3 now
 
** Looking for a machine with GTK3 to enable them -- working with Mikael Barbero to get this for David
 
* VS Code Open Sourced - plugin model is very similar to Orion
 
** Excellent with TypeScript, not quite as good as Orion for JavaScript
 
** Ideally, would love to see some unification of web-based IDEs (like Che already using Orion editor)
 
  
'''March 8, 2016''' - No call
+
'''March 6, 2018''' - McQ, Tom, Alex
 +
* Short call without any interesting topics
  
<hr/>
 
'''March 1, 2016''' - Dani, Martin
 
* Dani OOO next week
 
* Alex: '''{{bug|179924}} SSH-agent authentication''' 3rd party code for SSH using JVM internals
 
** Dani: Suggest asking on the bug for confirmation what's the JNA team's plan ... they have a full year time
 
** Martin: JNA seems quite widely used these days...
 
* EclipseCon next week - Dani and Alex out - Martin will open the Bridge but might be canceled.
 
  
<hr/>
+
'''February 27, 2018''' - Lars, Dani, McQ, Tom, Alex
'''February 23, 2016''' - McQ, Martin, Dani, Alex
+
* JDT support for new Java releases
* Dani: '''Mars.2 is on track'''
+
** McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible
* Dani: '''FEEP Update'''
+
** Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community
** EMO still looking for people bidding on items prioritized by the AC - Pascal to look at some p2ish issues in April
+
* Dropping XP support
* Dani: '''Update on Welcome'''
+
** Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release
** Brian de Alwis contributed Solstice based Welcome - looking nice and done right, just a 4th theme to select (some artwork needs IP review)
+
** Mail to be posted to cross project by Dani to gather feedback
* McQ: '''Scrollbars on Windows''' and their appearance
+
** Alex: 1 week for gathering input on cross-project - '''AGREED'''
** Dark Theme Scrollbars don't currently look good on Windows - proposal to paint in SWT - currently proposed on StyledText only
+
** If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex
** Dani agrees with Alex that this would open the door to hell
+
** To be formally voted after the mail to cross-project
** McQ: Having seen AWT take ages in terms of emulating OS appearance makes the idea of painting ourselves not too appealing
+
* Release names
** Also concerned about special cases (like performance with ultra-long lines etc)
+
** Version only, release names are irrelevant from Eclipse TLP side - '''AGREED'''
** Alex: Any approach in this direction will have bad effects in terms of SWT maintainability and its cross-platform support (think Wayland, RAP, ...). API additions designed with not at least 2 out of the 3 WSs supported are probably not good cross platform APIs considering how different the WSs are.
+
* Inactive committers pruning
** Could a GTK version on Windows perhaps be an alternative? Alex(after meeting additions): GTK is supposed to run fine there and Broadway on Windows can be driving for it as figuring the build on Windows should give working SWT (thanks to Wayland work making GTK port quite crossplatform).
+
** 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/>
 
  
'''February 16, 2016''' - Alex, Dani, Martin
+
'''February 20, 2018''' - Lars, Dani, McQ, Tom
* no topics
+
  
<hr/>
+
* 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 9, 2016''' - Alex, McQ, Dani
 
* Dani: looking good for Mars.2 (4.5.2) - no RC4 planned
 
* Dani: please take a look at {{bug|466370}} Welcome Screen redesign
 
* Dani: please take a look at {{bug|472614}} Smart Project Importer
 
  
<hr/>
+
'''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: [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
 +
** 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
  
'''February 2, 2016''' - Dani, Alex, Martin, McQ
 
* Dani: '''Foundation Hires''' - Dani hopes they'll find someone in Europe to deal with Releng issues
 
* Dani: '''Neon M5''' went smoothly - M6 will be the API freeze; tomorrow is the last planned RC for Mars.2
 
* Dani: '''CQ Deadline''' on Feb.12 for Neon
 
* Dani: {{bug|486647}} for changing the strategy when opening files not associated with Eclipse
 
** With M5, can now use the System Editor (default) or Text Editor - there's a request to always use the text editor
 
** Dani thinks that for JPG one wants to use the OS
 
*** Martin agrees, OpenWith and choosing an editor remembers the choice, and one can also remember;
 
*** We also show the System Icon in Project Explorer, so using the System Editor by default is natural
 
*** Alex set it to "ask via popup" - can be quite noisy, but avoids trouble when KDevelop or something associated itself with Makefiles or so
 
** Agreement that flexibility is fine - see no case for changing the default
 
  
<hr/>
+
'''January 30, 2018''' - Alex, Lars, Dani, Tom
'''January 26, 2016''' - Dani, McQ, Alex, Martin, Lars
+
* General Updates (Dani)
* Official PMC representation on AC calls - keep McQ listed since he is interested but nominate Dani instead of John
+
** Shipped M5, still working some p2 issues
* Next round of FEEP coming up - discussed pro and cons
+
** RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates
* Dani: busy week for the team: Mars.2 (4.5.2) RC2 and Neon (4.6) M5 due this Friday - on track
+
** 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 [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 19, 2016''' - Dani, Alex, Martin
 
* Upstaffing PMC - meet next week
 
* Update Eclipse PMC representation on the AC
 
** Since only Alex will represent the Eclipse PMC at EclipseCon, should push for not making formal decisions unless there is remote attendance support
 
* Dani: {{bug|485429}} '''PDE Build''' - looks like a lot of people still use it; OK if moving to a different component, but there's still a dependency:
 
** Plugin or feature export still needs PDE Build -- Whoever wants to remove it, will need to implement a replacement '''in the Platform'''
 
** Alex: Platform build currently does double bootstrapping Tycho already ... making this more complex would be a problem
 
** Introducing other build system into the Platform would be a wrong approach
 
** Will go ahead with what we have for 4.6
 
* Alex: As of today's GTK3 build, Eclipse is working fine on Wayland :) thanks to a number of fixes in GTK
 
** Some GTK developers are now considering Eclipse as part of their regression suite :)
 
* SWT move to Java 7 was much appreciated; moving forward, how to deal with functional interfaces ?
 
* Alex would be interested in some styling support in SWT - would simplify some things, at least on GTK
 
** Could be a very simple API like setStyle(String) - win32 also seems to have some styling support
 
* Martin: '''Stability of GTK3 on Mars.2 ?'''
 
** Alex: Many distros do their own hacks, so hard to tell... Mars.2 should be stable on every distro that has a stable GTK3 distro without too many patches
 
** Can't recommend GTK3 on Ubuntu yet; few things improved lately, but still causes troubles whenever Ubuntu updates their GTK, requires more fixes in SWT; Kubunutu and derivatives might be even worse
 
*** Good news is that GTK3.16 dropped support for custom theming engines - causes some ugliness but at least it's stable
 
** Debian or SuSE should be OK;
 
** Expect Neon GTK3 to be more stable everywhere than GTK2
 
  
<hr/>
+
'''January 16, 2018''' - Alex, Lars, Dani, Tom
'''January 12, 2016''' - McQ, Dani, Alex, Martin
+
* Native builds at eclipse.org status (Lars):
* Dani: '''Upstaffing the PMC'''
+
** Dani: swt is done for some time already
** Considering "one-time invitation" to get to know candidates better; not so comfortable with a "trial period"
+
** Dani: launchers after M5 is released to prevent breakage
* Dani: '''Remove Kim Moir from Platform Releng''' - ideally talk to Kim before moving forward
+
* GTK launcher changes (Alex):
* Dani: {{bug|485429}} '''Remove PDE Build from our drops?'''
+
** Changes to not rely on X11 atoms but on dbus ready for review
** Removing PDE Build is one thing - adding a different technology would be wrong, as wrong as adding EGit
+
** Linux only as no other GTK platforms are currently built
** McQ and Dani will reach out inside IBM;
+
* Equinox CQs (Tom):
** Patches are still being submitted; middle ground would be remove from the delivery but keep in repo (and deprecate since not adding features)
+
** P2 capabilities patch from Todor and felix.scr update
* Dani: {{bug|485257}} '''Copyright Policy Change''' - waiting on EMO/Legal input
+
** Slow process risking M5
* Alex: '''Updating SWT to Java7'''
+
** Alex: Ping Sharon asking for speedup if possible
* McQ: '''Travel for EclipseCon'''
+
* 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/>
 
'''January 5, 2016''' - McQ, Dani
 
* Dani: '''PMC Membership'''
 
  
<hr/>
+
'''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 =
 
= 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 2015 | Archive of Meeting Minutes from 2015]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]

Revision as of 12:49, 25 February 2020

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

February 25, 2020 - Dani, McQ, Tom, Alex

  • Dani: Created and sent Endgame plan
  • Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
  • Alex: SWT on Linux in 4.16 to require Gtk 3.20 to simplify CSS machinery and prep for GTK4
  • Alex: ICU4J removal
    • Dani: ICU4J reacts faster to changes and supports more features (new Japanese era)
    • Alex: It might but Eclipse fails at keeping up so current version shipped with Eclipse misses features that the JVM supports (latest CLDR)
    • Dani: Asks for a proof that JVM is better that ICU
    • Alex: Which metrics to be measured?
    • Dani: Will check with ICU guy about that and whether it's still needed


February 18, 2020 - McQ, Alex, Dani, Lars, Tom

  • Dani: need to work on IP Log, Release Review and Endgame Plan
  • Lars: ECF - will we update to the latest
    • Alex: is in the works. Scott needs to provide us with the update
  • Tom: Found an issue with JUnit 5 launching but not reproducible with latest I-build
    • Dani: File a bug if you have steps or contact Noopur directly
  • Dani: Update on X-builds and tags


February 11, 2020 - McQ, Alex, Dani, Lars, Tom

  • Alex: Infrastructure is very instable, how can be complain to the foundation?
    • Alex: Eclipse foundation server team not responding to complains and seem unclear about the source of the issue
    • Discussion about makes a stronger statement to the foundation about the bad state of the infrastructure
    • McQ: Suggestion to send a note as PMC to the foundation
    • Dani: First we should ask webmaster why this takes so long
    • Alex: Marketplace infrastructure is also in bad state

-> Alex to contact Denis and to cc the other PMC members

February 4, 2020 - McQ, Dani, Tom

  • OSGi Spec talk
    • OSGi R8 Core will be done this year.
    • May be ready for 4.16, but no rush if it slips to 4.17
    • Will not put anything in master until spec is final which makes it more likely to be 4.17


January 28, 2020 - McQ, Alex, Dani, Tom, Lars

  • Ongoing saga of the EPP packages
    • Markus did it last week
    • PMC discussed possible futures here, but no conclusions
    • Discussion also happening at the board level
  • M2 is this week
  • Pushing for JUnit updates for M2


January 21, 2020 - Dani, Tom, Lars

  • Dani: EPP builds still missing, Dani contacted Markus Knauer to update EPP for M1, release train is at risk if nobody steps up
  • New test failures are investigated, action plan is to restart the test, if they still fails restart the machine and if the tests still fail, see if a revert fixes the test


January 14, 2020 - McQ, Alex, Dani, Tom

  • Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
  • Dani: Plan updated to remove Windows 7
  • Alex: Felix Dependencies for SCR done
    • confirm fix for bug 544571
    • releng disruptions during update, but recovered. More disruptions expected as we update dependencies for March release.
    • broken builds, need to get a list of issues. Seems to be more infrastructure issues. Need to report back to the foundation. Example, the signing issue that broken the respin.
  • Some discussion about gitlab option at foundation. bug 537913
    • What happens to gerrit work flow for review?
    • Would dropping bugzilla happen or can we migrate all issues?
    • Without migration it is a no-go for us
    • Currently no plans to move Eclipse project to gitlab at this time.


January 7, 2020 - McQ, Alex, Dani, Tom, Lars

  • Dani: Created initial 4.15 plan - please have a look
  • Dani: Created release record for 4.15
  • Dani: Sent a note to teams to create their 4.15 plan items/bugs
  • Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
    • Unanimous decision: Yes
  • Dani: Discuss (again, see below) resolution for stale bugs
    • We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
    • We will only auto/mass close existing stale bugs with notification turned off
  • Change rules about x-internal exports (bug 553709)
    • Decision:
    • - Newly added internal packages should not use x-internal exports unless there are very good reasons
    • - For existing packages the x-internal export can be removed with PMC approval


December 10, 2019 - Alex, Dani, Tom, Lars

  • Dani: RC2a respin to be promoted today
  • Dani: 4.15 M1 approaching fast (January 10)
  • Dani: master is open
  • Dani: Version bumps done for now
    • Rebase if needed Gerrit makes it being able to push without version bumps and breaks next build
    • Tool needs improvement to collect all version bumps needed to make initial bumps faster
  • Dani: How to make milestones used more
    • Have latest and deny things that have been since M1 and no one reported till RC1
    • Consider having latest unstable aka milestone channel which can be used by users/integrators
  • Tom: Java 8 support dropped - no decision to be made now


December 3, 2019 - Alex, Dani, McQ, Lars

  • Dani: RC2 this week. Supposed to be the end of 4.14 for us.
  • Dani: Rules for exporting packages as outlined in Export-Package :
    • Background: bug 544977.
    • We need to discuss whether we want to relax those rules.
    • Tom to file a bug report.


November 26, 2019 - Alex, Dani, McQ

  • GTK minimum version being upgraded: 3.14 -> March; 3.22 -> June
  • Target environments upgraded for 4.14, PMC members please verify
  • Standalone SWT download was broken in M3; Fixed in RC1
  • Mac downloads are now being notarized
  • Red Hat team will help with release engineering work


November 19, 2019 - Tom, Alex, Lars, Dani

  • Bumping GTK minimum version for SWT
    • No bump has been done in the last 2 years
    • GTK 4 is starting to shape up. In preparation we need to move up. 3.14 minimal version from 3.10 for March 2020 release. Will allow styling to go through our CSS engine. Will address many bugs because we override the behavior. Allows us to remove dead code.
    • For June release move to 3.22 release directly. Wayland is useless under 3.20
    • Will confirm with the SWT team that this is ok, will have an answer next week. PMC agrees to proceed as long as the development team is OK with it.
  • Dani: Fighting with build
    • Orbit checksums were not redone in latest (working on fix)
    • Issues with Mac signing - been really unreliable bug 553205
  • Dani: No IPLog needed this release, will need to be at least every year and we will do it in March.
  • SWT patch for Windows, allows to theme the scrollbar. Patch is stale now?
    • Can the team look at the patch and rework? We can review but likely not rework. bug 444560


November 12, 2019 - Tom, Alex, Lars, Dani

  • M3 next week
    • Many open bugs targeted for 4.14 M3 and 4.14
    • Request for contributors to act on them and retarget
  • Gerrit reviews
    • Dedicated time to spend on review patches from non-commiters and non-employees of IBM and Red Hat
    • Time still to be considered
  • Dani to check whether IP Log and review are needed for 4.14
  • Official build runs with Java 11 now
    • This is the runtime JVM used by the build system, nothing in the deliverables should require Java 11
    • Tools are catching up, reports had to be modified to work with it
    • If there is any issue noticed in deliverables, reports, download pages ... - please open a bug report and add Alex on cc
  • Pack200 (tom)
    • Test whether everything is fine if pack200 is gone is pending
    • Companies shipping only packed files will face issues
    • Ship alternative pack200 implementation? - better look at alternative compression if so critical
    • Build tools (e.g. reports generator) are using Pack200 classes directly, that would be a problem in the future
    • Drop packed files requirement for SimRel
      • If/when contribution requires Java 14 it's the only feasible thing to do, to be clarified in requirements


October 29, 2019 - Tom, McQ, Alex, Lars, Dani

  • Dani
    • still working on the PPC64LE issue
    • EclipseCon was great, met lots of people, JDT team plans to do more reviews in the future
      • Dani: missed Lars, Mickael, Andrey and others
    • Wayne and Markus might not continue to work on the release train, so this may end up an automatic process or a new working group may be founding another person
  • General discussion about unmaintained projects and how to deal with that

October 15, 2019 - Tom, Alex, Dani

  • Shipped 4.13 M1 on time
  • Quickly discussed Wayne's plans to reduce his time for the Release Train
  • Next week EclipseCon (no Dani)


October 08, 2019 - Tom, McQ, Alex, Dani, Lars

  • PPC64LE machine
    • Downtimes experienced with current one and general warning that there might be more
    • McQ: how many downloads do we have?
      • Dani: probably more in products rather than IDE downloads
    • PPC64LE workstation on the market (https://www.raptorcs.com/content/TL2DS1/intro.html) and Fedora looks into adding PPC64LE desktop spin
  • Jetty update test failures
    • Tom to ask Raymond to help us with it
  • 4.14 plan created
    • To be published once we gather the work items
  • Release record created
  • M1 this week
  • Gerrit submit
    • AGREED: Switch to "Rebase if Necessary"
    • Alex to take care of contacting admins to see change implemented


October 01, 2019 - Tom, McQ, Alex, Dani, Lars

  • Dani to look into plan and release record for 4.14
  • Stale bug reports should be closed as WONTFIX if there is not a response to the stale bug flag
  • Changes on Gerrit to allow fast-forward merges
    • deferred to next week


September 24, 2019 - Tom, McQ, Alex, Dani

  • discussed enabling fail on warnings on JDT projects
    • Dani to clarify with Roland


September 17, 2019 - Tom, McQ, Alex, Dani

  • Crash issue on win32 - respin done
  • Java 13 GA
    • marketplace entry works with M3 and onwards
    • merge into master starting
  • 4.13 GA
    • looks goods so far, packages are there
    • macos notarization still in process for EPPs


September 10, 2019 - Tom, McQ, Alex, Lars, Dani

  • Gerrits are failing
    • one failed because of missing version increase, some appear to be tooling issues
    • change went in to API tooling, which may fix it
    • do not merge failing gerrits
  • Many thanks to those who worked through the weekend to fix the Mac signing issue!


September 3, 2019 - Tom, McQ, Alex, Lars

  • Discussed status of RC3
    • This Friday for Platform - two known issues being looked at
    • bug 550672 - Alex - Still no final solution to the problem. May result in backing out fix to bug 548002
    • bug 550606 - Tom - at first seemed like a major regression that could require a revert of fix to bug 548877. Alex - has been determined to be a very limited scenario that we feel is not blocking the release and does not warrant reverting to fix.
  • Discussion of download stats. Much improved over the past year and looks to be double what the Photon release was a year ago for the 2019-06 release.
    • Some thoughts on what has caused the increased interest. Lars - much work around quality and performance. Alex - a result of a broader community involvement and other development plugins for eclipse gaining popularity which drive Eclipse downloads.


August 27, 2019 - Tom, Dani, Alex, Lars

  • Dani - Status update
    • RC1 this Friday for Platform - on track
    • Still working on Notarize Mac app (bug 549814)
  • Dani on vacation next week, starting this Friday
    • ==> please watch out for approval requests for API and feature changes after RC1
  • Lars - new filter icon (bug 465914)
    • all agree to be willing to change the icon
    • Dani: not just a funnel, but maybe a combination of sieve and funnel, or a good sieve icon
    • Lars: will make some suggestion in the bug report
  • Lars - compare panel orientation: should we change the default to what's in Gerrit? (bug 501752)
    • Agreement to try in 4.14 M1


August 20, 2019 - Tom, Dani, Alex, Lars

  • Dani - Status update
    • Tests are looking good for M3
    • Dani team gave focus to new Search, found several UX issues, like shortcuts
    • NPE Bug in the JDT quick outline, got fixed and rebuild was triggered
    • Resource packs were donated by Redhat, IBM and vogella GmbH to platform, discussion how long it will take for the foundation to update
    • Dani to discuss the build infrastructure with the foundation
  • Parallel activation for the IDE - Tom
    • Tom stated that it will be very time consuming to enable this
    • Might cause lots of issues during startup, i.e. deadlocks or missing DI due to activation order
    • Result: definitely nothing we should just do, without seeing a clear benefit during startup and it would require lots of efforts to get this well tested
  • Process removal of views - Dani /Lars
    • NavigatorView is deprecated but plugin.xml extension is not deprecated as we have no means of doing that
    • Suggestion from Lars: Announcement of removal now and mark for deletion
    • Suggestion from Dani: Replace the implementation
    • Alex: Adding it to the label of the view

Result: Send out send to cross that we want to delete the view, outdate the label with "Deprecate" and mark it for deletion.

Tom: Do we need a way to deprecate an individual extension? Discussion about and general agreement that this would not help clients.

August 13, 2019 - Tom, Dani, Alex, Lars

  • Dani: Mass changes only up to M1?
    • Lars - If everyone agrees then post M1 changes can happen
    • Tom - What makes it a mass change?
    • Alex - doesn't see the need for timeline on guideline, just make it across the build
    • -1 review always blocks the merge until some agreement is made on the change
    • Committers are not required to have review and it is up to the committer to ask for a review
    • JDT has additional concerns because a branch is needed to do next Java release development. Should just be a restriction for JDT to decide when mass changes can be made.
    • Resolution:
      • Mass changes are requested not to be more than 50 files in general if they can be split up but ...
      • Don't force it to be split for cases it is difficult to do so
      • A committer can block a mass change (like any other change) with -1 if there are good arguments
      • Don't restrict mass changes to specific milestones
      • Cleanups are allowed at any time during development cycle
      • Should reviewers be added??
        • No adding reviewers is not required by committers
        • Project leads should monitor Gerrit queues - PMC agreed
  • General discussion about JDT team changes with Java release cycle ...
    • expect large changes for Java 14 (e.g. Valhalla)
  • Alex - What happens when our dependencies require java 11?
    • Particularly for help, Lucene and Jetty
  • Lars - Fix in toolbar (bug 549898) that exposed another bug that is old
    • If not fixed do we need to revert original issue?
  • Dani talks about resource packs and possibility of companies donating resources to the Eclipse Project: https://www.eclipse.org/lists/eclipse.org-project-leadership/msg00181.html


August 6, 2019 - McQ, Tom, Dani


July 30, 2019 - McQ, Alex, Dani

  • Nothing to discuss.


July 23, 2019 - McQ, Tom, Dani

  • Nothing to discuss.


July 16, 2019 - Alex, Tom

  • Bouncycastle MessageDigets plugin inclusion (bug 541781)
    • Alex: Which feature should contain it so it's published?
    • Tom: Let's discuss on the bundle but usability of current equinox features is questionable.
    • Alex: Let's sanitize them in this case.
    • Tom: +1, we need to figure what the deprecation policy (if any) there is for features.
  • Merge of rt.equinox.bundles and framework git repos
    • Tom: still interested in it but very low priority
    • Alex: interested in it for the sake of rename of repos from rt.equinox to eclipse.equinox


July 9, 2019 - Dani, Tom

  • Dani: M1 this week. Looks good so far.
  • We will not suspend the calls during summer.


July 2, 2019 - Alex, Tom

  • General chat about bugzilla vs gerrit only workflow. No binding decisions due to lack of quorum.


Jun 25, 2019 - Alex, Lars

  • General chat about state of affairs due to lack of quorum


Jun 18, 2019 - McQ, Lars, Tom

  • The 1.5 minute start up time issue (Windows Defender) needs to be investigated
    • Is this related to the signing problem?
    • What do we have to do to be "blessed" by Microsoft?
      • Dani: Not sure this is the solution as we do not even know what the problem is
  • There is a perception that Eclipse on Windows is not as smooth/performant as Linux now
    • This is a bit troubling, since windows is still our most significant platform (by downloads)
    • Do we need to look for ways to increase participation in SWT on Win?
  • Do we need better coding pattern/style guidelines?


Jun 11, 2019 - McQ, Dani, Alex, Lars, Tom

  • 2019-06 release
    • RC2 shipped on time
    • No pending request
    • Lars: Opening next release stream - felt too long due to amount of incoming gerrits. It's a nice problem to have but no change planned on the topic so far.
  • Gerrit down
    • Dani called webmaster, negotiated it to be made tier 1
  • Emeritus status for historical committers
    • Foundation is dropping the feature overall so no plans to nominate new people from the last group of removed committers
  • No bug report policy
    • Simple fixes do not require bug report
    • Dani: larger patches to require bug
    • McQ: reviewer should the have the right to request
    • Alex: requiring too many bugzillas is against young population used to github
    • AGREED - we stay as we are and reviewer has the right to ask for one if he feels the need
  • New committer process document - whoever has a comment to comment on the document
  • Modern eclipse
    • McQ: how to define what to work on without too much bias
    • Alex: new intern working on inline editing - an initiative to serve as example of modernization
    • AGREED - come up with list of things to work on
    • ACTION ITEM: Lars: to create initial document for list of things/initiatives
  • Dani not on call for the next 3 times (Eclipse Board meeting, manager training and vacation)


May 28, 2019 - McQ, Dani, Alex, Lars, Tom

  • http client issue
    • should we ship old and new?
    • we initially decided to only ship new one.
    • ship old only gives ability to revert back, but still requires work on client
    • if a fix isn't available for using the new http client then we will consider shipping only the old one for 4.12
    • others can install the new http client if they want to try it out
  • message to Stephan
    • Note set, no additional information or status available
  • heading into RC builds for 4.12
    • end game plan created
    • finalizing the plan and closed after updating target environments
  • discussed bug 547011
    • decided to bump event bundle version to work around
    • need a new bug opened to enable us to detect this situation earlier
  • Major version increase on API removal discussion
    • announced API removals will not cause major version bumps
    • This potentially breaks others
    • We only do this on announced deprecations for 3 years.
  • Future of Eclipse IDE (McQ)
    • Power users for writing code. A lot still use vanilla text editor ...
    • What is the value of the IDE in today's environment. Deployment and monitor of applications is more important.
    • Are we not addressing the problems of today to make Eclipse the power tool of today.
    • Do we need support for new languages.
    • Language server help?
    • can we find some set of things to do to reduce friction to using Eclipse IDE?
    • remove notion of project natures?
    • asynchronous operations can help?
    • Make our lists of top things to do
    • get community involvement on prioritizing the list of important things to improve.
  • Alex out next week

May 21, 2019 - McQ, Dani, Alex, Lars

  • Dani
    • M3 is this week, need to watch out for bugs and issues
    • New feature to make modal dialogs non-modal created a blocker but this has been fixed
    • Endgame plan will be send out by Dani by the end of this week
    • We only ship an HttpClient45 implementation with the latest ECF and no HttpClient4 anymore which may cause issue. Dani's team will send out a note tomorrow, Alex thinks that this should not create an issue
    • Release restrictions from the foundation are less strict for the next release (no IP log and release review for every release required anymore), we will follow this process
  • Discussion about Stephan Herrmann's email to the PMC and we need to check with Stephan
    • IBM may have an option to provide service releases
    • We should also look at the bug system to see what is important to the users

May 14, 2019 - McQ, Dani, Alex, Tom

  • No complaints about our M2 delivery so far
  • M3 is next week
    • 200 bugs still open
    • People are just bumping them to the next milestone
    • Better to remove target milestone if you don’t actually believe it will be fixed by then
  • Jetty dev list note:
  • Batik update — 4 of 5 CQs approved should be in for M3


May 7, 2019 - McQ, Lars, Dani, Alex

  • Gerrit verification jobs to give -1 on warnings
    • Dani: not easy, single file with warnings in Jenkins for all type of warnings
    • PMC is in favor of such solution but there are technical limitations to achieve it or it would require significant effort to get to warning free builds
  • ECF http client update
    • Dani: prefer to ship both old and new implementation, fine with new one only and reconsider
    • Alex: not in favor of shipping two implementations as that would make the testing harder, prefer to ship single one and that being the new one, reconsider if there is issue
    • ACTION: Dani to reply to Scott that Eclipse SDK will ship latest only and we would like to have it for testing purposes ASAP
  • Inactive committers
    • Dani: Notification sent and inactive committers that want to keep commit rights can do it now
  • 2019-06 M2
    • Dani: I-build delivered to M2
  • Dependency updates
    • Alex: Jetty is in progress to 9.4.18, permissions to publishing the version to p2 repo on behalf of Jetty project granted
    • Alex: Batik - work in progress


April 30, 2019 - McQ, Tom, Lars, Dani

  • M2 for us this week - will only contribute last good I-build - no real milestone week
  • Extend fast track for committers for all projects not just inactive ones
    • Tom: already following the proposed process
    • We can't force committers to accept a new committer (against EDP)
    • Unanimous decision to drop fast track program. Mentor/committer can propose any contributor if he can justify the nomination
  • Request for review on JDT mailing list
    • Wait for Stephan to respond for a day or two
    • Dani to contact Stephan if no response


April 23, 2019 - McQ, Alex, Dani, Tom

  • M1 train has been published but no official announcement was sent
  • Alex to update Jetty with latest security fixes


April 16, 2019 - Lars, Dani, Tom, McQ

  • M1 has shipped -- Lots of good stuff, see the N&N
  • Plan has been posted
    • Attempt to simplify the creation process, still WIP
  • Started working on identifying inactive committers
    • Inactive == haven't committed anything for 2 years
  • Looking at ways to ensure we have enough testing of new Java features
    • Main projects should run on widest ranges of versions, so can't just raise BREE there
    • Could add new test projects, and allow tests to be written with new constructs


April 9, 2019 - Alex, Dani, Tom, McQ

  • Dani
    • Lots of regressions Dani investigating
      • cycle from tests (fixed)
      • UI elements gone missing (fixed)
    • Get rid of the new index from JDT
      • Needs lots of polish to get rid of bugs, but never showed performance improvements.
      • Decided to disable the option to use it (code remains). Open to others to help maintain.
    • Created initial 2019-06 (4.12) plan
      • Still need individual plan bugs from leads (cough Equinox).
    • Created initial release record for 2019-06 (4.12)
    • Made a call for plan items for 2019-06 (4.12)
    • M1 this week
      • Looks good so far.
  • Tom
    • Investigating parallel activation of bundles bug 540507
  • Alex
    • M1 fixes for SWT
      • Fixes for other things in M1 some small regression in custom Linux environment.
    • M1 jsch update needed
    • Tom to Open bug for Apache Felix SCR update post M1
    • SWT issue
      • SVG image support for Linux-only to start. Need support for other platforms.
      • Windows has a number of patches pending. (mostly cleanup patches?)
      • Try to get more people on board for Windows support help.
      • Ask for help on the platform list. We have combined the projects and have more devs available to work on SWT if they are willing to help.
      • For cleanup you need specific SWT knowledge.
        • two types of cleanup - use quick fix from Eclipse - and real refactoring.
    • If we are to advance SWT development then we cannot continue with a single committer on a platform. Need to promote the recruitment of new SWT committers.


April 2, 2019 - McQ, Dani, Lars, Tom

  • Planning for this release has started
    • Sub-projects need to have first cut of plan ready by a week from Friday
  • Also a week from Friday is our M1
  • Based on community feedback we will keep the update site for adding Java 11 support to the 2018-09 (4.9) release, the Marketplace entry remains removed


March 26, 2019 - McQ, Dani, Alex, Tom

  • Dani
    • Inactive committer cleanup progress.
      • It is now harder. Portal has been deactivated and the functionality to get inactive committers is gone.
      • Looking to use some script originated by Lars for list of contributors.
      • What is the timeline to be considered inactive again? Ans. A year of inactivity will trigger the question.
  • Alex
    • Confirms that the new indexer has no value to Red Hat (see also March 5 and bug 544898)
    • bug 545032 Implement native ImageLoader (Linux only)
      • Allows additional formats not previously supported to work with the native Linux implementation of SWT
      • What kind of error message will be available on other platforms?
      • Need to confirm the API doc is updated to indicate what formats are supported on what platforms. (Alex will take care of that in the javadoc)
      • Has there been investigation into what later Java versions provide for image loading?
        • No, could be done as part of investigating support on other platforms.
      • Need to have an umbrella bug for the new functionality with additional children defects for the platforms that don't support the new formats. (Alex to open that)


March 19, 2019 - McQ, Lars, Dani

  • Dani
    • 4.11 on track - repositories and download page ready for tomorrow
    • Java 12 GA expected today
    • Will merge Java 12 work to master tomorrow or on Thursday
    • Will provide a Marketplace entry for Java 12 support for 4.11


March 12, 2019 - ???

  • Missing


March 5, 2019 - Tom, Alex, Dani

  • Dani
    • I will be away starting Friday and next week. No laptop ==> watch out for any 4.11 related issues
    • Tom, please update the status on the Equinox 4.11 plan
    • Tom: bug 544370: NoClassDefFoundError: org/apache/sshd/server/auth/AsyncAuthException from SshServ
    • bug 544833: Inactive committer cleanup for Platform for the 4.12 release
      • Might be much more work since committer info from old portal is not available in the new PMI
    • Get rid of new indexer. Alex, not sure who from Red Hat mentioned it at EclipseCon Europe but there seemed to be interest to further work on this.
      • Alex: Roland looked at it and could not see any benefit
      • Current thinking: drop it, but Alex will double-check and report back in two weeks


February 26, 2019 - McQ, Tom, Alex, Lars, Dani

  • Dani
    • Issues with Mac signing
      • McQ: we should ask the Foundation whether they can't set up a watchdog
    • Issues with JAR signing
    • Release on track
    • Prune inactive committers
      • AGREED to do this like we did last year for Platform (bug 530200)
      • Lars for Platform. Tom for Equinox and Dani for JDT and PDE
  • Lars: move active committers to the list of contributors in the Acknowledgments
    • AGREED


February 19, 2019 - Tom, Alex, Dani, Lars

  • Lars: API removal announcement on cross project
    • AGREED: To send one mail per release for RC1 announcing all removals to reduce noise on the mailing list
    • In case of more important removal it can be announced individually.
    • Dani to open bugs for releases so it's handled properly.
  • Lars: Provisional API guidelines changes
    • Current approach with internal/provisional package names until API is stable is an issue because:
      • It creates more work for maintainers to rename packages.
      • It creates more work for adopters to change references once API is stable.
    • AGREED: Use the intended package name but mark it as x-internal until API is final. Lars will update the document.
  • Dani: End game plan posted


February 12, 2019 - Tom, Alex, Dani, Lars

  • Dani:
    • M3 next week.
    • Must start to work on IP log, release review and Endgame plan.
  • Alex: What's the future of ECF (not much happening there)? How feasible is it to replace ECF and HttpClient with new Java HTTP Client from Java 11?
    • Interesting to know, but unfortunately no resources to investigate this at the moment.
  • PMC decision regarding HttpClient for 2019-03: will ship what we have (4.5.5).


February 5, 2019 - Tom, Alex, Dani, Lars

  • Dani:
    • I-build contributed to 2019-03 M2, no complaints so far
    • Over 200 bugs for M3 with 2 weeks left, need to be looked at and target adjusted
  • Alex:
    • JIPPs are subject to update to new infra in the next few months. Releng JIPP is a matter of separate treatment.
    • As soon as most JIPPs (not Eclipse TLP only) are moved to new infra SWT will move to GTK 3.22 as a min version.
    • Sep 2019 release is the earliest possible for SWT GTK min version bump.
  • Tom:
    • equinox.framework and bundles git repositories merge
    • APPROVED if history is preserved
    • Alex: new name of repo should be eclipse.equinox.* not rt.equinox
    • After merge Alex takes renaming rest of equinox repos with webmaster
  • Lars: Fosdem
    • IDE and Free Tools room
    • Netbeans and IntelliJ talks and interest


January 29, 2019 - McQ, Tom, Alex, Dani, Lars

  • Alex: Java 11, should we move the build to Java 11?
    • Agreed to move the Tycho snapshots for testing and move back to Tycho stable after M3
  • Dani: This week is M2, we will contribute the Wednesday I-Build with some sanity checks
  • Dani: Having problems with the asynchronous JDT UI initialization bug 543935


January 22, 2019 - McQ, Tom, Alex, Dani

  • Alex:Felix SCR update
    • Tom: Orbit update to make felix.scr bundle imports non-optional
    • Missing compile warning in the first build - not clear why it happened
  • Tom: Equinox tests move from runtime git repo
    • Needed because tests are not run on gerrit and not findable for contributors
    • Alex: how easy it is to find which one are for equinox and which should stay in runtime repo
    • Tom: to open bug with details


January 15, 2019 - McQ, Tom, Alex, Lars, Dani

  • Dani
    • We shipped 4.11 M1 last Friday - no issue so far
    • Created release record for 4.11 (mandatory to be there by 4.11 M1)
  • Tom
    • Chatter about update configurator bug 542706
    • Alex: update configurator still there but not hooked into Equinox/p2/PDE anymore
    • Alex and Lars to update the bug report


January 8, 2019 - Dani, ?

  • We had a meeting, no notes were taken


December 18, 2018 - McQ, Tom, Alex, Dani

  • Talked about potential release train delay due to JAXB - nothing we have to worry about
  • Next call on January 8


December 11, 2018 - Tom, Lars, Dani

  • Dani: 4.10 looks good, work for 4.11 is open for development
  • Dani: Will add Bugzilla milestones
  • Tom: Will update Equinox to Java 8 soon will need to support Java 8 for quite some time in the future


December 4, 2018 - McQ, Alex, Tom, Lars, Dani

  • Dani away on Thursday and Friday.
    • Please keep an eye on RC2.
    • Please watch the release review (bug 541666).
  • Dani: 4.10 on good track but investigating last minute bug 542090.
  • bug 541689: What needs to be done to add OpenJDK on Windows as a reference platform?
    • We will add this for now, but for 4.11 we will query the community which runtimes are actually used and/or tested.
    • Alex: We need to specify from where the OpenJDK runtime comes from.
  • Tom: When do we push 4.10 to Maven central?
    • Dani: ask on Releng list.
  • Alex: Help Center issue. What's the state?
    • Tom will investigate this a bit more this week. Probably no fix for RC2.


November 27, 2018 - Alex, Dani, McQ, Tom

  • Mailing lists
    • Discussion on merging various mailing lists bug 541508
    • Merge all platform-x lists into one (platform-dev?) list, except the current platform-releng-dev will remain separate.
    • merge all jdt lists into one list (jdt-dev?) list.
    • Considered merging the equinox-dev and p2-dev into one list (equinox-dev?), will leave separate for now because the two groups still seem to have distinct topics to discuss (even if the traffic is relatively low).
    • What is the target usage of the lists? For the user community to ask questions or for the developers to have discussions around development of Eclipse? At this point the traffic is low and the PMC does not see a need to discourage usage by the user community to ask questions.
    • Before merging we need a way to have responses sent to messages sent to the old archived mailing lists which directs them to the new list.
  • Rules for freeze/endgame
    • Consider allowing the gerrit reviews to act as the way to record approval by a member of the PMC and/or project lead instead of requiring that to be flagged in the bugzilla. If the gerrit review was done by someone other than a member of the PMC or project lead then there still needs to be some record in the bugzilla that the required approval of the PMC or project lead was done.


November 20, 2018 - Alex, Lars, Dani, McQ

  • Dani reminded the team to update plans so we can do release review
  • Dani working on IP review
  • M3 this week; then API/feature freeze next week; then one more week and we’re done
  • JDT Code Mining went in today; test!; disabled by default
  • Demonstrated proof of concept, empty shell running on GTK4 alpha
  • bug 541307 needs to be investigated; could be a blocker for PDE or Equinox
  • Seems to be general consensus that code clean-up is more important than maintaining git blame usefulness


November 13, 2018 - Alex, Lars, Dani, McQ

  • Plan update 4.10 plan update 1 from Dani
    • As Foundation still provides only SLES 12 we might still have to list it
    • SWT team tests on SLES15
    • Details: bug 541074
  • Train name update from Dani: We can keep "our" Eclipse IDE name, foundation dropped the idea of adding an additional identifier to the "Eclipse IDE" brand.
  • jsch - Dani checked if preferences are used and could not find any usage, Dani did not yet contact Thomas as JGit did not make any progress in the area. Alex did update Equinox.
  • Cherry-pick as strategy in Gerrit
    • bug 541021
    • Dani does not like the idea and voted against it
    • Alex: Linux tools and CDT are using Cherry-pick

-> Everyone agrees that the build infrastructure is getting worse and that we should find ways to speed up the build, Dani will follow-up with the foundation on that


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

  • Dani: Update on release train name
    • Foundation accepts "Eclipse IDE" as long as the scope is clear
    • Foundation can use another name when the Eclipse IDE is shown along with other IDEs, e.g. Che. Possible name could be "Eclipse Classic IDE"
  • Increase major segment when deleting deprecated API
    • Discussed last year on October 10, 2017 but did not make an official decision
    • Disruption would be huge
    • Today we decided unanimously that in general we will NOT increase the major version when removing deprecated API
      • There might be cases/bundles where we might be more aggressive


October 23, 2018 - No meeting due to EclipseCon Europe


October 16, 2018 - Alex, Lars, Dani, McQ

  • We all agreed that at this point, the right thing regarding renaming the project is to do nothing.
  • Delivered 2018-12 (4.10) M1 on Friday. No feedback on that so far. Train to deliver this Friday.
  • Dani gave an update on the work for the EDP.
  • Alex together with Mickael will make sure that the Unconference session at EclipseCon will be split into interest groups after initial discussion.


October 9, 2018 - Alex, Lars, Tom, Dani, McQ

  • 4.10 plan and release record published
  • 4.10 M1 looks good, low number of bugs
  • Project naming - pushback in planning council and there will be no change until Eclipse Foundation provides the document describing the rules names should comply with
  • Performance tests
    • Lars: jdt.core performance tests not running
    • Dani: performance tests running (mostly) since Photon, most work done by Sravan
    • Dani: results look sane but need to be checked thoroughly for some time to ensure all the infra runs proper
    • Alex: SWT perf tests for 4.9 properly shown improvement in startup initialization


September 18, 2018 - Alex, Lars, Dani, Tom, McQ

  • Release looks ok, respin was required
  • EPL 2.0 conversion was done for the Eclipse SDK but not for the e4 sub projects
    • Lars: e4 repository have not been converted
    • Dani: JDT, Equinox, PDE and Equinox have been converted so the Eclipse SDK has been converted
    • Lars plans to convert the e4 spies
    • Dani will inform Wayne/ Webmaster about the EPL 2.0 migration of the Eclipse SDK
  • Alex suggests deleting the long dead e4 repository like e4 JDT (no commits for 5 years, they should be archived) -> Alex to announce on e4 mailing list
  • Lars reports that SAP might get more involved, he delivered a workshop for them and they have very skilled developers which hopefully will contribute to the platform.
  • Dani: JDT will create a common plan for its components under https://wiki.eclipse.org/JDT/Plan/4.10, similar to platform.


September 11, 2018 - Alex, Lars, Dani, Tom

  • Dani: 4.9 Review is done and passed
    • Release is looking good for final phase
    • RC2 is done - no planned changes left for 4.9
    • Moving on for 4.10
  • Alex: 4.9 is in good shape now
    • Had last minute issues that almost made us miss RC2 date. Felix SCR change in qualifier caused meta-data to be regenerated because of an upgrade in Tycho. Tycho now published generic OSGi capabilities. This lead to cases where Felix SCR would get included without equinox.ds. That lead to issues with activating Felix SCR.
    • Tycho is fixed now to handle starting of Felix SCR, worked around issue for 4.9
    • For 4.10 dropped 32-bit and gtk2 now
  • Tom: org.eclipse.equinox.ds to be removed. Decided to keep equinox.ds in the repository as part of the Equinox SDK feature, but it will not be shipped as part of the Eclipse SDK features.
    • Need to make sure other areas can handle equinox.ds missing (e.g PDE)
  • Dani: Informs us if the team attending Eclipse Day and EclipseCon events.
  • Via email: Pinging robot for bugs will be activated for all subcomponents of the Eclipse top level project, as it is currently not possible to activate the robot for only a sub-component.

September 04, 2018 - Alex, Lars, McQ, Tom

  • CQ in JDT was approved to create code duplication. Lars asked what caused that.
    • Delay in JDT review, biggest blocker is still not in JDT
    • Large change, agreed with Dani to get review priority review in 4.10 from the JDT team
  • Alex/Tom - 4.9 RC2 status
    • Looks good, no know bugs
  • Lars: Activate autoclose for Platform bugs?
    • Lars argues that platform and e4 has too many old bugs so people are not looking at them
    • McQ is against autoclose
    • Agreed by al to enable "Pinging the user if this problem still exists" for selected components (Platform/UI) and see how much feedback we get.
    • Email send to McQ, Tom and Alex if we could also add e4 to that pinging list -> all agreed to enable it also for e4 bugs

August 28, 2018 - Alex, Lars, Dani, Tom

  • Reminder - RC1 this week, RC2 next week
  • Dani on vacation starting this Friday
  • Dani will submit the release review and IP log before going on vacation (Wayne approved this)
    • Alex will handle all things that come up with that
  • EPL 2.0
    • Lars: almost done - few pending patches
    • Alex: boring work - hopefully EPL 3.0 only on 10 years


August 21, 2018 - Alex, Lars, Dani, Tom

  • Reminder - M3 this week RC1 next week
  • Milestone discussion
    • M2 and M3 are too close together.
    • Delivering M1 and M3 instead provides better space for the development team.
    • M1 will be short, but still should give us 1 month time to deliver.
    • For 4.10 we will try delivering M1 and M3 milestones.
  • Dani will look at submitting the release review and IP log early since he will be out during the week they are due.
    • Alex will cover if that cannot be done
  • EDP update - Arch council is making changes ... should ease some things.
    • For example, decoupling the project review from a project release. Project releases still will require IPLogs
  • Lots of bugs still open against 4.9.
    • Team needs to adjust milestones accordingly before 4.9 is done
  • Java 11
    • Work almost done to support Java 11.
    • Initial support will be delivered in Marketplace only (no 4.9a planned).
    • First official release with Java 11 support will be 4.10


August 14, 2018 - McQ, Alex, Lars, Dani, Tom

  • Changing our test framework to use JUnit 5 always (bug 531057)
    • In progress: suites are running, but some tests are aborting
    • Reports should be fine in next build
  • Release review and IP log will be coming soon
    • M3 next week, then one week for RC1 and one week for RC2
    • A lot of bugs in the backlog that need to have their milestone re-assigned
  • Once we get a few releases under our belt using the new process, we should do a retrospective looking at burn rates, quality, etc.
    • The good news is we no longer have to maintain two streams and back port changes.
  • Support for J9 shared classes merged into Equinox
    • Will not update launcher to specify them for this release
    • Need to provide doc on how users can specify the options themselves (via eclipse.ini)
  • McQ away for two weeks


August 7, 2018 - McQ, Alex, Lars, Dani

  • Dani: outstanding plan topics:
    • Target platforms should use SLES 15 (instead of 12)
      • Dani to talk to SWT team about this
    • Remove RHEL 7.4 (current is 7.5)
      • all agree to this
  • McQ to send note about Windows 32-bit EOL
  • Alex: ASM breakage in master — issue in Orbit; should be in next iBuild
  • Dani: shipped M2 last week everything went well


July 31, 2018 - Dani, Tom, Alex

  • Dani: For quality reasons, suggests to have an official M3 (August 24) since after RC1 (August 31) we will only have 1 week left
    • all agree to this
  • Dani: Initial 4.9 plan is ready but no feedback so far


July 10, 2018 - McQ, Dani, Tom, Alex

  • 32 bit support
    • Harder to find 32 bit JVM
    • Devs are not supposed to work on 32 bit OSes anymore
    • Agreement to drop support for 32 bit but keep sources and build support for some period to give people time to bring it back
  • GTK 2.x support in SWT
    • Planned to be removed for 2018-12 release
    • Needed so GTK 4.x port can be started prior to 4.0 release so SWT needs a taken into account from GTK devs
    • Bugs are not being looked at for some time already and GTK 3 has been the default for years now.
  • 4.9 release
    • M1 is this week
    • Platform will contribute I-build with some basic testing but not the full milestone which is to be done for the only milestone which is to be delivered for M2 of the SimRel


June 12, 2018 - McQ, Alex, Tom, Lars

  • RC4a looks good; hidpi fix is in place
    • no plans for further builds at this point

June 05, 2018 - McQ, Alex, Tom, Dani, Lars

  • Dani:
    • Image limit for help should be increased? -> Not covered in the call
    • Will most likely not be able to join the next call
  • Alex:
    • Support only last LTS version of Linux?
      • Agreement to drop old LTS versions for 4.9 but not to change the target environment for 4.8
    • Dropping big Endian -> we all agreed to drop it, MQ found the email to cross, so we can remove it
  • Lars:
    • Update to EPL 2.0?
      • change of about.html is trivial
      • requires version updates of MANIFEST.MF and pom.xml
      • Script for source update look good, Lars checked manually lots of files
      • Coordindate with Jay or Noopur for the JDT UI update
      • Dani suggested to announce such work via the mailing list so that everyone is aware of the work
    • Only one N&N per release? -> Agreed to have one document per release
    • Do we get a name for Photon+1 -> Dani: Our SDK is called 4.9, splash screen will only be month year, planning counsil still discussing
    • Include Tips and Tricks in the SDK -> Not covered in the call


May 29, 2018 - Alex, Tom, Dani

  • Dani:
    • Uploaded IP log
    • Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck
    • Finalized Photon plan
    • Sent Release Review material for approval to PMC mailing list
    • RC3 looks good so far


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

Back to the top