Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

(Meeting Minutes)
 
(285 intermediate revisions by 10 users not shown)
Line 8: Line 8:
 
= Meeting Schedule =
 
= Meeting Schedule =
  
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every wednesday at 10.30am EST'''.
+
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every Tuesday at 11.00am EST'''.
  
 
= Meeting Minutes =
 
= Meeting Minutes =
'''July 25, 2012:'''
 
* '''CBI Build'''
 
** For SR1, the build can produce what the Release Train needs ... but not all the extra validation
 
** Need to run both builds for now ... until the CBI team's bytecode verifier produces the same output
 
** CBI team continues to look at the list of diffs and improve their builder
 
** Platform team would be OK dropping the legacy build once the bytecode validator has no diffs
 
** Platform team can't commit more resources to CBI now (Paul Webster already heavily involved)
 
* '''Losing Commits on the Orion git repo'''
 
** Dozen commits or so
 
** Might be a defect in the Orion git tools, but the server side should prevent that !!!
 
** DenyNonFastForward should have protected ... need an extra layer of protection ?
 
  
 +
'''Aug 16, 2016''' - Dani, Martin, Lars
 +
* 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/>
 
<hr/>
'''June 27, 2012:''' - McQ, Dani, Martin, John
 
* Eclipse Demo Camps - none in Ottawa
 
* Going to skip the arch calls for all of July - leave the PMC slot in place.
 
* Should keep an eye on the Community feedback for Eclipse 4
 
  
 +
'''Aug 09, 2016''' - Dani
 +
* no one joined - had private conversation with McQ later
 +
** '''guys, please announce when you can't join. I can make better use of my time than waiting for you in the call ;-) - thanks.'''
 
<hr/>
 
<hr/>
'''June 13, 2012:''' - McQ, Dani, Martin, John
 
  
* Discussed the ECF rebuild request ({{bug|382206}}). Arguments in favor: it is a safe change, it reverts the situation to where it was in RC3 and earlier. Arguments against summarized in https://bugs.eclipse.org/bugs/show_bug.cgi?id=382206#c20.
+
'''Aug 02, 2016''' - Dani, Martin, Alex
* We will need to tag the release but we can wait until we are officially done (week of June 25th).
+
* Dani: New [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_7_draft.xml Oxygen Plan Format]
 +
** '''AI Dani''' ask Denis about aggregating the Sub Wiki's into the master page
 +
* Alex: SWT Fragments for ARM64 etc
 +
** Tycho doesn't support auto-selecting fragments - in contact with Jan and Tobias
 +
** Dani: Would like to revert changes - don't want to punish people who are not interested in fragments
 +
** Not really an SWT problem, so editing .target files would be a clean solution
 +
** Will probably go with empty (dummy) fragments without natives, as that's the simplest solution
 +
* Dani: SWT team - Lakshmi going to Sweden, will not be available until end 2016
 +
** Arun is mostly back, Sravan is now on Releng
 +
** Need to push further on building at the Foundation!!
 +
** Alex: Getting CentOS for building ... but test machines are on SLES11, which is too old, will need at least SLES12
 +
*** Dani: Will need an owner at the Eclipse Foundation to ensure this proceeds ! Alex agreed to further drive this.
 +
* Target Env: Dropping REL6 -- reference platform for testing will only be REL7 (though will continue to run on REL6)
 +
** Reducing support level this year, in order to prepare for only supporting GTK3 next year
  
 
<hr/>
 
<hr/>
'''June 6, 2012:''' - McQ, Dani, Martin, John, Andrew
 
  
* Discussion of how to handle test failures for final build. Most of the remaining failures are infrastructure issues related to our move to Hudson for tests. We will document the failures through bugs, and include a note on the build results page for the final build explaining the failures
+
'''July 26, 2016''' - no meeting
* Discussion of whether we need a 3.9 release. Unanimous conclusion was that we do not see a need for it. Reducing to one stream will greatly reduce our development overhead and encourage consolidation around the single stream.
+
 
* Discussion of how to handle the disappearance of org.eclipse.equinox.concurrent from our RC3 builds. This was never deliberately included in the platform, but was present due to a greedy optional dependency from ECF. By very close 3/2 decision PMC decided to leave it alone and document the disappearance in porting guide, readme file, release review material, and cross-project list.
+
'''July 19, 2016''' - no meeting
  
 
<hr/>
 
<hr/>
 +
'''July 12, 2016''' - McQ, Lars, Alex
 +
* Dani: Hackathon summary
  
'''May 23, 2012:''' - McQ, Dani, Martin
+
<hr/>
* McQ: '''CBI / Tycho builder''': Paul Webster driving Platform efforts (AI Martin notify about {{bug|359719}})
+
'''July 5, 2016''' - Lars, McQ, Alex, Dani, Martin
* Martin: {{bug|380984}} ant / Orbit respin? - Unclear for now
+
* Lars: SWT move to Java 8
* McQ: Finally figured out some long-standing bug eg "Variables view sometimes empty"
+
* Alex: Initial builds of GTK 2.24 for AIX - planning to bump minimum GTK version to 2.24
** Dani: It's 2 issues: First-time switch to Perspective deferred to 4.2.1, but {{bug|379818}} is finally fixed
+
** Will remove non-cairo drawing, this is where most of the breakage happens
** The actual underlying defect had been in there for years
+
** Ubuntu 12.04: 2.24.10 / 3.4.5
 +
** 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/>
 
<hr/>
'''May 16, 2012:''' - McQ, John, Dani, Martin
+
'''June 28, 2016''' - McQ, Martin, Alex
* Dani: '''Version Number''' in branding features gets auto-generated and 3.8 version is now higher than 4.2 (since 3.8 build runs after 3.8)
+
* Discussion about Language Server Protocol
** John thinks it's not a big deal
+
** MS sponsoring hackathon in Zurich, Dani expected to go there
* John: '''CBI Patches''' - CBI has lots of patches downstream in their POM's ... RC2 is the last chance getting that in
+
** The protocol has an Open Source license, but there is no Open Source Governance ... who owns the specification?
** Auto-generating the POM.XML would be nice but that's not how things work today
+
  
 
<hr/>
 
<hr/>
'''May 9, 2012:''' - McQ, John, Dani
+
'''June 21, 2016''' -  
* John: Classic update can still be enabled via capabilities - should we remove it?
+
*  
** Dani: in general "yes", but too late now
+
** McQ: too late, but make sure we do it for Kepler
+
  
 
<hr/>
 
<hr/>
'''May 2, 2012:''' - McQ, Dani, Martin, Andrew, John
+
'''June 14, 2016''' - Dani, McQ, Martin, Lars
* John: '''Forking of SWT''' 3.8 and 4.2 are now separate Streams with CTabFolder implementation being the only difference
+
* McQ: '''Mattermost / Slack''' for communication
* Dani: '''Icons''' (not discussed)
+
** 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
 +
* no topics
  
 
<hr/>
 
<hr/>
'''April 18, 2012:''' - McQ, Dani, Martin, Andrew, John
+
'''May 31, 2016''' - Dani, Martin, Lars, McQ, Alex
* Martin: [[E4/Scripting]] initiative
+
* Dani: '''IP Log'''
** McQ thinks the E4 Application Model should be exposed as a DOM to scripting .. anything other than utilizing the e4 DOM for hiding a view feels wrong
+
** The tool did not work, but it was manually submitted and approved
*** Martin: Approach is very pragmatic - don't see anybody investing into new Frameworks at this point but converging on what already exists
+
** 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
*** If this goes towards macro recording, the recorder should utilize the e4 app model
+
* Dani: '''Release Review'''
** Signing up on the [https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev eclipse-scripting-dev] mailing list will keep people in the loop (expect low volume)
+
** Reply to the public E-Mail with comments or +1
* Dani: '''API Approval Process''' Approval on Bug plus sent to eclipse-pmc list (like last year)
+
* Dani: '''Update Jetty to 3.9.3'''
* John: '''PDE Committers''' - perception of not being open
+
** Consensus to update - Jetty team working on fixing their update site
** McQ would like to see a plan item for next year "actively promote more committers from outside"
+
* Dani: '''RC4 Status Update'''
* Martin: [[Asterisk]] - will need a dialin for Dani in Switzerland; '''AI Dani''' forward his dialin to Martin for the time being
+
** Cooling down - maybe 2 fixes from SWT, 1 in Platform/Text Search, and the approved doc fix for deprecating the mac command
  
 
<hr/>
 
<hr/>
'''April 11, 2012:''' - McQ, Dani, Martin, Andrew, John
+
'''May 24, 2016''' - Dani, Lars, Martin
* Martin: '''LTS vs Quality/Fixes in Current Stream''' - Like John's reply making the link between the two
+
* Dani: '''IP Log Generator''' - New version is unable to deal with Eclipse Project, Wayne is working on it
* McQ/John: '''Builds''' - Moving forward
+
* Dani: '''Release Review''' - Deadline next week (June 2)
* McQ: '''CBI Builds''' - Platform not going to take any ownership but will be a consumer like others - still shooting for Juno SR1
+
* Dani: '''Deprecation Request from Brian'''
* Andrew: '''4.2 Builds in Fedora 17''' - Testing now
+
** Command org.eclipse.ui.cocoa.fullscreenWindow -- all PMC agree on the deprecation although late, since it only affects docs
* McQ: '''IBM Ottawa Team moving to new building''' - expect delays during next couple days
+
* 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/>
 
<hr/>
'''April 4, 2012:''' - McQ, Dani, Martin, Andrew
+
'''May 17, 2016''' - Dani, Lars, Martin, Alex
* Dani: '''VM Requirements''' - Help no longer works on Java 5, this surprised some people... but Project Plan talks about a Java 6 req now
+
* Dani: '''{{Bug|475184}} Neon Plan Update 2'''
** Martin suggestion: on the "Required JVM" table in the Project Plan, add a 2nd column with closure of BREE including all pre-reqs (continue having 1st column the BREE of the bundle itself auto-generated)
+
** Windows 10 and Ubuntu 16.04 will be added as "active" Platforms that people do work on
* Dani: '''Jeff still mentioned as PMC member'''
+
** SWT would like to remove Windows 8 and Ubuntu 12.04 from the list of reference Platforms
** '''AI Dani''' send E-Mail
+
*** Alex: Ubuntu 12.04 has GTK 3.10 which is hard to support
* Martin: '''Concern about Platform Quality''' - eg SWT Redraws on 3.7.x - Old-time committers moving away
+
**** Correction (Markus): Ubuntu 12.04 has GTK 3.4.2. Ubuntu 14.04 has GTK 3.10.8
** McQ: Platform team's focus will continue being maintenance, and new Platform support ... team's capacity is going down, but SWT is not affected mosted
+
*** Message is clear: "Supposed to run on older Platforms, but these are the primary ones" - including last 2 LTS ones
** Martin: Code contributions are easy, hi-quality triage and review are harder
+
** Agreement to keep Windows 7 and remove Windows 8
** Martin: Re-think the idea of having committers paid by the Foundation and Member Companies paying their share
+
** '''AI Dani''' to check if SuSE 11 is right (12 been out since 2 years)
*** Example: Why would Pascal review p2 in his sparetime ... but if he gets paid per bug his experience can be extremely valuable
+
* Dani: '''Copyright End Date''' - EMO: To be decided per project
*** Be more creative on resourcing side
+
** IBMers will have to continue updating the copyright end date, regardless of what other companies do
** McQ: In favor of putting more structure in place similar to LTS ("hire people for fixes") ... just continue with LTS ?
+
** Copyright tool: Only the person who made a change is allowed to update the Copyright notice
*** IBM will have a need for fixes for at least another 8 years .. but that's a very self-serving focus
+
*** gray area: actually fixing the date can be considered a change
** [[Image:Ok_green.gif]] '''AI Martin''' send E-Mail to Mike to keep the ball rolling
+
** Alex is in favor of consistency across the project
* Dani: {{bug|375292}} '''Reference to Marketplace in the SDK'''
+
* Dani: '''Policy for Neon.Update Releases''' - What to allow in, which rules to apply on the endgame
** Martin: "Classic" is a Building Block but "Packages" are for end users
+
** Martin: Fact is, that the Update stream is built less often, and thus also tested less often
** McQ: The purity of the SDK in itself isn't relevant
+
** Rule: Any fix or feature must be in master first (and may be backported thereafter)
*** Martin: Why not just create a new package "Classic" which is at +3 and pulls in egit + marketplace ... the process for building is all in place, may just need a package reviewer
+
** Will want "some" features in Update, but probably not all of them - '''decision''': discuss feature by feature at PMC
*** [[Image:Ok_green.gif]] '''AI Martin''' mail Markus
+
** 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/>
 
<hr/>
'''March 21, 2012:''' - McQ, Dani, Andrew, Martin
+
'''May 10, 2016''' - Dani, Martin, Alex, McQ
* McQ '''Oracle Java on Mac'''
+
* Dani: '''Policy for what should go into Neon.Update Releases'''
* Dani '''denyNonFastForward'''
+
** Would like to be more flexible than in the past - discussion point for next week
* McQ '''JDT Team might see some losses'''
+
* Martin: '''RHEL7 -- GTK3 versus --launcher.GTK_Version 2'''
* Andrew '''Running OpenJDK tests now on ARM''' :)
+
** GTK2 rendering still much more reliable than GTK 3 - forced to release commercial software with the GTK2 fallback for now
 +
*** Drawback: Even with MATE desktop using GTK2 (for accessibility), the Browser widget webkitgtk2 is not easy to get since not in the official repos
 +
** Alex: Desktops are moving faster - adopting change very quickly - cannot keep up with the investment that the Community currently makes in SWT
 +
*** Heavily limiting what we support looks like the only viable approach at the moment...
 +
*** There's 2 big groups of bugs: (a) "Next" version of GTK, and (b) "Old" version like Ubuntu 13.04 which has 3.10 - can we limit support to "latest" ?
 +
*** Martin: Need "LTS" Linux (RHEL 7, RHEL 6, Ubuntu 12, 14 - soon 16).
 +
** Alex: Gnome people have come up with a "Container environment" for GTK - could ship Eclipse that way ?
 +
*** Limitations: Updates must come through this application - already using Gimp from such an environment
 +
*** Might be able to deliver Eclipse that way next year (Oxygen)
  
 
<hr/>
 
<hr/>
'''March 14, 2012:''' - McQ, Andrew, Dani, John
+
'''May 3, 2016''' - Dani, Martin, Alex, McQ
* Losing Eclipse project release engineer next week
+
* [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02598.html Brian's request on the PMC list]
* David Williams is stepping in to help with our builds until Juno
+
** McQ: Why would we care about adding small enhancements in RC1 when we should focus on testing and critical fixes
* Most immediate issue is that our build needs elevated privileges to tag, sign, and promote builds
+
** Dani: Two parts in the change - the original one (approvable), but another change also sneaked in (enable the prefix search) - not approvable
** kmoir was the only committer with sufficient privileges
+
** Alex: People don't want to wait for getting in an improvement...
** We either need to give another committer sufficient rights, or give build user access it needs
+
** McQ: OK for adding as feature to Neon.1 , but Neon.0 should be focused on bug fixes
** Could use hooks to ensure build user isn't doing anything other than tagging
+
** Keep in Gerrit for now - Neon.1 stream is typically opened when no new changes are expected. Rebasing is relatively easy from Gerrit.
** All agreed the build user approach was the best option. John to open bug against foundation to carry it out
+
** '''ACTION''' McQ to -1 and argue why.
 +
 
 +
* 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/>
 
<hr/>
'''March 7, 2012:''' - McQ, Andrew, Martin, John
+
'''April 26, 2016''' - Dani, Lars, Alex, Martin, McQ
* John: '''API Deletions''' {{bug|370248}} - PMC agrees.
+
* Mickael's API change request ... tried to address feedback from Markus but then got no additional feedback
* McQ: '''Common Build Infrastructure at the Foundation'''
+
* Alex: '''Accessibility''' - broken on recent GNOME and probably others
** Shipping Platform Juno bits built by PDE ... but Foundation wants EPP packages built by Tycho; Platform can't support this
+
** Accessibility is important. Have reports from users who say "Eclipse works for them"
*** Reason might be that 4.2 is planned to be the start of LTS and VLTS .. ok for now if LTS bits are different since not publicly available
+
** McQ: Need to keep some focus and look at what we can do for Neon.1
*** Plus, LTS really starts after Juno SR2 ... Platform might be in a better position for Tycho by then
+
* Alex: '''Platform.ui generification of project'''
*** In Linux, Fedora also builds by themselves ... but assumption is that people come to Fedora support first
+
** Dani: Won't get a consistent story when done piecemeal - needs to be done "per framework" and not necessarily "per plugin"
** Martin, Andrew really concerned about fragmentation and duplication of effort ... eg what if the qualifiers don't match
+
** McQ: It's a huge effort - enough by itself for one whole release !
** Should be treated as proof of concept but not publicly available until Juno SR2, in order to avoid fragmentation !
+
** Dani: If a meaningful separate unit is found that can be done, but things like e.g. LabelProvider, ContentProvider and TreeViewer can't be done isolated
 +
** Lars: If a smaller unit of generification work is possible, that's permitted when somebody signs up for the work and it has been discussed in the public
 +
** '''ACTION Alex''' to prepare a message for review and then send that.
 +
* Lars: '''Copyright discussion'''
 +
** Not having the end date in the copyright notice makes the copyright invalid.
 +
** The IP Advisory Board will discuss it again.
 +
* Dani: '''Update on FEEP'''
 +
** Paul not reached out yet
 +
** A list now shows what's done or in progress - but no time
 +
* Dani: '''Update on M7'''
 +
** Last 4 builds failed due to infrastructure issues - Maven stuff could not be accessed
 +
** Will try to enable cache on the build side and re-try until the cache is full
 +
 
 +
<br/>
 +
'''April 19, 2016''' - McQ, Dani, Martin, Alex (regrets: Lars)
 +
* 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/>
 +
'''April 12, 2016''' - McQ, Dani, Martin, Lars, Alex
 +
* Lars: '''Get rid of the Copyright Year Update Requirement'''
 +
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485257#c13 bug 485257_c13] EMO: All information is in the git repos
 +
** McQ: OK lifting the requirement but doesn't want wrong information in files .. get rid of all copyright years ?
 +
** Dani: Replacing the end-date by "[see git]" might be an option
 +
** '''ACTION''' McQ or Dani talk to IBM Legal, then decide next week
 +
 
 +
* Lars: '''{{bug|490012}} Remove Project Settings to force strictly compatible JRE'''
 +
** Example: When don't have admin rights on a customer machine, can't install anything
 +
** Dani: With the Gerrit Build Validation, the risk of getting unbuildable code is no longer there
 +
** Proposal: Project requests a particular JRE, but the workspace configures treating this as an error or warning
 +
** '''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'''
 +
** 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/>
 
<hr/>
'''February 29, 2012:''' - Dani, McQ, John, Martin, Andrew
+
'''April 5, 2016''' - McQ, Dani, Alex, Martin, Lars
* John: Orion team received a box full of '''Black Ducks''' to honour their Black Duck Rookie of the Year award
+
* Dani: '''FEEP Update'''
* Dani: '''Gerrit Move'''
+
** Foundation pays Patrik Suzzi as a contractor to look at Platform bugs (triage, and fix)
** John: Important information needs to stay in Bugzilla ... don't pull from outside git exclusively
+
** Will focus on critical / blocker bugs initially, or bugs already tagged by committers for 4.6 M7 and 4.6
* Andrew: '''Platform Defect Contest'''
+
** 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)
** McQ concern: Lots of duplicate bugs would take focus away from the team
+
* Dani: '''Solaris 32-bit'''
** Martin: Could encourage triage as part of the contest, and only count good/new bugs
+
** Will provide Solaris 64-bit binaries, but stop building Solaris 32-bit with Neon
** John: Some low-hanging fruit bugs in Platform UI but not necessarily in 4.x ("helpwanted")
+
** Open question: what does this mean in terms of GTK versions ? (GTK3 would be nice)
** John: Re-introduce the "greatbug" keyword ?
+
*** Alex may start asking questions as soon as the binary fragments are in the repo
*** A greatbug is relevant, new, good description that helps understanding/finding the issue; ideally with a patch.
+
** McQ: Windows 32-bit is still active - future change probably tied to
*** Resolution: '''AI John''' send note to Mike
+
* Dani: '''New Solstice Welcome'''
* John: '''PDE API Moved'''
+
** Some issues with Logo, sometimes it's there sometimes not; Brian working on it, Solstice will become the new default in M7
** Some internal, provisional API was migrated to full API in this release
+
** Currently, ONE product logo must work on all Themes - bad design - probably to be changed
** Someone from SAP (Dimitar Giormov) Asked adding back the provisional API such that they could support 2 versions of Eclipse with one codebase
+
** McQ: Do we mirror the welcome for BIDI ? (Dani thinks yes, saw bugs come along)
** McQ: Would have helped them 4 years ago .. but at the moment don't have enough people
+
* Alex: '''FEEP Process Discussion (around Themed Scrollbars)'''
*** McQ: Question how pervasive their use of the old API is ... how much Reflection would they need to put int
+
** "Scrollbar Theming": Contractor doing work without SWT committers knowing, and disregarding suggestions from the committers
*** One resolution could be OK but only if they provide all the patches
+
*** Looks like the proper fix from committers was not even tried ?
** This kind of duplication is error prone and adds a maintenance burden on the project
+
*** 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/>
 
<hr/>
'''February 22, 2012:''' - Dani, McQ, John, Andrew
+
'''March 29, 2016''' - McQ, Lars, Martin, Dani, Alex
* Repeat of PDE build discussion from last week. We decided to nominate John Arthorne as a committer so we at least have someone to accept community patches. We will revisit after Juno and perhaps do a larger restructuring
+
* Lars: '''PDE Build in Maintenance''' - Officially state this ?
* Communication with eGit: We have written some patches for eGit that have been growing stale. Dani will review the patches, and then send an email to eGit lead asking if there is a particular reason for not accepting them. If there is no problem with the patches we will track down an eGit committer to release them.
+
** PDE Build still works; and we're not yet in a position to replace it (it's needed for manual export)
* Andrew asked about process for approving CQs:
+
** Alex: What about not quite declaring maintenance mode, but state something like "for a new project, you might consider Tycho or something else"
** Any PMC member can feel free to approve CQs
+
** McQ: '''DECISION''' Ensure that on the PDE Build Homepage, we clarify the relationship between PDE Build and other technologies (like Tycho)
** New versions of existing third party libraries are a no-brainer, typically just +1 right away
+
* Lars: '''Integrate more projects into Platform UI?'''
** For new third party libraries we may need a PMC discussion about why the library is needed, what feature it will live in, etc
+
** Having few commits on a component, or overlapping committer list, is not an argument for merging projects
** For code contributions just make sure the legal process has been followed and then +1. We generally trust the judgement of the committer who will process the contribution.
+
** 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/>
 
<hr/>
'''February 15, 2012:''' - Dani, McQ, John
+
'''March 22, 2016''' - McQ, Dani, Alex, Martin
* Some discussion of what to do with PDE Build, which lacks committers. PDE as a whole has barely enough committers to be a functioning project, so maybe we should be looking at a larger restructuring after
+
* Dani: we shipped M6 on time. Watch out for API change requests on the PMC mailing list.
Juno rather than one piece at a time. We lacked quorum to make a decision so we will defer discussion to another week.
+
* 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
  
 
<hr/>
 
<hr/>
'''February 8, 2012:''' - Dani, Martin, Andrew, McQ
+
'''March 1, 2016''' - Dani, Martin
* Andrew: Eclipse stand at '''FOSDEM in Brussles'''
+
* Dani OOO next week
** Lots of people just dropped by to say hi and thanks
+
* Alex: '''{{bug|179924}} SSH-agent authentication''' 3rd party code for SSH using JVM internals
** Mike Milinkovich was showing off Orion; Gunnar and Andrew did others (Web, EclipseRT, C/C++)
+
** Dani: Suggest asking on the bug for confirmation what's the JNA team's plan ... they have a full year time
* McQ: '''4.2 Quality''' ... current list of defects looks manageable to tick all off .. any messaging we want to do ?
+
** 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/>
 
<hr/>
'''February 1, 2012:''' - Dani, Martin, John
+
'''February 23, 2016''' - McQ, Martin, Dani, Alex
* Dani: '''No UA Committers any more''' - move UA under Platform UI such that at least somebody can apply patches
+
* Dani: '''Mars.2 is on track'''
** AI John check with Wayne ... UA is a subcomponent now, may not even need a move review.
+
* Dani: '''FEEP Update'''
* Dani: {{bug|343150}} git '''DenyNonFastForward'''
+
** EMO still looking for people bidding on items prioritized by the AC - Pascal to look at some p2ish issues in April
** Orion could eventually add tooling to support easy workflows in spite of deny on the repo ... but not in this release
+
* Dani: '''Update on Welcome'''
** Ping on the bug again and proceed
+
** Brian de Alwis contributed Solstice based Welcome - looking nice and done right, just a 4th theme to select (some artwork needs IP review)
* John: Decide when to switch 4.2 builds from re-using 3.x binary bundles vs full 4.x builds
+
* McQ: '''Scrollbars on Windows''' and their appearance
** Today, the 4.x testsuite just tests 4.x specific stuff; things like JDT tests just run against 3.8 today
+
** Dark Theme Scrollbars don't currently look good on Windows - proposal to paint in SWT - currently proposed on StyledText only
** Today, cannot generate Javadocs in 4.x today sine it needs the full source
+
** Dani agrees with Alex that this would open the door to hell
** Today, nightlies are running 3.x only (could change to running 4.x nightlies only)
+
** McQ: Having seen AWT take ages in terms of emulating OS appearance makes the idea of painting ourselves not too appealing
** Today, 3.x builds run at IBM and 4.x builds run at Eclipse.org
+
** Also concerned about special cases (like performance with ultra-long lines etc)
** Only few test failures left in the 4.x builds --&gt; ready to switch
+
** 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.
** AI: '''Kim''' to send 4.x test results to the mailing list, consider switching right after M5
+
** 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).
** '''Performance Tests:''' Not yet run on 4.x yet - should be able to run on Denis' vserver
+
*** IBM is going to lose the physical machines for performance tests in 2 weeks ! (Going to migrate to vserver too!)
+
*** Need a new baseline
+
** Andrew: at '''FOSSLC''' in Brussels this week, going to represent Eclipse with Mike Milinkovich, Gunnar Wagenknecht and others
+
* '''Gerrit''': Platform won't jump in as an early adopter this time, wait for other projects first
+
** Not all Platform Unittests can run on Hudson today (need at least some fingerprint tests to get value from Gerrit)
+
  
 
<hr/>
 
<hr/>
'''January 25, 2012:''' - McQ, John, Martin, Andrew, Dani
 
* McQ: '''Note about 4.2 on Release Train'''
 
* Andrew: '''Eclipse 4.2 for Fedora''' - Feature note written for Eclipse Juno led to some discussion at Eng.Steering Committee, but finally approved
 
* Dani: Team down by 1 but no impact (Dani is going to take over responsibilities)
 
* John: '''Build Failures in UA, Update, PDE, p2 yesterday''' after the move to Java 7... nobody watching these, need to find caretakers
 
** UA tests often fail due to a link validity checker, these can be caused by anyone
 
** Certificate Validity issue (Jar signing)
 
  
 +
'''February 16, 2016''' - Alex, Dani, Martin
 +
* no topics
  
 
<hr/>
 
<hr/>
'''January 18, 2012:''' - McQ, John, Martin, Andrew, Dani
+
 
* McQ: '''4.2 quality''' and next steps
+
'''February 9, 2016''' - Alex, McQ, Dani
** More resources found to enable 4.2 as the LTS base - encouraging, although some items still missing
+
* Dani: looking good for Mars.2 (4.5.2) - no RC4 planned
** Fedora 17 think about shipping 4.2m6 (work ongoing) - that would be a large stack on top of 4.2
+
* Dani: please take a look at {{bug|466370}} Welcome Screen redesign
** John: '''Oracle Java 7 as Reference Platform''' now that the most severe issues are fixed (Java 6 EOL is June 2012 !) - that is Oracle, not OpenJDK
+
* Dani: please take a look at {{bug|472614}} Smart Project Importer
*** Not remove Java 6 for now
+
*** Fedora also does all tests on 7
+
  
 
<hr/>
 
<hr/>
'''January 11, 2012:''' - McQ, John, Dani, Martin, Andrew
+
 
* McQ: '''State of Presentation API's'''
+
'''February 2, 2016''' - Dani, Alex, Martin, McQ
** Different API's in 4.2 and 3.x -- will need to deprecate API in 3.x
+
* Dani: '''Foundation Hires''' - Dani hopes they'll find someone in Europe to deal with Releng issues
** Christian suggested deleting API that's not implemented in 4.x to get compile errors ... John thinks that binary compatibility is more important
+
* Dani: '''Neon M5''' went smoothly - M6 will be the API freeze; tomorrow is the last planned RC for Mars.2
*** Plugins will be "mostly OK", presentation API is cosmetic anyways
+
* Dani: '''CQ Deadline''' on Feb.12 for Neon
** McQ: get in touch with clients who use presentation API, telling them what's best to do ... often newer 4.x infrastructure is much better than trying to keep 3.x around forever
+
* Dani: {{bug|486647}} for changing the strategy when opening files not associated with Eclipse
* Andrew: '''Cairo and GTK3'''
+
** With M5, can now use the System Editor (default) or Text Editor - there's a request to always use the text editor
* John: '''4.2 compiling now'''
+
** Dani thinks that for JPG one wants to use the OS
* Martin: '''Updated JSch-0.1.44 version''' - how to announce properly
+
*** Martin agrees, OpenWith and choosing an editor remembers the choice, and one can also remember;
** AI Martin Announce on eclipse-dev and cross-project
+
*** We also show the System Icon in Project Explorer, so using the System Editor by default is natural
** Should also put into migrtion notes and README
+
*** 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/>
 
<hr/>
'''January 4, 2012:''' - McQ, Dani, Martin, Andrew
+
'''January 26, 2016''' - Dani, McQ, Alex, Martin, Lars
* McQ: Pascal's note about p2 leadership .. not sure who could step in and make a commitment (may see the same fate as UA)
+
* Official PMC representation on AC calls - keep McQ listed since he is interested but nominate Dani instead of John
** Tom Watson looking for candidates, but looks like none in McQ's team
+
* 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/>
 +
'''January 19, 2016''' - Dani, Alex, Martin
 +
* Upstaffing PMC - meet next week
 +
* Update Eclipse PMC representation on the AC
 +
** Since only Alex will represent the Eclipse PMC at EclipseCon, should push for not making formal decisions unless there is remote attendance support
 +
* Dani: {{bug|485429}} '''PDE Build''' - looks like a lot of people still use it; OK if moving to a different component, but there's still a dependency:
 +
** Plugin or feature export still needs PDE Build -- Whoever wants to remove it, will need to implement a replacement '''in the Platform'''
 +
** Alex: Platform build currently does double bootstrapping Tycho already ... making this more complex would be a problem
 +
** Introducing other build system into the Platform would be a wrong approach
 +
** Will go ahead with what we have for 4.6
 +
* Alex: As of today's GTK3 build, Eclipse is working fine on Wayland :) thanks to a number of fixes in GTK
 +
** Some GTK developers are now considering Eclipse as part of their regression suite :)
 +
* SWT move to Java 7 was much appreciated; moving forward, how to deal with functional interfaces ?
 +
* Alex would be interested in some styling support in SWT - would simplify some things, at least on GTK
 +
** Could be a very simple API like setStyle(String) - win32 also seems to have some styling support
 +
* Martin: '''Stability of GTK3 on Mars.2 ?'''
 +
** Alex: Many distros do their own hacks, so hard to tell... Mars.2 should be stable on every distro that has a stable GTK3 distro without too many patches
 +
** Can't recommend GTK3 on Ubuntu yet; few things improved lately, but still causes troubles whenever Ubuntu updates their GTK, requires more fixes in SWT; Kubunutu and derivatives might be even worse
 +
*** Good news is that GTK3.16 dropped support for custom theming engines - causes some ugliness but at least it's stable
 +
** Debian or SuSE should be OK;
 +
** Expect Neon GTK3 to be more stable everywhere than GTK2
 +
 
 +
<hr/>
 +
'''January 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/>
 +
'''January 5, 2016''' - McQ, Dani
 +
* Dani: '''PMC Membership'''
 +
 
 +
<hr/>
 +
'''December 15, 2015''' - McQ, Dani, Martin, Alex
 +
* No calls until Jan.5
 +
* Looking for a new PMC member
 +
 
 +
<hr/>
 +
'''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/>
 +
'''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/>
 +
'''November 25, 2015''' - McQ, Martin, Alex
 +
* Alex: '''Bumping SWT to Java8'''
 +
** Lars wants to use Lambdas {{bug|481195}}; Markus keller wants static helper methods;
 +
** Stephan Herrmann - University Research for Thread safety through typed annotations
 +
*** Are they ready to contribute? - Probably yes, needs to be clarified; having better dev support for Thread Safety will be a huge help
 +
*** 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
 +
*** John: Lambda support doesn't necessarily require SWT to be Java 8 itself (it could just be more lambda friendly)
 +
**** Won't help with base listeners, but probably with mouse events and related .. follow up in the bugreport
 +
**** Labdas are more than syntactic sugar, it's more efficient ... still there is more value in Thread safety annotations
 +
*** 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/>
 +
 
 +
'''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/>
 +
 
 +
'''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/>
 +
 
 +
'''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/>
 +
 
 +
'''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").
 +
** 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/>
 +
 
 +
'''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/>
 +
'''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/>
 +
 
 +
'''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?'''
 +
*** Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
 +
**** Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
 +
**** For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
 +
**** Plugins who don't care recompiling may have to live with ClassNotFoundException
 +
**** Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
 +
*** '''Summary:''' Handle the Major with care -- in most cases, the cost of updating the major is not justified by the benefit.
 +
 
 +
** 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 ?
 +
*** Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
 +
 
 +
** John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
 +
*** 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)
 +
*** Committers still need to be able to delete stuff when they find it necessary.
 +
*** Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
 +
 
 +
* Alex: '''Bumping the minimum GTK version again''' (may cause issues on Platforms like AIX -- to be discussed when it's time)
 +
 
 +
 
 +
<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/>
 +
'''September 9, 2015''' - Dani, Alex, Martin, John, McQ
 +
* John: '''Planning Council Updates'''
 +
** 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
 +
** Mid December rather than end to avoid churn, so this one is a little shorter
 +
** Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
 +
** McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
 +
 
 +
* Software is getting more important - would be good to better support multicore
 +
 
 +
* John: '''IntelliJ change in licensing / sales model'''
 +
** Many eclipse-positive comments on the announcement blog
 +
** Possibility putting Money on Eclipse Development may become interesting for companies in this context
 +
 
 +
<hr/>
 +
'''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'''
 +
** Do we want to stick to the "Service" model or allow feature updates ?
 +
** Mars.1 winding down -- sticking to "Critical Fixes Only" for that
 +
** Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
 +
** Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
 +
*** Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
 +
*** Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed
 +
 
 +
'''August 26, 2015''' -
 +
* Dani/Alex/Martin can't join (traveling)
 +
 
 +
<hr/>
 +
'''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/>
 +
'''August 5, 2015''' - McQ, John, Dani, Alex, Martin
 +
* PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
 +
** adding another release before Christmas might be a next step - even if Platform contributes identical bits
 +
 
 +
* Dani: '''[[Eclipse/Mars Retrospective]]'''
 +
** 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)
 +
** The Project has to agree
 +
** Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
 +
** Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
 +
** Dani to sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02422.html request for voting]
 +
 
 +
* Dani: Switching to '''Jetty 9.3.x (which requires JRE 8)'''
 +
** 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
 +
 
 +
* Martin: '''libwebkitgtk-3 on Ubuntu 14 forcing GTK 2''' not working ?
 +
** 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'''
 +
** Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month
 +
 
 +
 
 +
<hr/>
 +
'''July 15, 22 and 29, 2015''' -- no meeting
 +
 
 +
<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/>
 +
'''July 1, 2015''' -- no meeting
 +
 
 +
<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/>
 +
'''June 17, 2015''' - Dani, John, Martin, Alex
 +
* John: '''Mars''' Platform in good shape for Mars - EPP respin for Error Reporting
 +
* Dani: '''Crashes with Java 8''' - Potentially will add to the online README
 +
** Happens in the JIT, with latest Oracle Java 8 (with 8 Cores and very specific circumstances)
 +
** See {{Bug|465693}} - Probably https://bugs.openjdk.java.net/browse/JDK-8078262
 +
* Alex: '''XDG Application''' - looks like Docker but a similar idea
 +
** Environment description of the runtime - helps specifying the line-up of library versions that we test against and use
 +
** Big part of GNOME / GTK already pushing for it, might make sense to consider alignment
 +
** GNOME working towards compiling with a really old compiler, such that the physically identical bits can run against a large set of distros
 +
** See https://wiki.gnome.org/Projects/SandboxedApps
 +
** But if you want to try it out please read https://blogs.gnome.org/alexl/2015/06/17/testing-rawhide-apps-using-xdg-app/
 +
 
 +
<hr/>
 +
 
 +
'''June 10, 2015''' - Dani, Alex, Martin
 +
* Dani: 4.5RC4 looking good, no more fixes planned
 +
* Dani: Working on Java 9 feature patch
 +
* Alex: PC discussing a change in the release train
 +
** Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
 +
** From Platform point of view, stability is key. Some key contributors not interested doing
 +
** Martin: How to also cater to contributors who want their contributions released soon ?
 +
*** Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
 +
*** Or, open up a new "experimental" stream ?
 +
*** Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
 +
* Martin: Tested eclipse-installer (Oomph), looking really really good now
 +
 
 +
<hr/>
 +
'''June 3, 2015''' - Alex, Dani, Martin, McQ, John
 +
* Dani: '''Mars Endgame'''
 +
* Dani: Please vote for release review
 +
 
 +
<hr/>
 +
'''May 20, 2015''' - Dani, Alex, Martin, McQ
 +
* Dani: '''Security Update''' - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
 +
* Dani: '''RC2 Build''' - too many bugs assigned, Lars on Vacation, Dani will fill in
 +
* McQ: '''Too Many Platforms Built?''' - Who's really hurt by "too many builds" ?
 +
** Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).
 +
 
 +
<hr/>
 +
'''May 13, 2015''' - McQ, John, Alex, Martin
 +
* John, Dani - Mars Endgame looking good
 +
* Alex - {{bug|465874}} Lucene 5 looking good, almost done - Ready to commit as soon as CQs are in and Mars+1 is open
 +
* JDT for Java 9 - will need a wider discussion with EMO on make it easier to publish the work, e.g. in normal builds
 +
 
 +
<hr/>
 +
'''May 6, 2015''' - McQ, Dani, Martin, John
 +
* Dani: '''Java 9 timing''' - slight delay
 +
* Dani: RC1 preps
 +
** 2-day test pass went fine - 2 severe issues found, will be addressed
 +
** Request to watch PMC mailing list for API exceptions and defect approvals
 +
* John: '''PC Discussion on Release Cycles'''
 +
** Multiple releases per year PLUS maintenance streams seems like overkill
 +
** Consider an approach like Orion that just moves constantly forward
 +
** Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
 +
*** A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
 +
*** Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
 +
*** Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?
 +
 
 +
 
 +
'''April 15, 2015''' - Dani, John, McQ, Alex, Martin
 +
* Dani: '''Java 1.7 Changes'''
 +
** Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
 +
** Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
 +
*** Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
 +
*** Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
 +
** Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
 +
* Dani: '''Batik 1.6 update'''
 +
 
 +
<hr/>
 +
'''April 8, 2015''' - Dani, Martin, Alex, John, McQ
 +
* Dani: '''Batik''' - Platform is good, Train may need to update, perhaps updating one bundle only would suffice. John will follow up.
 +
* Alex: '''SWT for GTK 3 News'''
 +
** GTK port finally decoupled from X11 - it renders on Wayland now, can switch the renderer to a pure HTML one
 +
** This opens up opportunities (but depends on hosts that have GTK).
 +
 
 +
 
 +
<hr/>
 +
'''April 1, 2015''' - McQ, Alex, Martin, Dani (Regrets: John travelling)
 +
* Alex: '''GTK 3.16''' seeing issues again - fixed some crashes, but scrolling is still entirely broken
 +
** SWT uses a number of things that GTK declares as "implementation detail"
 +
* PMC approval on piggyback CQ's (AC question forwarded by John)
 +
** Dani sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02332.html our position] to John in order to update the AC
 +
 
 +
<hr/>
 +
'''March 18, 2015''' - Dani, Alex, Martin, McQ, John
 +
* John: '''EclipseCon''' - Bigger this year due to LocationTech (750 attendees)
 +
** Mark Reinhold keynote and "after-session" on Java 9
 +
** Much interest in Orion JS tooling / editor, also on desktop
 +
** Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
 +
* Dani: {{bug|458730}} '''Mars Plan Update'''
 +
* Dani: '''e4 project leadership''' approved by EMO
 +
* Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list
 +
 
 +
<hr/>
 +
 
 +
'''March 11, 2015 - no meeting (EclipseCon)'''
 +
 
 +
<hr/>
 +
 
 +
'''March 4, 2015''' - Dani, McQ, Martin, John
 +
* Dani: '''e4 leadership''' - Dani will volunteer to co-lead
 +
* Dani: '''BREEs''' - documentation about how to pick the EE
 +
** Recommending the "earliest generally supported JRE that provides the capabilities you need"
 +
** Would like an URL on the page pointing to the most recent plan (talking to Wayne)
 +
* John: '''greatfix contest'''
 +
** Dani: Working well - some very small contributions but some also very large (eg Customize Perspective fixes)
 +
* John: '''EclipseCon''' - numbers looking good; join Planning Council Breakfast as delegate for Dani
 +
 
 +
<hr/>
 +
'''February 25, 2015''' - Dani, Martin McQ
 +
* No topics
 +
 
 +
<hr/>
 +
'''February 18, 2015''' - Dani, Alex, Martin
 +
* Alex: '''Building Native Launchers'''
 +
** Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
 +
** Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
 +
** Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
 +
* Dani: Great initiative, but other (non-EF) builders must not be broken
 +
** EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
 +
* Alex is willing to spend time to get Linux builds running; but can't help with other architectures
 +
** Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
 +
* Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
 +
** Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
 +
** Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
 +
 
 +
* Alex: '''{{bug|459399}} - Policy for recommended minimum execution environments for bundles'''
 +
** Dani: It works today
 +
*** To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
 +
*** To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
 +
** Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
 +
*** But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
 +
*** Suggested BREE for new bundles has already been changed by Lars
 +
* Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
 +
* No conclusion so far (Alex and Dani disagree)
 +
 
 +
* Dani: '''e4 leadership'''
 +
** Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier
 +
 
 +
<hr/>
 +
'''February 11, 2015''' - Dani, Alex
 +
* no topics
 +
 
 +
<hr/>
 +
 
 +
'''February 4, 2015''' - Dani, Alex, Martin
 +
* Alex: With GTK-3.15.[345] , Eclipse is entirely unusable
 +
** Alex has some dirty workarounds to make it start, but still many issues like trees not painted, ...
 +
** Crash on startup identified to be GTK bug. Fix to be released in 3.15.6 https://git.gnome.org/browse/gtk+/commit/?id=edec64cda3d4518b4e87d5ea5d287d4570ba9933
 +
* Dani: Working on Solaris 64-bit
 +
 
 +
<hr/>
 +
 
 +
'''January 28, 2015''' - Dani, Alex, John
 +
* Dani: Switch Mac OS X 10.9 with 10.10 in Mars target environments
 +
** No objections
 +
* Alex: Looking for any Eclipse related activity @Fosdem
 +
<hr/>
 +
 
 +
'''January 21, 2015''' - Dani, Alex, Martin, McQ
 +
* Alex: '''Process for allowing non-committers extended bugzilla privileges (for bug triage)?'''
 +
** Dani: Yes a process exists. Send bugzilla username to Dani.
 +
* Alex: '''New resource for helping with SWT'''
 +
* Dani: '''Platform/UI co-lead'''
 +
* Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --&gt; IBM SWT Team considering to invest in getting patches in for 64-bit Solaris
 +
 
 +
<hr/>
 +
'''January 14, 2015''' - Dani, Alex, Martin, McQ, John
 +
* Dani: Update on Platform/UI Leadership: Daniel Rolka left IBM and for now has no time to contribute. He stepped down as co-lead and nominated Lars Vogel
 +
* Dani: Solaris x86 64-bit support - patches exist, but no machine available. No luck to get one from Oracle or via Eclipse Foundation. We will not support Solaris x86 64-bit unless someone makes a machine available
 +
<hr/>
 +
 
 +
'''January 7, 2015''' - Dani, Alex, Martin, McQ, John
 +
* Dani: '''Platform/UI Leadership'''
 +
* John: '''Git security issue''' - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP
 
<hr/>
 
<hr/>
  
 
= Archive =
 
= Archive =
 +
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 +
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]
 +
* [[Eclipse/PMC/Minutes 2012 | Archive of Meeting Minutes from 2012]]
 
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]

Latest revision as of 12:12, 16 August 2016

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

Aug 16, 2016 - Dani, Martin, Lars

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

Aug 09, 2016 - Dani

  • no one joined - had private conversation with McQ later
    • guys, please announce when you can't join. I can make better use of my time than waiting for you in the call ;-) - thanks.

Aug 02, 2016 - Dani, Martin, Alex

  • Dani: New Oxygen Plan Format
    • AI Dani ask Denis about aggregating the Sub Wiki's into the master page
  • Alex: SWT Fragments for ARM64 etc
    • Tycho doesn't support auto-selecting fragments - in contact with Jan and Tobias
    • Dani: Would like to revert changes - don't want to punish people who are not interested in fragments
    • Not really an SWT problem, so editing .target files would be a clean solution
    • Will probably go with empty (dummy) fragments without natives, as that's the simplest solution
  • Dani: SWT team - Lakshmi going to Sweden, will not be available until end 2016
    • Arun is mostly back, Sravan is now on Releng
    • Need to push further on building at the Foundation!!
    • Alex: Getting CentOS for building ... but test machines are on SLES11, which is too old, will need at least SLES12
      • Dani: Will need an owner at the Eclipse Foundation to ensure this proceeds ! Alex agreed to further drive this.
  • Target Env: Dropping REL6 -- reference platform for testing will only be REL7 (though will continue to run on REL6)
    • Reducing support level this year, in order to prepare for only supporting GTK3 next year

July 26, 2016 - no meeting

July 19, 2016 - no meeting


July 12, 2016 - McQ, Lars, Alex

  • Dani: Hackathon summary

July 5, 2016 - Lars, McQ, Alex, Dani, Martin

  • Lars: SWT move to Java 8
  • Alex: Initial builds of GTK 2.24 for AIX - planning to bump minimum GTK version to 2.24
    • Will remove non-cairo drawing, this is where most of the breakage happens
    • Ubuntu 12.04: 2.24.10 / 3.4.5
    • 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: Build, and Hackathon

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?

June 21, 2016 -


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

  • no topics

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

May 24, 2016 - Dani, Lars, Martin

  • 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

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

May 10, 2016 - Dani, Martin, Alex, McQ

  • Dani: Policy for what should go into Neon.Update Releases
    • Would like to be more flexible than in the past - discussion point for next week
  • Martin: RHEL7 -- GTK3 versus --launcher.GTK_Version 2
    • GTK2 rendering still much more reliable than GTK 3 - forced to release commercial software with the GTK2 fallback for now
      • Drawback: Even with MATE desktop using GTK2 (for accessibility), the Browser widget webkitgtk2 is not easy to get since not in the official repos
    • Alex: Desktops are moving faster - adopting change very quickly - cannot keep up with the investment that the Community currently makes in SWT
      • Heavily limiting what we support looks like the only viable approach at the moment...
      • There's 2 big groups of bugs: (a) "Next" version of GTK, and (b) "Old" version like Ubuntu 13.04 which has 3.10 - can we limit support to "latest" ?
      • Martin: Need "LTS" Linux (RHEL 7, RHEL 6, Ubuntu 12, 14 - soon 16).
    • Alex: Gnome people have come up with a "Container environment" for GTK - could ship Eclipse that way ?
      • Limitations: Updates must come through this application - already using Gimp from such an environment
      • Might be able to deliver Eclipse that way next year (Oxygen)

May 3, 2016 - Dani, Martin, Alex, McQ

  • Brian's request on the PMC list
    • McQ: Why would we care about adding small enhancements in RC1 when we should focus on testing and critical fixes
    • Dani: Two parts in the change - the original one (approvable), but another change also sneaked in (enable the prefix search) - not approvable
    • Alex: People don't want to wait for getting in an improvement...
    • McQ: OK for adding as feature to Neon.1 , but Neon.0 should be focused on bug fixes
    • Keep in Gerrit for now - Neon.1 stream is typically opened when no new changes are expected. Rebasing is relatively easy from Gerrit.
    • ACTION McQ to -1 and argue why.
  • Alex: Update on Accessibility
    • 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 !

April 26, 2016 - Dani, Lars, Alex, Martin, McQ

  • Mickael's API change request ... tried to address feedback from Markus but then got no additional feedback
  • Alex: Accessibility - broken on recent GNOME and probably others
    • Accessibility is important. Have reports from users who say "Eclipse works for them"
    • McQ: Need to keep some focus and look at what we can do for Neon.1
  • Alex: Platform.ui generification of project
    • Dani: Won't get a consistent story when done piecemeal - needs to be done "per framework" and not necessarily "per plugin"
    • McQ: It's a huge effort - enough by itself for one whole release !
    • Dani: If a meaningful separate unit is found that can be done, but things like e.g. LabelProvider, ContentProvider and TreeViewer can't be done isolated
    • Lars: If a smaller unit of generification work is possible, that's permitted when somebody signs up for the work and it has been discussed in the public
    • ACTION Alex to prepare a message for review and then send that.
  • Lars: Copyright discussion
    • Not having the end date in the copyright notice makes the copyright invalid.
    • The IP Advisory Board will discuss it again.
  • Dani: Update on FEEP
    • Paul not reached out yet
    • A list now shows what's done or in progress - but no time
  • Dani: Update on M7
    • Last 4 builds failed due to infrastructure issues - Maven stuff could not be accessed
    • Will try to enable cache on the build side and re-try until the cache is full


April 19, 2016 - McQ, Dani, Martin, Alex (regrets: Lars)

  • 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


April 12, 2016 - McQ, Dani, Martin, Lars, Alex

  • Lars: Get rid of the Copyright Year Update Requirement
    • bug 485257_c13 EMO: All information is in the git repos
    • McQ: OK lifting the requirement but doesn't want wrong information in files .. get rid of all copyright years ?
    • Dani: Replacing the end-date by "[see git]" might be an option
    • ACTION McQ or Dani talk to IBM Legal, then decide next week
  • Lars: bug 490012 Remove Project Settings to force strictly compatible JRE
    • Example: When don't have admin rights on a customer machine, can't install anything
    • Dani: With the Gerrit Build Validation, the risk of getting unbuildable code is no longer there
    • Proposal: Project requests a particular JRE, but the workspace configures treating this as an error or warning
    • 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
    • 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.

April 5, 2016 - McQ, Dani, Alex, Martin, Lars

  • Dani: FEEP Update
    • Foundation pays Patrik Suzzi as a contractor to look at Platform bugs (triage, and fix)
    • Will focus on critical / blocker bugs initially, or bugs already tagged by committers for 4.6 M7 and 4.6
    • Mickael Barbero still quite involved in Releng - Foundation looking for Releng replacement so Mickael can develop (already reviewed autosave - but might be on vacation at the moment)
  • Dani: Solaris 32-bit
    • Will provide Solaris 64-bit binaries, but stop building Solaris 32-bit with Neon
    • Open question: what does this mean in terms of GTK versions ? (GTK3 would be nice)
      • Alex may start asking questions as soon as the binary fragments are in the repo
    • McQ: Windows 32-bit is still active - future change probably tied to
  • Dani: New Solstice Welcome
    • Some issues with Logo, sometimes it's there sometimes not; Brian working on it, Solstice will become the new default in M7
    • Currently, ONE product logo must work on all Themes - bad design - probably to be changed
    • McQ: Do we mirror the welcome for BIDI ? (Dani thinks yes, saw bugs come along)
  • Alex: FEEP Process Discussion (around Themed Scrollbars)
    • "Scrollbar Theming": Contractor doing work without SWT committers knowing, and disregarding suggestions from the committers
      • Looks like the proper fix from committers was not even tried ?
      • It's OK putting adding a layer if it solves a problem ... but if the proper solution is suggested, it should at least be tried.
      • McQ: Accessibility - with 10000 items it's getting slow - should try the native way
    • Lars: Transparency? - No insight on what FEEP's are actually ongoing
      • AI Dani send note to Wayne and Mike asking for location of FEEP Project List
      • AI Martin compare against AC's requested list, and put on agenda for the next AC call
    • Lars: Styling is actually an important business driver!
    • Alex: FEEP feels like "quick and dirty" is favored at the moment over sustainable solutions !
      • McQ: Perhaps a problem with the funding model ?
      • Dani: Lack of people who want to fix issues on the list of the AC ?
      • McQ: FEEP is still early - time to provide feedback now. Goal Transparency on what's done, and why design decisions are taken.
      • McQ: Who cares for StyledText - have Markus have a conversation with the submitter ?
        • Lars: We have no API for styling scrollbars (background, foreground) - Alex: THIS is what the FEEP should have adressed !
    • Martin: Next step should be conversation with EMO about toplevel transparency, and basic guidelines ("sustainable solution over quick fix").
    • Alex: Need something like JEP (Java Enhancement Process) for FEEP.
      • McQ: Agree this is what we want, but would it discourage submitters ? The lighter-weight the process the better...
    • Alex: If anyone stepped in and did that work it's fine ... but such work sponsored via FEEP seems putting resources in a wrong direction.
  • Lars Question: Google work on improved Type Hierarchy
    • Main work is a new Index, Type hierarchy will be the first client, planned past Neon (contributor: Stefan Xenos).

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"

March 22, 2016 - McQ, Dani, Alex, Martin

  • 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 ?

March 15, 2016 - McQ, Dani, Alex, Martin

  • Dani: Platform/UI got awarded as the Most Open Project :)
  • Dani: Mention PDE/Build as in maintenance? - discuss next week when Lars is back
  • McQ: Merge Subproject Committers Groups? - Membership based on expertise is important
  • Dani: Test Failures due to hidpi work - not entirely done yet but looking good for M7
  • Dani: Lots of failures due to "Widget Disposed" failures
    • Gerrit tests didn't fail, probably sine the event timing on VNC is a little bit different than running manually
    • Alex: VNC/Gerrit tests run on GTK2 whereas all the rest defaults to GTK3 now
    • Looking for a machine with GTK3 to enable them -- working with Mikael Barbero to get this for David
  • VS Code Open Sourced - plugin model is very similar to Orion
    • Excellent with TypeScript, not quite as good as Orion for JavaScript
    • Ideally, would love to see some unification of web-based IDEs (like Che already using Orion editor)

March 8, 2016 - No call


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

February 23, 2016 - McQ, Martin, Dani, Alex

  • Dani: Mars.2 is on track
  • 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).

February 16, 2016 - Alex, Dani, Martin

  • no topics

February 9, 2016 - Alex, McQ, Dani

  • Dani: looking good for Mars.2 (4.5.2) - no RC4 planned
  • Dani: please take a look at bug 466370 Welcome Screen redesign
  • Dani: please take a look at bug 472614 Smart Project Importer

February 2, 2016 - Dani, Alex, Martin, McQ

  • Dani: Foundation Hires - Dani hopes they'll find someone in Europe to deal with Releng issues
  • Dani: Neon M5 went smoothly - M6 will be the API freeze; tomorrow is the last planned RC for Mars.2
  • Dani: CQ Deadline on Feb.12 for Neon
  • Dani: bug 486647 for changing the strategy when opening files not associated with Eclipse
    • With M5, can now use the System Editor (default) or Text Editor - there's a request to always use the text editor
    • Dani thinks that for JPG one wants to use the OS
      • Martin agrees, OpenWith and choosing an editor remembers the choice, and one can also remember;
      • We also show the System Icon in Project Explorer, so using the System Editor by default is natural
      • Alex set it to "ask via popup" - can be quite noisy, but avoids trouble when KDevelop or something associated itself with Makefiles or so
    • Agreement that flexibility is fine - see no case for changing the default

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

January 19, 2016 - Dani, Alex, Martin

  • Upstaffing PMC - meet next week
  • Update Eclipse PMC representation on the AC
    • Since only Alex will represent the Eclipse PMC at EclipseCon, should push for not making formal decisions unless there is remote attendance support
  • Dani: bug 485429 PDE Build - looks like a lot of people still use it; OK if moving to a different component, but there's still a dependency:
    • Plugin or feature export still needs PDE Build -- Whoever wants to remove it, will need to implement a replacement in the Platform
    • Alex: Platform build currently does double bootstrapping Tycho already ... making this more complex would be a problem
    • Introducing other build system into the Platform would be a wrong approach
    • Will go ahead with what we have for 4.6
  • Alex: As of today's GTK3 build, Eclipse is working fine on Wayland :) thanks to a number of fixes in GTK
    • Some GTK developers are now considering Eclipse as part of their regression suite :)
  • SWT move to Java 7 was much appreciated; moving forward, how to deal with functional interfaces ?
  • Alex would be interested in some styling support in SWT - would simplify some things, at least on GTK
    • Could be a very simple API like setStyle(String) - win32 also seems to have some styling support
  • Martin: Stability of GTK3 on Mars.2 ?
    • Alex: Many distros do their own hacks, so hard to tell... Mars.2 should be stable on every distro that has a stable GTK3 distro without too many patches
    • Can't recommend GTK3 on Ubuntu yet; few things improved lately, but still causes troubles whenever Ubuntu updates their GTK, requires more fixes in SWT; Kubunutu and derivatives might be even worse
      • Good news is that GTK3.16 dropped support for custom theming engines - causes some ugliness but at least it's stable
    • Debian or SuSE should be OK;
    • Expect Neon GTK3 to be more stable everywhere than GTK2

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

January 5, 2016 - McQ, Dani

  • Dani: PMC Membership

December 15, 2015 - McQ, Dani, Martin, Alex

  • No calls until Jan.5
  • Looking for a new PMC member

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

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

November 25, 2015 - McQ, Martin, Alex

  • Alex: Bumping SWT to Java8
    • Lars wants to use Lambdas bug 481195; Markus keller wants static helper methods;
    • Stephan Herrmann - University Research for Thread safety through typed annotations
      • Are they ready to contribute? - Probably yes, needs to be clarified; having better dev support for Thread Safety will be a huge help
      • 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
      • John: Lambda support doesn't necessarily require SWT to be Java 8 itself (it could just be more lambda friendly)
        • Won't help with base listeners, but probably with mouse events and related .. follow up in the bugreport
        • Labdas are more than syntactic sugar, it's more efficient ... still there is more value in Thread safety annotations
      • 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
  • 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)

November 18, 2015 - Alex, John, Dani


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

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

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

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

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 ? --> Might mean that external tools don't work as expected
    • Proposal 2: Make users aware (Restore Oomph Welcome, which was disabled via bug 459486) ? --> 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) ? --> But on "push" it may be too late
    • Martin: Encoding describes content, so should be managed with the content (as a project setting)
      • --> 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 --> 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 ?

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

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?
      • Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
        • Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
        • For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
        • Plugins who don't care recompiling may have to live with ClassNotFoundException
        • Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
      • Summary: Handle the Major with care -- in most cases, the cost of updating the major is not justified by the benefit.
    • 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 ?
      • Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
    • John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
      • 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)
      • Committers still need to be able to delete stuff when they find it necessary.
      • Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
  • Alex: Bumping the minimum GTK version again (may cause issues on Platforms like AIX -- to be discussed when it's time)



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
    • --> will have more discussion next week

September 9, 2015 - Dani, Alex, Martin, John, McQ

  • John: Planning Council Updates
    • 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
    • Mid December rather than end to avoid churn, so this one is a little shorter
    • Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
    • McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
  • Software is getting more important - would be good to better support multicore
  • John: IntelliJ change in licensing / sales model
    • Many eclipse-positive comments on the announcement blog
    • Possibility putting Money on Eclipse Development may become interesting for companies in this context

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
    • Do we want to stick to the "Service" model or allow feature updates ?
    • Mars.1 winding down -- sticking to "Critical Fixes Only" for that
    • Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
    • Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
      • Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
      • Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed

August 26, 2015 -

  • Dani/Alex/Martin can't join (traveling)

August 19, 2015 - Alex, Dani

  • nothing to discuss

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

August 5, 2015 - McQ, John, Dani, Alex, Martin

  • PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
    • adding another release before Christmas might be a next step - even if Platform contributes identical bits
  • Dani: Eclipse/Mars Retrospective
    • 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)
    • The Project has to agree
    • Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
    • Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
    • Dani to sent request for voting
  • 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
  • Martin: libwebkitgtk-3 on Ubuntu 14 forcing GTK 2 not working ?
    • 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
    • Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month



July 15, 22 and 29, 2015 -- no meeting


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

July 1, 2015 -- no meeting


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)

June 17, 2015 - Dani, John, Martin, Alex


June 10, 2015 - Dani, Alex, Martin

  • Dani: 4.5RC4 looking good, no more fixes planned
  • Dani: Working on Java 9 feature patch
  • Alex: PC discussing a change in the release train
    • Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
    • From Platform point of view, stability is key. Some key contributors not interested doing
    • Martin: How to also cater to contributors who want their contributions released soon ?
      • Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
      • Or, open up a new "experimental" stream ?
      • Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
  • Martin: Tested eclipse-installer (Oomph), looking really really good now

June 3, 2015 - Alex, Dani, Martin, McQ, John

  • Dani: Mars Endgame
  • Dani: Please vote for release review

May 20, 2015 - Dani, Alex, Martin, McQ

  • Dani: Security Update - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
  • Dani: RC2 Build - too many bugs assigned, Lars on Vacation, Dani will fill in
  • McQ: Too Many Platforms Built? - Who's really hurt by "too many builds" ?
    • Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).

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

May 6, 2015 - McQ, Dani, Martin, John

  • Dani: Java 9 timing - slight delay
  • Dani: RC1 preps
    • 2-day test pass went fine - 2 severe issues found, will be addressed
    • Request to watch PMC mailing list for API exceptions and defect approvals
  • John: PC Discussion on Release Cycles
    • Multiple releases per year PLUS maintenance streams seems like overkill
    • Consider an approach like Orion that just moves constantly forward
    • Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
      • A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
      • Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
      • Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?


April 15, 2015 - Dani, John, McQ, Alex, Martin

  • Dani: Java 1.7 Changes
    • Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
    • Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
      • Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
      • Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
    • Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
  • Dani: Batik 1.6 update

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



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)

March 18, 2015 - Dani, Alex, Martin, McQ, John

  • John: EclipseCon - Bigger this year due to LocationTech (750 attendees)
    • Mark Reinhold keynote and "after-session" on Java 9
    • Much interest in Orion JS tooling / editor, also on desktop
    • Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
  • Dani: bug 458730 Mars Plan Update
  • Dani: e4 project leadership approved by EMO
  • Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list

March 11, 2015 - no meeting (EclipseCon)


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

February 25, 2015 - Dani, Martin McQ

  • No topics

February 18, 2015 - Dani, Alex, Martin

  • Alex: Building Native Launchers
    • Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
    • Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
    • Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
  • Dani: Great initiative, but other (non-EF) builders must not be broken
    • EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
  • Alex is willing to spend time to get Linux builds running; but can't help with other architectures
    • Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
  • Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
    • Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
    • Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
  • Alex: bug 459399 - Policy for recommended minimum execution environments for bundles
    • Dani: It works today
      • To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
      • To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
    • Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
      • But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
      • Suggested BREE for new bundles has already been changed by Lars
  • Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
  • No conclusion so far (Alex and Dani disagree)
  • Dani: e4 leadership
    • Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier

February 11, 2015 - Dani, Alex

  • no topics

February 4, 2015 - Dani, Alex, Martin


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

January 21, 2015 - Dani, Alex, Martin, McQ

  • Alex: Process for allowing non-committers extended bugzilla privileges (for bug triage)?
    • Dani: Yes a process exists. Send bugzilla username to Dani.
  • Alex: New resource for helping with SWT
  • Dani: Platform/UI co-lead
  • Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --> IBM SWT Team considering to invest in getting patches in for 64-bit Solaris

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

January 7, 2015 - Dani, Alex, Martin, McQ, John

  • Dani: Platform/UI Leadership
  • John: Git security issue - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP

Archive