Skip to main content
Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

(Meeting Minutes)
(392 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 12: Line 11:
 
= Meeting Minutes =
 
= Meeting Minutes =
  
'''Sep 6, 2016''' - Dani, Lars, Alex, Martin
+
'''Febr 17, 2021''' - Lars, Alex, McQ
* Dani: Thanks for approving Noopur
+
* Looks good for 4.19 release
* Dani: Java Language Server Proposal - at the Foundation, will be called "JDT Language Server"
+
* Mac ARM has to wait for the 4.20 release, as the team fights multiple issues
* Dani: RC4 - Fix for an Equinox p2 issue, only known issue being fixed, looking good
+
* Top-level project page can currently only be edited by Tom, other PMC members also have access to it https://projects.eclipse.org/projects/eclipse/who
* 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 Arch call tomorrow
+
  
<hr/>
+
'''Dec 15, 2020''' - Lars, Alex, McQ
<strike>Aug 30, 2016 - No topics</strike>
+
* 06. January 2021 is the next meeting
 +
* How can PMC increase the awareness of the project leads / committers?
 +
** Maybe invite the project leads once per month to the PMC meeting?
 +
** Discussion how we can increase the JDT community
  
<strike>Aug 23, 2016 - No topics</strike>
+
'''Dec 01, 2020''' - Lars, Alex, McQ
 +
* RC1 is out; final touches on RC2
 +
* How can we remove the confusion about "e4" project?
 +
** e4 has always been intended to be a sandbox project where people could try things that are experimental or are on a longer timeline
 +
** Should be renamed to make it clear this isn't about leftovers from the Eclipse 4.0 work (maybe "eNext"?)
 +
** Should clean up repos
 +
*** Remove repos that just hold code that has already moved to the platform
 +
*** Remove repos that are no longer getting any investment
 +
*** Work toward moving things that are active/useful into the platform (e.g. "spies" to PDE)
  
<hr/>
+
'''Nov 24, 2020''' - Lars, Alex, McQ
'''Aug 16, 2016''' - Dani, Martin, Lars
+
* PMC is considering the potential of an SDK / IDE working group at the foundation
* Dani will not always be available next two weeks (Eclipse Summit India and IBM Bangalore team visit)
+
** 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
+
* Discussion Do we need the extra releng work to create p2 repositories for milestones?
* no one joined - had private conversation with McQ later
+
** Lot of extra work and sometimes goes wrong
** '''guys, please announce when you can't join. I can make better use of my time than waiting for you in the call ;-) - thanks.'''
+
** All I-Builds are anyway available
<hr/>
+
  
'''Aug 02, 2016''' - Dani, Martin, Alex
+
-> PMC decided to drop the additional p2 repository
* 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]
+
-> Alex will be sending out an email about it to inform potential users of the special p2 repos
** '''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/>
+
** Discussion about the purpose of the milestone week at all
 +
-> Decision not to change the process for now, as the additional testing and focus has also some benefits
  
'''July 26, 2016''' - no meeting
 
  
'''July 19, 2016''' - no meeting
+
'''Nov 17, 2020''' - Lars, Alex, Tom, McQ
 +
* Release 4.18 winding down
 +
** SWT churn for Linux and Mac Big Sur
 +
** Does not appear the Foundation got the new Mac Hardware for testing
 +
* Planning Council discussion
 +
** Dani filled the Eclipse TLP representation role on the Council
 +
** Alex can take the lead to that role
 +
** Alex will look to find a replacement for the tools TLP representative
  
<hr/>
 
'''July 12, 2016''' - McQ, Lars, Alex
 
* Dani: Hackathon summary
 
  
<hr/>
+
'''Nov 10, 2020''' - Lars, Alex, Tom, McQ
'''July 5, 2016''' - Lars, McQ, Alex, Dani, Martin
+
* Still dealing with the loss of Dani
* Lars: SWT move to Java 8
+
* Discussed representation of JDT on PMC
* Alex: Initial builds of GTK 2.24 for AIX - planning to bump minimum GTK version to 2.24
+
* Stabilizing for M3
** Will remove non-cairo drawing, this is where most of the breakage happens
+
* Some releng issues with Java 15 and 16
** Ubuntu 12.04: 2.24.10 / 3.4.5
+
* Tom began investigating p2 ECF httpclient dependency
** RHEL 6: 2.24.23-6
+
** AIX, HP-UX, Solaris ? -- Oxygen will only focus on Linux, Windows, Mac
+
** Secondary Platforms: Not built on EF Hardware, but interested parties can contribute binaries
+
** Trying to support Platforms which can't move up to modern GTK at a similar pace as Linux is hard
+
** '''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/>
+
'''Nov 10, 2020''' - Lars, Alex, Tom, McQ
'''June 21, 2016''' -  
+
* Still dealing with the loss of Dani
*  
+
* Discussed representation of JDT on PMC
 +
* Stabilizing for M3
 +
* Some releng issues with Java 15 and 16
 +
* Tom began investigating p2 ECF httpclient dependency
  
<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
+
'''Nov 3, 2020''' - Lars, Alex, Tom, McQ
* no topics
+
* Dani!
  
<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/>
+
'''Oct 27, 2020''' - Lars, Tom
'''May 24, 2016''' - Dani, Lars, Martin
+
* Nothing to discuss
* Dani: '''IP Log Generator''' - New version is unable to deal with Eclipse Project, Wayne is working on it
+
* Dani: '''Release Review''' - Deadline next week (June 2)
+
* Dani: '''Deprecation Request from Brian'''
+
** Command org.eclipse.ui.cocoa.fullscreenWindow -- all PMC agree on the deprecation although late, since it only affects docs
+
* Dani: '''Copyright End Date'''
+
** '''AGREEMENT''' to no longer require updating the end date (though committers are still ALLOWED to update it)
+
** Will no longer run the automated copyright tool (actually haven't run it the past 3 releases)
+
** Will live with the source code notices being inaccurate / incomplete - the accurate state is in Git
+
** This is acknowledged to not be ideal, but the best compromise we can come up with since "bulk changes" are not OK
+
* Dani: '''Neon Status'''
+
** Java 9 launching - affects all Java consumers, not clear yet what Oracle will do, no plan changing Equinox/Launcher at this time
+
  
<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/>
+
'''Oct 20, 2020''' - Lars, Tom, McQ, Alex
'''May 10, 2016''' - Dani, Martin, Alex, McQ
+
* EclipseCon is running virtual this week
* Dani: '''Policy for what should go into Neon.Update Releases'''
+
* Agreement that removal of API should only before M1 release
** Would like to be more flexible than in the past - discussion point for next week
+
* Proof of concept for using Java 11 http client instead of ECF should be done
* Martin: '''RHEL7 -- GTK3 versus --launcher.GTK_Version 2'''
+
* if we remove ECF we should send out an announcement and keep it for at least one release
** GTK2 rendering still much more reliable than GTK 3 - forced to release commercial software with the GTK2 fallback for now
+
* Decision to start using the @Deprecated(since = "x.y.z", forRemoval = true) for planned API removals if the bundle can use Java 11, wiki for API removal should be updated
*** 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/>
+
'''Oct 6, 2020''' - Dani, Tom, McQ, Alex
'''May 3, 2016''' - Dani, Martin, Alex, McQ
+
* M1 under control
* [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02598.html Brian's request on the PMC list]
+
* Release train materials being worked
** McQ: Why would we care about adding small enhancements in RC1 when we should focus on testing and critical fixes
+
* Moved to Jetty 9.4.32
** Dani: Two parts in the change - the original one (approvable), but another change also sneaked in (enable the prefix search) - not approvable
+
* ECF — need to simplify how we consume http client
** Alex: People don't want to wait for getting in an improvement...
+
** could use Java11 http client instead, but this would require significant development effort
** McQ: OK for adding as feature to Neon.1 , but Neon.0 should be focused on bug fixes
+
** Tom/Alex to take an initial stab at understanding scope + open bugs
** Keep in Gerrit for now - Neon.1 stream is typically opened when no new changes are expected. Rebasing is relatively easy from Gerrit.
+
* Proposal: remove API once a year
** '''ACTION''' McQ to -1 and argue why.
+
** Given the already long time for consumers to respond to API deprecation, PMC decision was to continue to allow API removal in any release. It was felt that the incremental benefit was outweighed by the need to be able to move forward quickly.
  
* Alex: '''Update on Accessibility'''
 
** broken since GTK 3.8 where accessibility is no longer a module but shipped with GTK itself
 
** 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/>
+
'''Sep 15, 2020''' - Dani, Tom, Lars, Alex
'''April 26, 2016''' - Dani, Lars, Alex, Martin, McQ
+
* M1
* Mickael's API change request ... tried to address feedback from Markus but then got no additional feedback
+
** Next week M1 - Alex to send reminder note
* Alex: '''Accessibility''' - broken on recent GNOME and probably others
+
** Holiday in India on this Friday
** 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/>
+
* Y-Build for Java 16
'''April 19, 2016''' - McQ, Dani, Martin, Alex (regrets: Lars)
+
** Builds should be fixed and can continue to progress on Java 16
* Dani: '''IP Stuff''' on Copyright Updates pinged the Lawyers but no update yet, need to wait
+
* Dani: '''FEEP''' discussed on AC, People were sympathetic to our issues.
+
** General direction that FEEP sponsored work is no different than other contributions
+
** Wayne took the Action Item setting up a meeting with Paul and interested parties.
+
** Website with ongoing FEEP still pending - Dani is tracking
+
* 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/>
+
* SCR upgrade
'''April 12, 2016''' - McQ, Dani, Martin, Lars, Alex
+
** Some issues with EBR maven plugin
* Lars: '''Get rid of the Copyright Year Update Requirement'''
+
** causes versions to be incorrectly represented in p2 meta-data
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485257#c13 bug 485257_c13] EMO: All information is in the git repos
+
** Orbit needs a new lead, will end up impacting us if no replacement found
** 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'''
+
* Tycho being updated to be able to OSGi-fy JARs if they are not there yet.
** Example: When don't have admin rights on a customer machine, can't install anything
+
** How to use this for a feature?
** Dani: With the Gerrit Build Validation, the risk of getting unbuildable code is no longer there
+
** Behaves much like Orbit to produce new versions of the artifact.
** Proposal: Project requests a particular JRE, but the workspace configures treating this as an error or warning
+
** Could be the solution for Orbit needs.
** '''DECISION''' to get rid of the strict error per project.
+
  
* Dani: '''{{bug|475934}} API Change on model processing order'''
 
** 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'''
+
'''Sep 22, 2020''' - no meeting
** EMO working on website update to announce the work being done
+
** Didn't talk about the specific SWT issue around "FEEP should provide clean stuff rather than quick fix"
+
** Already agreed on hiring a person, communication will come in June/July
+
  
* 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/>
+
'''Sep 15, 2020''' - McQ, Dani, Lars, Tom, Alex
'''April 5, 2016''' - McQ, Dani, Alex, Martin, Lars
+
* Dani: Java 15 released today
* Dani: '''FEEP Update'''
+
** 4.17 release together with Marketplace for Java 15 support are ready
** Foundation pays Patrik Suzzi as a contractor to look at Platform bugs (triage, and fix)
+
** JDT Java 15 to be merged this week
** Will focus on critical / blocker bugs initially, or bugs already tagged by committers for 4.6 M7 and 4.6
+
* Dani: Zoom call with password unless each of the PMC members can be added as meeting owner so can start the meeting
** 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)
+
* Alex: 4.18 stream opened and releng work calmed down
* Dani: '''Solaris 32-bit'''
+
* Lars: Cleanup of migration guides
** Will provide Solaris 64-bit binaries, but stop building Solaris 32-bit with Neon
+
** Dani: this will break existing links, so existing content have to stay unless someone does all the work to fix our plans and other links that will break
** Open question: what does this mean in terms of GTK versions ? (GTK3 would be nice)
+
** McQ: help system needs work to focus on the latest stuff/release, what should we do to achieve it? How can we better shape the help system now that having all content ofline is not a requirement?
*** Alex may start asking questions as soon as the binary fragments are in the repo
+
** Alex: do not ship migration, n&n,etc. but rather point to website url from help system
** McQ: Windows 32-bit is still active - future change probably tied to
+
** Alex: this would also reduce manual work for releng (+1 by Dani)
* Dani: '''New Solstice Welcome'''
+
** ACTION ITEM: Alex to work on n&n in help system to use the website content directly as a proof of concept for further work  
** 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/>
+
'''Sep 01, 2020''' - Lars, Alex
'''March 22, 2016''' - McQ, Dani, Alex, Martin
+
* RC1 is fine, no additional requests for RC2
* Dani: we shipped M6 on time. Watch out for API change requests on the PMC mailing list.
+
* Dani: public holiday on Friday (Good Friday) and/or Monday (Easter Monday)
+
* 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
+
'''August 25, 2020''' - Tom, Lars, Alex, Dani
 +
* Dani: sent out Endgame plan, RC1 this week, vacation starting on Friday
 +
* Alex informed about Red Hat's Releng participation
  
<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/>
+
'''August 18, 2020''' - Tom, Lars, Dani
'''February 23, 2016''' - McQ, Martin, Dani, Alex
+
* Dani to create and send out Endgame plan
* Dani: '''Mars.2 is on track'''
+
* Looking into Mac Big Sur launching issue ({{bug|565913}})
* Dani: '''FEEP Update'''
+
** EMO still looking for people bidding on items prioritized by the AC - Pascal to look at some p2ish issues in April
+
* Dani: '''Update on Welcome'''
+
** Brian de Alwis contributed Solstice based Welcome - looking nice and done right, just a 4th theme to select (some artwork needs IP review)
+
* McQ: '''Scrollbars on Windows''' and their appearance
+
** Dark Theme Scrollbars don't currently look good on Windows - proposal to paint in SWT - currently proposed on StyledText only
+
** Dani agrees with Alex that this would open the door to hell
+
** McQ: Having seen AWT take ages in terms of emulating OS appearance makes the idea of painting ourselves not too appealing
+
** Also concerned about special cases (like performance with ultra-long lines etc)
+
** 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.
+
** 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).
+
  
<hr/>
 
  
'''February 16, 2016''' - Alex, Dani, Martin
+
'''August 11, 2020''' - Alex, Dani, Tom, McQ
* no topics
+
* Eclipse Foundation is getting access to an Apple Silicon dev kit
 +
** Will make it available to SWT devs via cloud connectivity
 +
* M3 next week; RC1 following week
 +
* ARM64 port seems to be working fine, except for browser widget (still investigating)
  
<hr/>
 
  
'''February 9, 2016''' - Alex, McQ, Dani
+
'''August 4, 2020''' - Alex, Lars, Dani
* Dani: looking good for Mars.2 (4.5.2) - no RC4 planned
+
* no topics to discuss
* Dani: please take a look at {{bug|466370}} Welcome Screen redesign
+
* Dani: please take a look at {{bug|472614}} Smart Project Importer
+
  
<hr/>
 
  
'''February 2, 2016''' - Dani, Alex, Martin, McQ
+
'''July 28, 2020''' - Tom, McQ
* Dani: '''Foundation Hires''' - Dani hopes they'll find someone in Europe to deal with Releng issues
+
* no topics to discuss
* 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 26, 2016''' - Dani, McQ, Alex, Martin, Lars
 
* Official PMC representation on AC calls - keep McQ listed since he is interested but nominate Dani instead of John
 
* Next round of FEEP coming up - discussed pro and cons
 
* Dani: busy week for the team: Mars.2 (4.5.2) RC2 and Neon (4.6) M5 due this Friday - on track
 
  
<hr/>
+
'''July 21, 2020''' - Tom, Dani, Alex, McQ, Lars
'''January 19, 2016''' - Dani, Alex, Martin
+
* no topics to discuss
* Upstaffing PMC - meet next week
+
* Alex on vacation 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 12, 2016''' - McQ, Dani, Alex, Martin
 
* Dani: '''Upstaffing the PMC'''
 
** Considering "one-time invitation" to get to know candidates better; not so comfortable with a "trial period"
 
* Dani: '''Remove Kim Moir from Platform Releng''' - ideally talk to Kim before moving forward
 
* Dani: {{bug|485429}} '''Remove PDE Build from our drops?'''
 
** Removing PDE Build is one thing - adding a different technology would be wrong, as wrong as adding EGit
 
** McQ and Dani will reach out inside IBM;
 
** Patches are still being submitted; middle ground would be remove from the delivery but keep in repo (and deprecate since not adding features)
 
* Dani: {{bug|485257}} '''Copyright Policy Change''' - waiting on EMO/Legal input
 
* Alex: '''Updating SWT to Java7'''
 
* McQ: '''Travel for EclipseCon'''
 
  
<hr/>
+
'''July 14, 2020''' - Tom, Dani, Alex, McQ, Lars
'''January 5, 2016''' - McQ, Dani
+
* Project status
* Dani: '''PMC Membership'''
+
** M1 shipped last week
 +
** Draft Plan for 4.17 posted - additional fixes done after review
 +
** Release record created for 4.17
 +
* CQ process discussion - new clearly defined process
 +
** Note sent to Wayne to get clarifications on handbook, Wayne has made some edits in response.  We need to review latest handbook
 +
** Should simplify IP clearance for third party libraries
 +
*** If a bundle is approved by clearly defined it can be added with no CQ as long as the mavin URLs/coordinates are vetted by clearly defined
 +
*** Orbit should soon automate the linking to clearly defined approvals for bundles added.  Currently a work in progress by Roland at Orbit.
 +
*** The ratings system at clearly defined is not used.  Only the license check is used.
 +
** PMC needs to review latest handbook on the topic ... As of now we should move forward with the new process
 +
*** If concerns arise later we will need to take actions to correct
 +
* {{bug|565066}} - Needs some attention to the solution and testing
 +
** attempt to make incremental installation be consistent with resolution of a fresh install (or -clean).
  
<hr/>
 
'''December 15, 2015''' - McQ, Dani, Martin, Alex
 
* No calls until Jan.5
 
* Looking for a new PMC member
 
  
<hr/>
+
'''June 23, 2020''' - no call
'''December 8, 2015''' - McQ, Alex, John, Dani
+
* Discussed {{bug|483803}} regarding the BREE for org.eclipse.core.jobs.
+
** PMC decided to move it back to JavaSE-1.7 but keep databinding on JavaSE-1.8
+
* Dani: Reminder: {{bug|475185}} Plan Update 1 - Due with Neon M4 next week
+
  
<hr/>
+
'''June 16, 2020''' - no call
'''December 1, 2015''' - McQ, Alex, Martin, Dani
+
* McQ: The new 5-Dollar Raspberry Pi and Orion (Java server works just fine on the Pi2).
+
** Node server is a bit smaller but single-user and no git - nice for developing node apps though
+
* Dani: '''Mars.2 Endgame Plan sent'''
+
* Dani: {{bug|475185}} Plan Update 1 - Due with Neon M4 next week
+
  
<hr/>
+
'''June 9, 2020''' - Alex, Dani, McQ, Lars, Tom
'''November 25, 2015''' - McQ, Martin, Alex
+
* McQ: message to guide the community got no public reactions so far
* Alex: '''Bumping SWT to Java8'''
+
* Dani: bug reports needed for JDT, do we have PMC agreement?
** Lars wants to use Lambdas {{bug|481195}}; Markus keller wants static helper methods;
+
** Alex: For me that was approved after jdt-dev vote ended
** Stephan Herrmann - University Research for Thread safety through typed annotations
+
** AGREED
*** Are they ready to contribute? - Probably yes, needs to be clarified; having better dev support for Thread Safety will be a huge help
+
* Dani: RC2 done, no major bug so far but still monitoriing for regressions
*** Dani: Thinks that going to Java8 feels a bit early for SWT, which is at the bottom of the technology stack ... would prefer 1 year later
+
* Alex: 4.17 stream open, not finished until 4.16 if final so all apichecks and etc. are in proper shape
*** John: Lambda support doesn't necessarily require SWT to be Java 8 itself (it could just be more lambda friendly)
+
* Tom: OSGi R8 merge after stabilizing 4.17 stream
**** Won't help with base listeners, but probably with mouse events and related .. follow up in the bugreport
+
* Tom: OSGi Move to Java 8 right after that
**** Labdas are more than syntactic sugar, it's more efficient ... still there is more value in Thread safety annotations
+
* Dani: Switch to Java 11 as min version as it was already announced to happen in 4.17 stream shortly
*** McQ: Assumes there would be an extensive discussion on cross-project anyways ... but there is evidence now we could get value from doing this.
+
* Dani: '''Update on Move of platform.text'''
+
** Approval from IP, will soon move to platform.ui - will keep platform.text bugzilla.
+
* John: '''FEEP'''
+
** As discussed on the [[Architecture Council]]
+
* McQ: '''Platform Support'''
+
** Many Platforms are not really active - IBM keeps alive some of them, for example RHEL4
+
** Recent mailinglist asking for Mac 32bit, have we done enough on announcements ?
+
** '''Agreement''' there's no case for catering more to people who don't read announcements and follow the project. Having a mailinglist ask once in a while is OK.
+
** Dani: Planning Update for Neon / M4 - please comment on the bug.
+
*** John: Plan document is not really exhaustive on the oldest working Platform - RHEL4 surely won't work in Neon.
+
** Alex: Consider a "Build your Own" approach for the more obscure Platforms? - Frees us from keeping older binaries in sync
+
*** Did that for ARM32 and ARM64 in master - can build by just calling maven
+
*** McQ: Who would ever validate that scripts are still valid... (Linux community: provides no binaries at all, who validates?)
+
*** Alex: Providing scripts is a lot less work than providing stable and widely compatible binaries (about 1/3 of the work)
+
  
<hr/>
 
'''November 18, 2015''' - Alex, John, Dani
 
* Dani: EclipseCon NA 2016 submission from our team:
 
** https://www.eclipsecon.org/na2016/session/scaling-eclipse-high-dpi-dots-inch-monitors-challenges-and-solutions
 
** https://www.eclipsecon.org/na2016/session/java-9-support-eclipse
 
* John: mentioned FEEP
 
** Alex has concerns that there's not an equal opportunity for everyone
 
* Alex: new Lucene version: would like to put it in
 
** cross-projects has already been asked and we got no negative vote
 
** CQs are approved
 
** seems to be blocked by Orbit
 
** ==> Alex to find out why and report back next week in the PMC call
 
  
<hr/>
+
'''June 2, 2020''' - Alex, Dani, McQ, Lars, Tom
 +
* Inactive committer clean up for Eclipse project for the 4.16 release started via {{bug|563720}}
 +
* Infrastructure is really slow for RC2 release
 +
* RC2 bug queue is really low, one restart issue which is currently under investigated by Tom
 +
* Discussion about the JDT cleanup e-mails
 +
** Need to ensure community discussions are positive and respectful.
 +
** Expectations here should come from leadership
 +
*** LibreOffice did this in the past to great success.
 +
** Committers can vote against bugs but the tone of the discussion is important.
 +
** PMC will respond via the public mailing list within a week
  
'''November 11, 2015''' - McQ, John, Dani
 
* Discussed new meeting time that works for Martin
 
** John to send a note that proposes Tuesday, 11:00 EST / 17:00 CET (starting in two weeks)
 
* John: Alex mentioned at EclipseCon that there's no one in SWT team overlooking cross-platform, e.g. to craft new APIs
 
** owning one platform is a full-time job
 
** would need another person in SWT
 
** for now one of the two co-leads needs to own that task - Dani to talk to Pradeep and the co-leads
 
* John to Dani: how was EclipseCon
 
** Dani: Great! Lots of talking to people; spent quite some time at the Hackathon; only saw 4 talks
 
  
<hr/>
+
'''May 26, 2020''' - Alex, Dani, McQ
 +
* Closed all M3 bugs; RC1 looking good
 +
* Tips&tricks, new&noteworthy, contributions to the newsletter in progress
 +
* Chromium integration CQ approved -- https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21808
  
'''October 28, 2015''' - McQ, John, Alex, Dani
 
* Dani: Discuss new meeting time that works for Martin
 
** decided that John will send out a doodle poll
 
* Dani: Discuss our position regarding the removal of committer emeritus ({{bug|480670}})
 
** everyone agreed that we would like to keep this for the following reasons:
 
*** it is a good way reward those committers who invested lots of their time and made significant contributions to a project
 
*** it makes no sense to remove something that currently works and ask projects to maintain this on their website
 
** we have to make sure that the emeritus list doesn't get stale
 
  
<hr/>
+
'''May 19, 2020''' - Tom, Dani, Lars, Alex
 +
* Dani: Issues with the build infrastructure, might endanger M3, the team got a working build for testing
 +
* Dani: PowerPC hardware was donated so builds are starting again for it
 +
* Alex: CQ process might get simpler based on blog post from Wayne, Alex to test and validate with Wayne https://blogs.eclipse.org/post/wayne-beaton/revising-eclipse-ip-due-diligence-process-third-party-content
 +
* Lars: Question if we want to allow "EGit" commit style in Eclipse top-level project. Agreement was to allow it but not to recommend it or enforce it
  
'''October 21, 2015''' - McQ, Alex, Dani
 
* Dani: so far no negative vote in the vote to move platform.text into platform.ui
 
* McQ: Martin can no longer join, McQ would like to move the meeting
 
** detailed several alternatives but no fit yet
 
** decided to continue the discussion in our next meeting
 
  
<hr/>
+
'''May 12, 2020''' - Tom, Dani, McQ, Lars, Alex
 +
* Update to themes
 +
** Preference being added for choosing square vs round tabs
 +
** Intern from Alex's team is taking up the work
 +
** Update to Windows theme to be Windows 10
 +
* Alex brings up changes to CQ requirements.  Need to read up on Wayne's post about this and discuss in a future call if we can change how the project does CQs
 +
* Who is running dark theme?
 +
** Need someone to cover test of Dark Theme on Linux.  Lars indicated that he runs with Linux Dark Theme and can help in coverage
 +
** Dani described the various members of his team that cover the rest of the platforms
 +
* Request to contribute to article on what is new in the release for a June newsletter.  Lars to contribute improvements in the Dark theme.  General request to others to contribute anything else.
 +
* ppc64le build troubles
 +
** Been having ongoing issues with the university hosted ppc64le machine we use to build support for ppc64le
 +
** Currently the ppc64le build has been disabled
 +
** Need to find alternatives
 +
*** May be able to use something from IBM public cloud
 +
*** Other suggestions: McQ - look towards using emulation, Alex - could do cross-compilation
 +
** Need to plan if ppc 10 will supported in the future
  
'''October 14, 2015''' - McQ, John, Alex, Dani
 
* Dani: Community asked to move platform.text into platform.ui (see [https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html])
 
** 3 solutions:
 
*** make the move
 
*** make a more radical move to merge everything into 'Platform'
 
*** leave things as is and let new people join platform.text
 
** McQ: merging everything together is not an option. Skills are too different. Resources, Debug and SWT need to be kept separate.
 
** Dani: fine with the move as long as it does not serve as argument to merge everything into one pot
 
** Alex: committers need to accept the move
 
** PMC decision: OK with the move but Dani to ask the platform.text and platform.ui committers whether they are both OK with it. Dani to become co-lead of Platform UI
 
  
* John from Board Meeting: Eclipse Foundation wants to change perception that Eclipse is just an IDE. Therefore they would like to change the name of our project ("Eclipse").
+
'''May 5, 2020''' - Dani, Alex, Lars, McQ, Tom
** McQ:
+
*** this will not be for free. The name is used at many places (code, webpage, Help) and also by companies in their marketing
+
*** maybe we just have to accept we made a mistake in the beginning and now live with it
+
*** can't think of a good name - which indicates we shouldn't change it ("Platform" is not good and "Eclipse SDK" or "Eclipse IDE" hide that it is the base for "RCP" apps)
+
** decided to talk about this again in the next call
+
  
<hr/>
+
* M2 shipped on time
 +
** Dark theme rebuild for M2 due to severe issue
 +
* ICU4J removal note sent
 +
** Lars - 2 years notice period needed?
 +
** Agreement: it's needed as we expose it in API and still have usages in internals so we need time to clean up ourself
 +
** EPPs cleanup - some blocked by JDT still using it, some by WTP, Rust probably the first one to be icu4j clean
 +
* Roundes vs square ctabfolder
 +
** Number of themes to be reduced
 +
** Performance not being measurable
 +
** Agreement: add preference to switch the rounded vs
 +
** Agreement: when preference is available Square is default
 +
* Windows theme update -
 +
** Fix colors to match Windows 10
 +
** GTK looks way more sane as more effort has been invested to keep it current
 +
** Don't set colors but use the colors from the OS theme is the recipe
 +
** Ugly white line on windows dark theme needs bugzilla open
  
'''October 7, 2015''' - McQ, John, Alex, Dani, Martin
 
* Dani: '''{{bug|108668}} Default Text Encoding UTF-8 ?'''
 
** On Linux and Mac, the Platform encoding is UTF-8 ; on Windows it's Cp1252 in most countries around the globe, even with Windows 10
 
** Using the Platform encoding ensures interoperability with all local tools (editors, compilers, ...)
 
*** '''Desire for UTF-8 only for Windows exchanging files with users on other systems'''
 
*** '''Changing the encoding of an existing workspace after the fact is a no go''' (risk of data corruption when loading/saving a file, some encodings are lossy)
 
*** '''Using an encoding different than the OS encoding is problematic too''' (risk of data corruption when importing or D&D files from the OS)
 
** Proposal 1: UTF-8 on new empty workspaces on Windows ? --&gt; Might mean that external tools don't work as expected
 
** Proposal 2: Make users aware (Restore Oomph Welcome, which was disabled via {{bug|459486}}) ? --&gt; But many users don't understand implications, other tools also don't do this
 
** Proposal 3: Ask for encoding when team-sharing since only team-shared projects cause issues (eg EGit hook) ? --&gt; But on "push" it may be too late
 
** Martin: Encoding describes content, so should be managed with the content (as a project setting)
 
*** '''--&gt; Proposal 4: Move to a model where we encourage setting the project-level encoding preference'''
 
**** When creating a project, set the workspace default on project level automatically --&gt; ensures that projects remain sane over their lifetime
 
**** For projects lacking the project-level preference, introduce a Problem Marker (Warning) with quick fix to either UTF-8 or workspace default
 
** '''Decision:'''
 
*** '''We won't change the workspace default''' -- no use breaking existing users
 
*** '''We'll set the project encoding pro-actively'''
 
** Open questions:
 
*** Do we need tooling to convert project from encoding A to encoding B (if project preference was set incorrectly initially) ?
 
*** Shall we try setting source encoding on drag-and-drop, or shall the project dictate the policy ?
 
  
<hr/>
+
'''April 28, 2020''' - Dani, Alex, Lars
'''September 30, 2015''' - McQ, John, Alex, Dani
+
* Dani: will send a note to PMC list asking to approve new Debug leadership (Sarika)
+
* Dani: we should finalize our API removal discussion from last week
+
** agreed that APIs marked for removal have to be annotated with @noreference, @noextend and @noimplement
+
** agreed that components should be allowed to remove API but they have to provide good reasons
+
** agreed that we won't allow to delete APIs simply because they are deprecated
+
** agreed that the PMC will decide case by case i.e. there will be no general rule
+
** regarding version numbering we decided to also decide this case by case
+
** Dani to update the removal document and have it reviewed by the PMC
+
  
<hr/>
+
* PMC decided that the OS specific themes should be removed, https://bugs.eclipse.org/bugs/show_bug.cgi?id=562227
 +
* Windows light theme should become better https://bugs.eclipse.org/bugs/show_bug.cgi?id=551462
 +
* Dani - This week is M2, no special freeze or testing but we will contribute our build from Friday to the simrel
 +
* Databinding analyis was done by Jens Lindstroem and it looks good for an API compliant solution
 +
* Alex will prepare the information for cross that we will drop ibm icu from the SDK build
  
'''September 23, 2015''' - Dani, John, Alex, Martin
 
* Dani: '''JDT Core''' - Co-lead going to step up
 
* Dani: '''API Removal Discussion'''
 
** Q1: When do we actually delete API? What's the benefit compared to the pain that we cause ?
 
*** Example of methods that don't do anything any more or do wrong things -- those should be removed
 
*** Example TableTreeViewer : Continue having the API doesn't hurt, there's no significant benefit removing it
 
**** Alex: TableTree was completely broken on GTK for 2-3 years ... keeping such components that don't work properly lowers the quality
 
**** Dani: Is there actual proof of bugs ? Or could it be working fine on Windows RCP ? If it's deprecated, people use it at own risk; do we really need to break them, if it provides value to some people on some Platforms ?
 
**** John: In TableTreeViewer case, EMF had some generic code (was unclear if the path was ever taken) and CDT could update easily
 
*** '''Summary''': scheduling for removal is OK with good arguments. Give Adopters a chance to respond before removal takes place.
 
  
** Q2: '''How to deal with the versions?'''
+
'''April 21, 2020''' - McQ, Alex, Tom, Lars
*** Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
+
* Q: How do we deal with ICU removal from data binding?
**** Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
+
** Need to follow standard API removal rules
**** For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
+
*** Deprecate old API and offer new API
**** Plugins who don't care recompiling may have to live with ClassNotFoundException
+
*** Remove deprecated API after 2 years
**** Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
+
** Can we put the old stuff in a fragment that could be removed?
*** '''Summary:''' Handle the Major with care -- in most cases, the cost of updating the major is not justified by the benefit.
+
* Theming: rounded tabs versus square tabs ({{bug|562221}})
 +
** Should we offer it at all?
 +
** Alex: Don’t increase the number of themes or options
 +
** Lars: Square tabs are faster
 +
** If speed is significant, we should consider changing the default
  
** John: '''Announcement''' When thinking about removing something, we should announce that far and wide and ask for feedback
 
*** Martin: But which channel is as effective as actually removing it ? There's always who don't actually listen...
 
*** John: Still, giving a possibility to listen is important. Agree that mentioning in the release docs is not enough.
 
*** Dani: When making a release, also send message with a link to the removals page (for all removals that are planned)
 
** John: Mechanisms for maintaining binary compatibility while only breaking source compatibility (but it's a lot of work!)
 
*** Dani: Agree, in this case better just leave it in there
 
  
** Alex: What to do next time, can we remove more stuff ?
+
'''April 14, 2020''' - McQ, Dani, Alex, Tom, Lars
*** Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
+
* Dani
 +
** M1 shipped, no problems so far
 +
** Using ECJ from M1 to build the SDK has some issues, there are people working on it
 +
** 4.16 plan to be published this week
 +
* Unanimous decision to continue to use Zoom as usual
  
** John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
 
*** Eg release but without all the deprecated at certain well-known point in time eg every 3-5 years
 
*** '''AI''' ''continue that discussion on the Architecture Council''
 
  
** '''Summary:''' Essentially do what we did, plus more communication upfront, allow people to respond before deletion happens (to avoid churn)
+
'''April 7, 2020''' - McQ, Dani, Alex, Tom, Lars
*** Committers still need to be able to delete stuff when they find it necessary.  
+
* Dani
*** Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
+
** Created [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_16.xml 4.16 plan]
 +
** Created [https://bugs.eclipse.org/bugs/show_bug.cgi?id=561643 release record for 4.16]. Corresponding bug is {{bug|561643}}
 +
** Sent note to add planning bugs for 4.16
 +
** '''Please review and provide feedback if any'''
 +
** After some infrastructure issues we have a good test build and currently things look good for M1 this week
 +
* Alex seconded the infrastructure issues and missing test results
 +
* ICU4J ({{bug|560312}}): we decided to remove it piece by piece from projects where possible and where someone is interested to do it. The ICU bundle itself will stay, and we will follow the API removal process when we are ready to remove it, i.e. no usage in the SDK anymore
  
* Alex: '''Bumping the minimum GTK version again''' (may cause issues on Platforms like AIX -- to be discussed when it's time)
 
  
 +
'''March 31, 2020''' - Dani, Alex, McQ, Tom, Lars
 +
* Dani: Contacted the ICU4J owner. He updated {{bug|560312}}, PMC members will review the comment and we will discuss next week
 +
* Dani: Planning bugs are created slowly for 4.16. Will send a reminder to the list to submit more. Started to work on plan and release record.
  
<hr/>
 
'''September 16, 2015''' - John, Martin
 
* John: '''API Removal Discussion'''
 
** No urgency now -- changes have been reverted for now, and scheduled for 2017
 
** Updating the major of a bundle knowingly breaks everyone/most adopters
 
*** In the past, breaking changes have often been small enough to work without increasing the major
 
*** One can argue that removing TableTreeViewer is big enough to warrant updating the major
 
** Versioning packages has not been done in the past due to the huge upcoming maintenance effort when starting to do so
 
** "Release Version" is decoupled from "bundle versions" already (and may move to date-based versions eg "2016.1" with rolling updates moving forward
 
** --&gt; will have more discussion next week
 
  
<hr/>
+
'''March 24, 2020''' - Alex, McQ, Tom
'''September 9, 2015''' - Dani, Alex, Martin, John, McQ
+
* Dani: Regrets for the call (Eclipse Board call)
* John: '''Planning Council Updates'''
+
* Alex: status updates
** 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
+
** JDT merged Java 14 in master
** Mid December rather than end to avoid churn, so this one is a little shorter
+
** Build instability due to infra status
** Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
+
* Alex: OSGi R8 modules support - what is it?
** McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
+
** Tom: ability to represent external content in the OSGi framework
 +
** Alex: Will it allow shipping eclipse plugins as JPMS modules to ease native library handling?
 +
** Tom: Haven't found any clear example how JPMS handles this, so good example is needed before could be looked further.
  
* Software is getting more important - would be good to better support multicore
 
  
* John: '''IntelliJ change in licensing / sales model'''
+
'''March 17, 2020''' - Alex, McQ, Lars Tom, Dani
** Many eclipse-positive comments on the announcement blog
+
* ICU4J use still under discussion
** Possibility putting Money on Eclipse Development may become interesting for companies in this context
+
** Dani still to contact ICU4J owner
 +
* Shipping Java 14 and 4.15 this week
 +
* Java 14 work will be merged to master on Wednesday
  
<hr/>
 
'''September 2, 2015''' - Dani, Alex, Martin, John
 
* Dani: '''EclipseDay India''' on Saturday, 200 attendees wanted to join, hat to cut to 150
 
** Keynote by Mike Milinkovich - large Community
 
  
* Dani: '''Policy for and Mars.2'''
+
'''March 10, 2020''' - Lars, Tom
** Do we want to stick to the "Service" model or allow feature updates ?
+
* Dani: Regrets for the call (vacation)
** Mars.1 winding down -- sticking to "Critical Fixes Only" for that
+
* ICU4J use still under discussion
** Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
+
** if we can be confident that performance and language support are of *similar* quality, we should work towards removing icu4j because it reduces complexity for us, in addition allowing for smaller RCP apps
** Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
+
** note that we already have mixed usage -- some components using icu4j and some not
*** Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
+
* to clarify approvals that require a project lead can be done by a project lead for any of the Eclipse Project subprojects
*** Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed
+
** as usual, the project lead should take care to understand the change and its implications before approving
 +
* we will move to Jetty 10 (and thus to Java 11) for the fall release
 +
* RH will be leading releng for 4.16
  
'''August 26, 2015''' -
 
* Dani/Alex/Martin can't join (traveling)
 
  
<hr/>
+
'''March 3, 2020''' - no meeting
'''August 19, 2015''' - Alex, Dani
+
* nothing to discuss
+
  
<hr/>
 
'''August 12, 2015''' - John, Dani
 
* John asked whether we run on Windows 10
 
** Dani: yes, the team already tested on it a few weeks ago. Runs smoothly one bug so far. Browser widget works despite new browser (Edge)
 
** ''Martin (added after the meeting): A CDT update is needed to keep the Terminal from hanging (see {{bug|474327}}, will release with Mars.1). Got some duplicates already. Workaround is switch the Win10 Console to "Legacy Mode".''
 
* Dani would like to get plan feedback by Friday EOD
 
  
<hr/>
+
'''February 25, 2020''' - Dani, McQ, Tom, Alex
'''August 5, 2015''' - McQ, John, Dani, Alex, Martin
+
* Dani: Created and sent Endgame plan
* PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
+
* Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
** adding another release before Christmas might be a next step - even if Platform contributes identical bits
+
* 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
  
* Dani: '''[[Eclipse/Mars Retrospective]]'''
 
** Move more components to Tycho build? (Would still need Ant to test against final build/bits)
 
** Contribution Review Dates: joined by some components but not all
 
** Error Reporter: Interesting to look at top ten but the sheer number is too big
 
*** John - based on Orion experience with similar error reporting :
 
**** Looking at changes in reported issues is more interesting than looking at reports themselves
 
**** Reports help getting contributions (But, Dani finds that "just adding a null check" is often not what's desired for Java .. though helpful for Javascript)
 
  
* Dani: Foundation IP team doesn't require updating copyright notices per contribution any more (since that information is in git anyways)
+
'''February 18, 2020''' - McQ, Alex, Dani, Lars, Tom
** The Project has to agree
+
* Dani: need to work on IP Log, Release Review and Endgame Plan
** Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
+
* Lars: ECF - will we update to the latest
** Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
+
** Alex: is in the works. Scott needs to provide us with the update
** Dani to sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02422.html request for voting]
+
* 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
  
* Dani: Switching to '''Jetty 9.3.x (which requires JRE 8)'''
 
** JRE 8 from Oracle (and also from IBM) exists for all Reference Platforms
 
** Except Solaris, because we only support Solaris 32-bit and the JRE only exists as 64-bit
 
** But the Plan for Neon is to have 64-bit Solaris support
 
** New Language features in Java 8 are adopted, contributors would like to start using Java 8
 
** McQ: In the past, staying on older Java was desired to enable more widespread use ... today, this argument does not seem valid any more, in fact likely more contributions / community is enabled by moving to Java 8
 
** Dani: Only concern is some "non reference" Platforms like HP-UX might not have JREs initially; but that's OK as long as the reference platforms are good
 
** '''AGREEMENT''' to move to JRE 8 and allow projects to use Java 8 in their code.
 
  
* Dani: Looking for a contributor for SWT improvements for GTK3
+
'''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.
  
* Martin: '''libwebkitgtk-3 on Ubuntu 14 forcing GTK 2''' not working ?
+
-> Alex to contact Denis and to cc the other PMC members
** Alex: Using libwebkitgtk-4 which is much more stable, but not implementing the full SWT API
+
** Most distros don't ship libwebkit for gtk-2 any more since it's not supported upstream any more and has many security issues
+
  
* Alex: '''Build SWT at the Foundation'''
+
'''February 4, 2020''' - McQ, Dani, Tom
** Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month
+
* 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
  
  
<hr/>
+
'''January 28, 2020''' - McQ, Alex, Dani, Tom, Lars
'''July 15, 22 and 29, 2015''' -- no meeting
+
* 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
  
<hr/>
 
'''July 8, 2015''' - McQ, Dani, John, Martin, Alex
 
* John: '''Cross-Language Tooling Discussion''' on the eclipse.org-architecture-council and ide-dev mailing lists
 
* decided to cancel the upcoming July meetings
 
  
<hr/>
+
'''January 21, 2020''' - Dani, Tom, Lars
'''July 1, 2015''' -- no meeting
+
* 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
  
<hr/>
 
'''June 24, 2015''' - McQ, Dani, Martin, Alex
 
* Dani: '''Java 9''' - <a href="http://marketplace.eclipse.org/content/eclipse-java%E2%84%A2-9-support-beta-mars">EAR Feature Patch</a> on the Marketplace NOW
 
** No JARs any more - JRE is doing things internally using "jimage" format; updated search etc to create projects and work against them
 
** If the Jimage filesystem provider isn't backported, one has to run the IDE on Java9 in order to code Java9
 
** Modules are just a list of packages (and can refer to other modules) - no real JSR describing the plan yet - seems like just a replacement of "Profiles" (and JARs)
 
  
<hr/>
+
'''January 14, 2020''' - McQ, Alex, Dani, Tom
'''June 17, 2015''' - Dani, John, Martin, Alex
+
* Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
* John: '''Mars''' Platform in good shape for Mars - EPP respin for Error Reporting
+
* Dani: Plan updated to remove Windows 7
* Dani: '''Crashes with Java 8''' - Potentially will add to the online README
+
* Alex: Felix Dependencies for SCR done
** Happens in the JIT, with latest Oracle Java 8 (with 8 Cores and very specific circumstances)
+
** confirm fix for {{bug|544571}}
** See {{Bug|465693}} - Probably https://bugs.openjdk.java.net/browse/JDK-8078262
+
** releng disruptions during update, but recovered.  More disruptions expected as we update dependencies for March release.
* Alex: '''XDG Application''' - looks like Docker but a similar idea
+
** 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.
** Environment description of the runtime - helps specifying the line-up of library versions that we test against and use
+
* Some discussion about gitlab option at foundation. {{bug|537913}}
** Big part of GNOME / GTK already pushing for it, might make sense to consider alignment
+
** What happens to gerrit work flow for review?
** GNOME working towards compiling with a really old compiler, such that the physically identical bits can run against a large set of distros
+
** Would dropping bugzilla happen or can we migrate all issues?
** See https://wiki.gnome.org/Projects/SandboxedApps
+
** Without migration it is a no-go for us
** But if you want to try it out please read https://blogs.gnome.org/alexl/2015/06/17/testing-rawhide-apps-using-xdg-app/
+
** Currently no plans to move Eclipse project to gitlab at this time.
  
<hr/>
 
  
'''June 10, 2015''' - Dani, Alex, Martin
+
'''January 7, 2020''' - McQ, Alex, Dani, Tom, Lars
* Dani: 4.5RC4 looking good, no more fixes planned
+
* Dani: Created initial 4.15 plan - please have a look
* Dani: Working on Java 9 feature patch
+
* Dani: Created release record for 4.15
* Alex: PC discussing a change in the release train
+
* Dani: Sent a note to teams to create their 4.15 plan items/bugs
** Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
+
* Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
** From Platform point of view, stability is key. Some key contributors not interested doing
+
** Unanimous decision: Yes
** Martin: How to also cater to contributors who want their contributions released soon ?
+
* Dani: Discuss (again, see below) resolution for stale bugs
*** Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
+
** We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
*** Or, open up a new "experimental" stream ?
+
** We will only auto/mass close existing stale bugs with notification turned off
*** Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
+
* Change rules about x-internal exports ({{bug|553709}})
* Martin: Tested eclipse-installer (Oomph), looking really really good now
+
** 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
  
<hr/>
 
'''June 3, 2015''' - Alex, Dani, Martin, McQ, John
 
* Dani: '''Mars Endgame'''
 
* Dani: Please vote for release review
 
  
<hr/>
+
'''December 10, 2019''' - Alex, Dani, Tom, Lars
'''May 20, 2015''' - Dani, Alex, Martin, McQ
+
* Dani: RC2a respin to be promoted today
* Dani: '''Security Update''' - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
+
* Dani: 4.15 M1 approaching fast (January 10)
* Dani: '''RC2 Build''' - too many bugs assigned, Lars on Vacation, Dani will fill in
+
* Dani: master is open
* McQ: '''Too Many Platforms Built?''' - Who's really hurt by "too many builds" ?
+
* Dani: Version bumps done for now
** Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).
+
** 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
  
<hr/>
 
'''May 13, 2015''' - McQ, John, Alex, Martin
 
* John, Dani - Mars Endgame looking good
 
* Alex - {{bug|465874}} Lucene 5 looking good, almost done - Ready to commit as soon as CQs are in and Mars+1 is open
 
* JDT for Java 9 - will need a wider discussion with EMO on make it easier to publish the work, e.g. in normal builds
 
  
<hr/>
+
'''December 3, 2019''' - Alex, Dani, McQ, Lars
'''May 6, 2015''' - McQ, Dani, Martin, John
+
* Dani: RC2 this week. Supposed to be the end of 4.14 for us.
* Dani: '''Java 9 timing''' - slight delay
+
* Dani: Rules for exporting packages as outlined in [https://wiki.eclipse.org/Export-Package Export-Package] :
* Dani: RC1 preps
+
** Background: {{bug|544977}}.
** 2-day test pass went fine - 2 severe issues found, will be addressed
+
** We need to discuss whether we want to relax those rules.
** Request to watch PMC mailing list for API exceptions and defect approvals
+
** Tom to file a bug report.
* John: '''PC Discussion on Release Cycles'''
+
** Multiple releases per year PLUS maintenance streams seems like overkill
+
** Consider an approach like Orion that just moves constantly forward
+
** Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
+
*** A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
+
*** Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
+
*** Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?
+
  
  
'''April 15, 2015''' - Dani, John, McQ, Alex, Martin
+
'''November 26, 2019''' - Alex, Dani, McQ
* Dani: '''Java 1.7 Changes'''
+
* GTK minimum version being upgraded: 3.14 -> March; 3.22 -> June
** Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
+
* Target environments upgraded for 4.14, PMC members please verify
** Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
+
* Standalone SWT download was broken in M3; Fixed in RC1
*** Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
+
* Mac downloads are now being notarized
*** Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
+
* Red Hat team will help with release engineering work
** Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
+
* Dani: '''Batik 1.6 update'''
+
  
<hr/>
 
'''April 8, 2015''' - Dani, Martin, Alex, John, McQ
 
* Dani: '''Batik''' - Platform is good, Train may need to update, perhaps updating one bundle only would suffice. John will follow up.
 
* Alex: '''SWT for GTK 3 News'''
 
** GTK port finally decoupled from X11 - it renders on Wayland now, can switch the renderer to a pure HTML one
 
** This opens up opportunities (but depends on hosts that have GTK).
 
  
 +
'''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}}
  
<hr/>
 
'''April 1, 2015''' - McQ, Alex, Martin, Dani (Regrets: John travelling)
 
* Alex: '''GTK 3.16''' seeing issues again - fixed some crashes, but scrolling is still entirely broken
 
** SWT uses a number of things that GTK declares as "implementation detail"
 
* PMC approval on piggyback CQ's (AC question forwarded by John)
 
** Dani sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02332.html our position] to John in order to update the AC
 
  
<hr/>
+
'''November 12, 2019''' - Tom, Alex, Lars, Dani
'''March 18, 2015''' - Dani, Alex, Martin, McQ, John
+
* M3 next week
* John: '''EclipseCon''' - Bigger this year due to LocationTech (750 attendees)
+
** Many open bugs targeted for 4.14 M3 and 4.14
** Mark Reinhold keynote and "after-session" on Java 9
+
** Request for contributors to act on them and retarget
** Much interest in Orion JS tooling / editor, also on desktop
+
* Gerrit reviews
** Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
+
** Dedicated time to spend on review patches from non-commiters and non-employees of IBM and Red Hat
* Dani: {{bug|458730}} '''Mars Plan Update'''
+
** Time still to be considered
* Dani: '''e4 project leadership''' approved by EMO
+
* Dani to check whether IP Log and review are needed for 4.14
* Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list
+
* 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
  
<hr/>
 
  
'''March 11, 2015 - no meeting (EclipseCon)'''
+
'''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
  
<hr/>
+
'''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)
  
'''March 4, 2015''' - Dani, McQ, Martin, John
 
* Dani: '''e4 leadership''' - Dani will volunteer to co-lead
 
* Dani: '''BREEs''' - documentation about how to pick the EE
 
** Recommending the "earliest generally supported JRE that provides the capabilities you need"
 
** Would like an URL on the page pointing to the most recent plan (talking to Wayne)
 
* John: '''greatfix contest'''
 
** Dani: Working well - some very small contributions but some also very large (eg Customize Perspective fixes)
 
* John: '''EclipseCon''' - numbers looking good; join Planning Council Breakfast as delegate for Dani
 
  
<hr/>
+
'''October 08, 2019''' - Tom, McQ, Alex, Dani, Lars
'''February 25, 2015''' - Dani, Martin McQ
+
* PPC64LE machine
* No topics
+
** 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
  
<hr/>
 
'''February 18, 2015''' - Dani, Alex, Martin
 
* Alex: '''Building Native Launchers'''
 
** Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
 
** Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
 
** Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
 
* Dani: Great initiative, but other (non-EF) builders must not be broken
 
** EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
 
* Alex is willing to spend time to get Linux builds running; but can't help with other architectures
 
** Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
 
* Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
 
** Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
 
** Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
 
  
* Alex: '''{{bug|459399}} - Policy for recommended minimum execution environments for bundles'''
+
'''October 01, 2019''' - Tom, McQ, Alex, Dani, Lars
** Dani: It works today
+
* Dani to look into plan and release record for 4.14
*** To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
+
* Stale bug reports should be closed as WONTFIX if there is not a response to the stale bug flag
*** To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
+
* Changes on Gerrit to allow fast-forward merges
** Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
+
** deferred to next week
*** But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
+
*** Suggested BREE for new bundles has already been changed by Lars
+
* Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
+
* No conclusion so far (Alex and Dani disagree)
+
  
* Dani: '''e4 leadership'''
 
** Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier
 
  
<hr/>
+
'''September 24, 2019''' - Tom, McQ, Alex, Dani
'''February 11, 2015''' - Dani, Alex
+
* discussed enabling fail on warnings on JDT projects
* no topics
+
** Dani to clarify with Roland
  
<hr/>
 
  
'''February 4, 2015''' - Dani, Alex, Martin
+
'''September 17, 2019''' - Tom, McQ, Alex, Dani
* Alex: With GTK-3.15.[345] , Eclipse is entirely unusable
+
* Crash issue on win32 - respin done
** Alex has some dirty workarounds to make it start, but still many issues like trees not painted, ...
+
* Java 13 GA
** Crash on startup identified to be GTK bug. Fix to be released in 3.15.6 https://git.gnome.org/browse/gtk+/commit/?id=edec64cda3d4518b4e87d5ea5d287d4570ba9933
+
** marketplace entry works with M3 and onwards
* Dani: Working on Solaris 64-bit
+
** 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
 +
 
 +
 
 +
'''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 [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?
 +
 
 +
--> 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: [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
 +
 
  
<hr/>
+
'''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 [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.
  
'''January 28, 2015''' - Dani, Alex, John
 
* Dani: Switch Mac OS X 10.9 with 10.10 in Mars target environments
 
** No objections
 
* Alex: Looking for any Eclipse related activity @Fosdem
 
<hr/>
 
  
'''January 21, 2015''' - Dani, Alex, Martin, McQ
+
'''January 16, 2018''' - Alex, Lars, Dani, Tom
* Alex: '''Process for allowing non-committers extended bugzilla privileges (for bug triage)?'''
+
* Native builds at eclipse.org status (Lars):
** Dani: Yes a process exists. Send bugzilla username to Dani.
+
** Dani: swt is done for some time already
* Alex: '''New resource for helping with SWT'''
+
** Dani: launchers after M5 is released to prevent breakage
* Dani: '''Platform/UI co-lead'''
+
* GTK launcher changes (Alex):
* Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --&gt; IBM SWT Team considering to invest in getting patches in for 64-bit Solaris
+
** 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
  
<hr/>
 
'''January 14, 2015''' - Dani, Alex, Martin, McQ, John
 
* Dani: Update on Platform/UI Leadership: Daniel Rolka left IBM and for now has no time to contribute. He stepped down as co-lead and nominated Lars Vogel
 
* Dani: Solaris x86 64-bit support - patches exist, but no machine available. No luck to get one from Oracle or via Eclipse Foundation. We will not support Solaris x86 64-bit unless someone makes a machine available
 
<hr/>
 
  
'''January 7, 2015''' - Dani, Alex, Martin, McQ, John
+
'''Januar 09, 2018''' - McQ, Alex, Lars, Dani
* Dani: '''Platform/UI Leadership'''
+
* Updates from Dani:
* John: '''Git security issue''' - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP
+
** Ian Skerrett is leaving the Eclipse foundation
<hr/>
+
** 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 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]
 
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]

Revision as of 11:46, 17 February 2021

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

Febr 17, 2021 - Lars, Alex, McQ

  • Looks good for 4.19 release
  • Mac ARM has to wait for the 4.20 release, as the team fights multiple issues
  • Top-level project page can currently only be edited by Tom, other PMC members also have access to it https://projects.eclipse.org/projects/eclipse/who

Dec 15, 2020 - Lars, Alex, McQ

  • 06. January 2021 is the next meeting
  • How can PMC increase the awareness of the project leads / committers?
    • Maybe invite the project leads once per month to the PMC meeting?
    • Discussion how we can increase the JDT community

Dec 01, 2020 - Lars, Alex, McQ

  • RC1 is out; final touches on RC2
  • How can we remove the confusion about "e4" project?
    • e4 has always been intended to be a sandbox project where people could try things that are experimental or are on a longer timeline
    • Should be renamed to make it clear this isn't about leftovers from the Eclipse 4.0 work (maybe "eNext"?)
    • Should clean up repos
      • Remove repos that just hold code that has already moved to the platform
      • Remove repos that are no longer getting any investment
      • Work toward moving things that are active/useful into the platform (e.g. "spies" to PDE)

Nov 24, 2020 - Lars, Alex, McQ

  • PMC is considering the potential of an SDK / IDE working group at the foundation
  • Discussion Do we need the extra releng work to create p2 repositories for milestones?
    • Lot of extra work and sometimes goes wrong
    • All I-Builds are anyway available

-> PMC decided to drop the additional p2 repository -> Alex will be sending out an email about it to inform potential users of the special p2 repos

    • Discussion about the purpose of the milestone week at all

-> Decision not to change the process for now, as the additional testing and focus has also some benefits


Nov 17, 2020 - Lars, Alex, Tom, McQ

  • Release 4.18 winding down
    • SWT churn for Linux and Mac Big Sur
    • Does not appear the Foundation got the new Mac Hardware for testing
  • Planning Council discussion
    • Dani filled the Eclipse TLP representation role on the Council
    • Alex can take the lead to that role
    • Alex will look to find a replacement for the tools TLP representative


Nov 10, 2020 - Lars, Alex, Tom, McQ

  • Still dealing with the loss of Dani
  • Discussed representation of JDT on PMC
  • Stabilizing for M3
  • Some releng issues with Java 15 and 16
  • Tom began investigating p2 ECF httpclient dependency


Nov 10, 2020 - Lars, Alex, Tom, McQ

  • Still dealing with the loss of Dani
  • Discussed representation of JDT on PMC
  • Stabilizing for M3
  • Some releng issues with Java 15 and 16
  • Tom began investigating p2 ECF httpclient dependency


Nov 3, 2020 - Lars, Alex, Tom, McQ

  • Dani!


Oct 27, 2020 - Lars, Tom

  • Nothing to discuss


Oct 20, 2020 - Lars, Tom, McQ, Alex

  • EclipseCon is running virtual this week
  • Agreement that removal of API should only before M1 release
  • Proof of concept for using Java 11 http client instead of ECF should be done
  • if we remove ECF we should send out an announcement and keep it for at least one release
  • Decision to start using the @Deprecated(since = "x.y.z", forRemoval = true) for planned API removals if the bundle can use Java 11, wiki for API removal should be updated

Oct 6, 2020 - Dani, Tom, McQ, Alex

  • M1 under control
  • Release train materials being worked
  • Moved to Jetty 9.4.32
  • ECF — need to simplify how we consume http client
    • could use Java11 http client instead, but this would require significant development effort
    • Tom/Alex to take an initial stab at understanding scope + open bugs
  • Proposal: remove API once a year
    • Given the already long time for consumers to respond to API deprecation, PMC decision was to continue to allow API removal in any release. It was felt that the incremental benefit was outweighed by the need to be able to move forward quickly.


Sep 15, 2020 - Dani, Tom, Lars, Alex

  • M1
    • Next week M1 - Alex to send reminder note
    • Holiday in India on this Friday
  • Y-Build for Java 16
    • Builds should be fixed and can continue to progress on Java 16
  • SCR upgrade
    • Some issues with EBR maven plugin
    • causes versions to be incorrectly represented in p2 meta-data
    • Orbit needs a new lead, will end up impacting us if no replacement found
  • Tycho being updated to be able to OSGi-fy JARs if they are not there yet.
    • How to use this for a feature?
    • Behaves much like Orbit to produce new versions of the artifact.
    • Could be the solution for Orbit needs.


Sep 22, 2020 - no meeting


Sep 15, 2020 - McQ, Dani, Lars, Tom, Alex

  • Dani: Java 15 released today
    • 4.17 release together with Marketplace for Java 15 support are ready
    • JDT Java 15 to be merged this week
  • Dani: Zoom call with password unless each of the PMC members can be added as meeting owner so can start the meeting
  • Alex: 4.18 stream opened and releng work calmed down
  • Lars: Cleanup of migration guides
    • Dani: this will break existing links, so existing content have to stay unless someone does all the work to fix our plans and other links that will break
    • McQ: help system needs work to focus on the latest stuff/release, what should we do to achieve it? How can we better shape the help system now that having all content ofline is not a requirement?
    • Alex: do not ship migration, n&n,etc. but rather point to website url from help system
    • Alex: this would also reduce manual work for releng (+1 by Dani)
    • ACTION ITEM: Alex to work on n&n in help system to use the website content directly as a proof of concept for further work


Sep 01, 2020 - Lars, Alex

  • RC1 is fine, no additional requests for RC2


August 25, 2020 - Tom, Lars, Alex, Dani

  • Dani: sent out Endgame plan, RC1 this week, vacation starting on Friday
  • Alex informed about Red Hat's Releng participation


August 18, 2020 - Tom, Lars, Dani

  • Dani to create and send out Endgame plan
  • Looking into Mac Big Sur launching issue (bug 565913)


August 11, 2020 - Alex, Dani, Tom, McQ

  • Eclipse Foundation is getting access to an Apple Silicon dev kit
    • Will make it available to SWT devs via cloud connectivity
  • M3 next week; RC1 following week
  • ARM64 port seems to be working fine, except for browser widget (still investigating)


August 4, 2020 - Alex, Lars, Dani

  • no topics to discuss


July 28, 2020 - Tom, McQ

  • no topics to discuss


July 21, 2020 - Tom, Dani, Alex, McQ, Lars

  • no topics to discuss
  • Alex on vacation next week


July 14, 2020 - Tom, Dani, Alex, McQ, Lars

  • Project status
    • M1 shipped last week
    • Draft Plan for 4.17 posted - additional fixes done after review
    • Release record created for 4.17
  • CQ process discussion - new clearly defined process
    • Note sent to Wayne to get clarifications on handbook, Wayne has made some edits in response. We need to review latest handbook
    • Should simplify IP clearance for third party libraries
      • If a bundle is approved by clearly defined it can be added with no CQ as long as the mavin URLs/coordinates are vetted by clearly defined
      • Orbit should soon automate the linking to clearly defined approvals for bundles added. Currently a work in progress by Roland at Orbit.
      • The ratings system at clearly defined is not used. Only the license check is used.
    • PMC needs to review latest handbook on the topic ... As of now we should move forward with the new process
      • If concerns arise later we will need to take actions to correct
  • bug 565066 - Needs some attention to the solution and testing
    • attempt to make incremental installation be consistent with resolution of a fresh install (or -clean).


June 23, 2020 - no call

June 16, 2020 - no call

June 9, 2020 - Alex, Dani, McQ, Lars, Tom

  • McQ: message to guide the community got no public reactions so far
  • Dani: bug reports needed for JDT, do we have PMC agreement?
    • Alex: For me that was approved after jdt-dev vote ended
    • AGREED
  • Dani: RC2 done, no major bug so far but still monitoriing for regressions
  • Alex: 4.17 stream open, not finished until 4.16 if final so all apichecks and etc. are in proper shape
  • Tom: OSGi R8 merge after stabilizing 4.17 stream
  • Tom: OSGi Move to Java 8 right after that
  • Dani: Switch to Java 11 as min version as it was already announced to happen in 4.17 stream shortly


June 2, 2020 - Alex, Dani, McQ, Lars, Tom

  • Inactive committer clean up for Eclipse project for the 4.16 release started via bug 563720
  • Infrastructure is really slow for RC2 release
  • RC2 bug queue is really low, one restart issue which is currently under investigated by Tom
  • Discussion about the JDT cleanup e-mails
    • Need to ensure community discussions are positive and respectful.
    • Expectations here should come from leadership
      • LibreOffice did this in the past to great success.
    • Committers can vote against bugs but the tone of the discussion is important.
    • PMC will respond via the public mailing list within a week


May 26, 2020 - Alex, Dani, McQ


May 19, 2020 - Tom, Dani, Lars, Alex

  • Dani: Issues with the build infrastructure, might endanger M3, the team got a working build for testing
  • Dani: PowerPC hardware was donated so builds are starting again for it
  • Alex: CQ process might get simpler based on blog post from Wayne, Alex to test and validate with Wayne https://blogs.eclipse.org/post/wayne-beaton/revising-eclipse-ip-due-diligence-process-third-party-content
  • Lars: Question if we want to allow "EGit" commit style in Eclipse top-level project. Agreement was to allow it but not to recommend it or enforce it


May 12, 2020 - Tom, Dani, McQ, Lars, Alex

  • Update to themes
    • Preference being added for choosing square vs round tabs
    • Intern from Alex's team is taking up the work
    • Update to Windows theme to be Windows 10
  • Alex brings up changes to CQ requirements. Need to read up on Wayne's post about this and discuss in a future call if we can change how the project does CQs
  • Who is running dark theme?
    • Need someone to cover test of Dark Theme on Linux. Lars indicated that he runs with Linux Dark Theme and can help in coverage
    • Dani described the various members of his team that cover the rest of the platforms
  • Request to contribute to article on what is new in the release for a June newsletter. Lars to contribute improvements in the Dark theme. General request to others to contribute anything else.
  • ppc64le build troubles
    • Been having ongoing issues with the university hosted ppc64le machine we use to build support for ppc64le
    • Currently the ppc64le build has been disabled
    • Need to find alternatives
      • May be able to use something from IBM public cloud
      • Other suggestions: McQ - look towards using emulation, Alex - could do cross-compilation
    • Need to plan if ppc 10 will supported in the future


May 5, 2020 - Dani, Alex, Lars, McQ, Tom

  • M2 shipped on time
    • Dark theme rebuild for M2 due to severe issue
  • ICU4J removal note sent
    • Lars - 2 years notice period needed?
    • Agreement: it's needed as we expose it in API and still have usages in internals so we need time to clean up ourself
    • EPPs cleanup - some blocked by JDT still using it, some by WTP, Rust probably the first one to be icu4j clean
  • Roundes vs square ctabfolder
    • Number of themes to be reduced
    • Performance not being measurable
    • Agreement: add preference to switch the rounded vs
    • Agreement: when preference is available Square is default
  • Windows theme update -
    • Fix colors to match Windows 10
    • GTK looks way more sane as more effort has been invested to keep it current
    • Don't set colors but use the colors from the OS theme is the recipe
    • Ugly white line on windows dark theme needs bugzilla open


April 28, 2020 - Dani, Alex, Lars


April 21, 2020 - McQ, Alex, Tom, Lars

  • Q: How do we deal with ICU removal from data binding?
    • Need to follow standard API removal rules
      • Deprecate old API and offer new API
      • Remove deprecated API after 2 years
    • Can we put the old stuff in a fragment that could be removed?
  • Theming: rounded tabs versus square tabs (bug 562221)
    • Should we offer it at all?
    • Alex: Don’t increase the number of themes or options
    • Lars: Square tabs are faster
    • If speed is significant, we should consider changing the default


April 14, 2020 - McQ, Dani, Alex, Tom, Lars

  • Dani
    • M1 shipped, no problems so far
    • Using ECJ from M1 to build the SDK has some issues, there are people working on it
    • 4.16 plan to be published this week
  • Unanimous decision to continue to use Zoom as usual


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

  • Dani
    • Created 4.16 plan
    • Created release record for 4.16. Corresponding bug is bug 561643
    • Sent note to add planning bugs for 4.16
    • Please review and provide feedback if any
    • After some infrastructure issues we have a good test build and currently things look good for M1 this week
  • Alex seconded the infrastructure issues and missing test results
  • ICU4J (bug 560312): we decided to remove it piece by piece from projects where possible and where someone is interested to do it. The ICU bundle itself will stay, and we will follow the API removal process when we are ready to remove it, i.e. no usage in the SDK anymore


March 31, 2020 - Dani, Alex, McQ, Tom, Lars

  • Dani: Contacted the ICU4J owner. He updated bug 560312, PMC members will review the comment and we will discuss next week
  • Dani: Planning bugs are created slowly for 4.16. Will send a reminder to the list to submit more. Started to work on plan and release record.


March 24, 2020 - Alex, McQ, Tom

  • Dani: Regrets for the call (Eclipse Board call)
  • Alex: status updates
    • JDT merged Java 14 in master
    • Build instability due to infra status
  • Alex: OSGi R8 modules support - what is it?
    • Tom: ability to represent external content in the OSGi framework
    • Alex: Will it allow shipping eclipse plugins as JPMS modules to ease native library handling?
    • Tom: Haven't found any clear example how JPMS handles this, so good example is needed before could be looked further.


March 17, 2020 - Alex, McQ, Lars Tom, Dani

  • ICU4J use still under discussion
    • Dani still to contact ICU4J owner
  • Shipping Java 14 and 4.15 this week
  • Java 14 work will be merged to master on Wednesday


March 10, 2020 - Lars, Tom

  • Dani: Regrets for the call (vacation)
  • ICU4J use still under discussion
    • if we can be confident that performance and language support are of *similar* quality, we should work towards removing icu4j because it reduces complexity for us, in addition allowing for smaller RCP apps
    • note that we already have mixed usage -- some components using icu4j and some not
  • to clarify approvals that require a project lead can be done by a project lead for any of the Eclipse Project subprojects
    • as usual, the project lead should take care to understand the change and its implications before approving
  • we will move to Jetty 10 (and thus to Java 11) for the fall release
  • RH will be leading releng for 4.16


March 3, 2020 - no meeting


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