Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

(June 12 meeting notes)
(129 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
= Documents =
 
= Documents =
 
 
Some documents written and/or used by the PMC:
 
Some documents written and/or used by the PMC:
  
Line 12: Line 11:
 
= Meeting Minutes =
 
= Meeting Minutes =
  
'''Feb 8, 2017''' - Dani, Alex, Martin, Lars
+
'''June 12, 2018''' - McQ, Alex, Tom, Lars
* Dani: '''{{bug|509412}}''' - Adopt newer JSch for Platform 4.6.3
+
* RC4a looks good; hidpi fix is in place
** Alex is fully consumed with Webkit work for Oxygen
+
** no plans for further builds at this point
** Need to move target platform to the latest Orbit in order to pick up the new JSch; that might cause other changes, since Orbit retention policy keeps only one version
+
** Dani: Cherry-pick the new JSch recipe to the Orbit Maintenance Branch ?
+
** Martin: Looks like in the past, new Orbit R-Builds were made for Maintenance ... but with the move of Orbit to git, it is unclear how branch builds for Neon.x would be made
+
* Dani: '''Update on RT PMC (Equinox) coming to Platform'''
+
** Tom Watson is in favor, reached out to Wayne for process
+
** Potentially move entire IP log, but IP team is currently busy with CQs for Oxygen
+
* Dani: '''Finally Unblocked on Java Language Server'''
+
** Microsoft signed the committer agreement
+
* Dani: '''Scenarios for UI Testing'''
+
** Initial Scenario from the PMC Notes can already be used; once that works, could extend to more
+
* Dani: '''Sign Up for Security Rep'''
+
** See [https://dev.eclipse.org/mhonarc/lists/tools-pmc/msg03927.html Wayne's message to PMCs] requesting PMC attendance
+
** John Arthorne used to be the Security Rep;
+
** Tasks: Follow the security mailing list; currently low volume but might get higher with IoT getting up speed
+
** '''RESOLUTION: Alex agrees to sign up''' since already following security issues
+
* Dani+Alex: '''libswt-gtk3 natives for PPC'''
+
** Alex: Trying to limit the list of supported GTK versions to maximum 2; now at the latest GTK2 version
+
** Currently, only Intel builds do both GTK2 and GTK3; PowerPC only does GTK2; the current hardware is unable to install REL7
+
** Would prefer building at the Foundation over using custom company hardware; cost of hardware is around 50K
+
** Primary Platforms should be built at the Foundation, secondary builds can be contributed ... should Linux-PPC be considered primary ?
+
** Alex could easily provide a Fedora Platform, but it would be much newer than anything else that's around; ARM32 and ARM64 builds are already provided by Fedora
+
** If somebody (IBM) needs an older version like CentOS, it would need to be provided by such adopters
+
** '''AI Dani+McQ''' find out on priority of Linux-PPC (32bit, 64bit)
+
* Alex: '''Update on Reddeer Testing Framework'''
+
** A new version is being written, that no longer uses SWTBot underneath; there's a plan making this an Eclipse project
+
** Engineers claim that after the rewrite it's a lot more stable recognizing widgets than on top of SWTBot
+
** Martin has been looking at [http://eclipsesource.com/blogs/tutorials/rcp-testing-tool-rcptt-basic-tutorial/ RCPTT] which looks promising initially (easy to record tests) but unclear how stable such tests would be.
+
** (call had to be closed at this point)
+
 
+
<strike>Feb 1, 2017 - cancelled</strike>
+
 
+
'''Jan 24, 2017''' - Dani, Lars, Martin, Alex
+
* Dani: '''New Jetty Version''' - Alex will look at it after FOSDEM (Feb 7)
+
* Dani: '''javax.xml''' - Plan to announce removal from the feature on cross-project for M6
+
** Cannot remove from the compile prerequisites, because plugins still on Java 5 need it
+
* Alex: '''[http://jboss-reddeer.github.io/reddeer/ Reddeer Testing Framework]'''
+
** JBoss Tools uses Reddeer for overall user story validation
+
** Lars: Why wasn't the framework added to SWTBot? -
+
*** Reddeer is not a framework, it's meant as a test harness library - smaller scope than SWTBot or Jubula
+
*** API Stability across multiple Eclipse versions is out of scope, thus created outside Eclipse for now
+
** Martin: Any improvements in object recognition compared to plain SWTBot?
+
*** Reddeer tries to make use of the best mechanisms from SWTBot for object recognition (Finder, or callbots). That saves users from making newbie mistakes in SWTBot, but apart from that it's no better
+
*** No solution for external (non-Eclipse) dialogs ... that's not doable in SWT
+
** Lars: EclipseSource people have been talking about [http://eclipsesource.com/blogs/tutorials/rcp-testing-tool-rcptt-basic-tutorial/ RCPTT], it might be able to deal with native tooltips etc
+
** Dani and Lars think Jubula is too heaviweight; might work for Integration Builds, but not for individual developer's builds. Local setup must be really easy. Also, setup looks non-trivial, needs resources to work on ... and, doesn't seem to add much benefit over SWTBot (assuming that Jubula agent doesn't hook into native libs like win32, Cocoa or GTK).
+
*** Alex: Especially integration in Maven may be hard.
+
** Alex: Main limitation is that we don't have resources to actually create tests. Suggest reaching out for help asking people who would actually create tests ... then use whatever framework that people would like to use.
+
** Dani and Lars won't be able to come up with a workflow scenario before end of next week --&gt; Alex will come up with an idea since he has meetings on Monday.
+
*** Dani: Launch Eclipse, choose a workspace, open the package explorer, create a Java project (helloworld). Expand later, maybe into quick assist.
+
*** '''AI Alex''' to demo Reddeer in 2 weeks
+
*** '''AI Martin''' to try installing Jubula until next week
+
*** '''AI Martin''' ping Sergey re: asking for help on Platform/Resources.
+
 
+
<hr>
+
'''Jan 17, 2017''' - Dani, Sergey, Alex, Lars, Martin, McQ
+
* Sergey: '''Merging platform.resources with platform.ui'''
+
** Seems that more contributions to platform.resources are made by platform.ui committers, than others. Only 2 platform.resources committers seem active (and those two are actually platform.ui committers as well)
+
*** Opening up to Platform UI would encourage more people to actually contribute to resources. Strive for shared access on components that are interrelated
+
** Dani: Merging into platform.ui would mean making Dani and Lars the leaders for signoff - that causes too much burden
+
** Sergey: Platform/Team has actually more synergy with Platform/UI than resources
+
** Alex: For gcc for example, there is a notion of "maintainers" per git repo for signoffs - that's independent of leadership or commit rights
+
*** McQ: Not sure how adding another role would simplify things ?
+
** Sergey: The problem for signoffs is not is much the volume of commits, but the volume of failing tests
+
** Alex: The manpower of Platform Resources is so low by now that even {{bug|509412}} was not being filed ... existing committers do not really seem to "own" the project any more, this is an indication for merging
+
** Martin: Can't see how merging into a bigger entity would resolve the "ownership" problem. Perhaps make interested contributors Platform/Resources committers instead, and see how to resolve the ownership issue on the smaller scope ?
+
** McQ: Propose applying the recent simplification of gaining commit rights (for "known" committers)
+
* Lars: '''Removing javax.xml'''
+
** Was introduced only for very old JRE's , it is part of the JRE now
+
** Martin: Might cause a uses constraint issue since not exporting the package with version any more, see http://njbartlett.name/2011/09/02/uses-constraints.html
+
** Lars: With javax.annotation, that was solved with smart reexporting
+
** McQ: OK with removal when we can confirm we're not breaking things
+
** Dani: Whoever requested removal should double-check whether the API is the same.
+
**'''AI Lars''' send a note to Tom Watson as the submitter.
+
* Dani: '''Project Updates'''
+
** Deadlines upcoming for CQs and APIs - see Endgame Plan, please provide feedback
+
* McQ: '''UI Testing and Jubula'''
+
 
+
<hr/>
+
'''Jan 10, 2017''' - Dani, Lars, Martin, Alex, Sergey, McQ - Special Guest: Alex Schladebeck
+
* Dani: '''Platform Bits on Maven Central''' - Now available thanks to Stephan Herrmann
+
* Dani: '''Board Committer Rep Elections''' opening
+
* Dani: After David Williams' move, Wayne is looking for a Planning Council Chair; Fred Gurr has taken over Simrel Releng
+
* Dani: objenesis (Mockito / Easymock dependency) and Java9 - will wait for how upstream is planning to address issues
+
* Lars: '''Equinox move to Platform''' - no updates - '''AI Dani''' talk to Tom again
+
* McQ / AlexS: '''Jubula'''
+
** In the past, with lots of full-time Platform committers, sniff tests just happened automatically giving great confidence. Now, with more part-time work happening, there is more need for end-to-end workflow test automation to give quality confidence
+
** Martin: On top of low-level JUnit tests, want at least very few highlevel end-to-end test to avoid "Eclipse looking silly". Need UI tests that are really stable (avoid random failures)
+
** Dani: On EGit SWTBot tests, too many libraries to install, how to run on Gerrit HIPP slaves
+
** AlexS: Original Jubula goal was to allow non-programmers write tests. Beginning 2015, the client API (for controlling the SUT) was separated from the front-end, was separated from the ITE. This allows writing UI tests programmatically, and avoids the need for a database.
+
*** For identifying components/actions to write tests, officially an object mapping needs to be done in the front-end (ITE, integrated test environment). But there may be a shortcut available for getting object IDs
+
*** Compared to SWTBot, Jubula is 90% blackbox (code highlevel actions rather than things like calling setText())
+
*** UI Tests typically take longer than unittests by definition (due to setup, teardown, ...), so might not be applicable for Gerrit triggers
+
*** Dani: Would like to run a first test on CentOS first, as part of the integration tests
+
*** Lars: Robustness of the tests? - SWT on Mac is problematic, but Linux and Windows should be OK.
+
*** Martin: Dependencies? - Around 5MB Libs, plus the agent needs to be installed (around 100MB). Once that is there, tests are stand-alone on a laptop. There might also be an "embedded agent" but not sure ('''AI AlexS to check''')
+
*** Getting a first test up and running ? - Maybe around 1 week, depends on what to do ?
+
**** Lars: Would like something for quick access. Martin would something for "fresh download" (fresh config area + workspace) maybe combined with quick access.
+
*** '''AI AlexS''' send slides
+
*** '''AI Dani + Lars''' propose scenarios. Check possible owners of the initiative on Platform/UI side
+
*** '''AI AlexS''' check possible PlatformUI Contributors from Jubula team to get started
+
 
+
== 2016 Minutes ==
+
 
+
'''Dec 20, 2016''' - Dani, Lars, Alex, Martin, Sergey
+
* Dani: '''{{bug|499768}} Oxygen Plan Update''' - Ubuntu 14.04 removed as a reference platform. CQ deadline added.
+
* Dani: '''SWTBot Status'''
+
** Worked well until Eclipse.org HIPPs were updated - now, with icewm there are focus issues, causing random recognition errors. There is {{bug|506995}} open to provide a better alternative.
+
** CDT has been affected as per {{bug|509248}} - Dani also in contact with egit
+
** Until then, we have to wait to look into SWTBot
+
* Sergey: '''Neon.2''' - GA tomorrow, branch is open already
+
* Alex: '''Webkit 2 Update''' - Javascript integration is working; plugins running out-of-process is a huge benefit
+
** BrowserFunctions not working yet (callbacks like "onClick" in Browser Widgets) - OK to still make Webkit2 the default ?
+
** Should test Javadoc hovers; Help system navigation to Javadoc; Intro pages; expect to be done by M6, probably even M5
+
** Martin doesn't want to block downstream adopters; enable fallback by environment variable and announce on cross-project
+
** Alex will look at enabling at least onClick(), that's perhaps the 80% case, and do some more testing before switching
+
* Dani: '''Eclipse.org Infrastructure Updates'''
+
** {{bug|499399}} being discussed on the board level now; especially VNC on the HIPPs, and {{bug|508658}} repo.eclipse.org
+
** VNC may be non-trivial to get fixed since SLES is almost entirely targeting back-end services
+
** Would need a reasonably recent UI stack - anything like CentOS, Fedora, Mandriva
+
** '''Goal would be having the test "close to what end users use"'''
+
** Enterprise users tend to use "older" distributions (CentOS, Ubuntu LTS)
+
*** Statistics like https://www.linuxcounter.net/statistics/distributions might be misleading since enterprise users typically don't count there
+
*** On the other hand, enterprise customers typically also don't use the very latest Eclipse; and have their own support channels to report issues. So for active development, newer distros may be desirable.
+
* Will cancel the Dec.27 and Jan.3 PMC calls
+
 
+
<hr/>
+
'''Dec 13, 2016''' - McQ, Lars, Alex, Martin, Dani, Sergey
+
* McQ: '''Rebuild for M4''' due to 3 bugs, e.g. {{bug|508717}} - Could testing be improved ?
+
** Probably no 1:1 relation, but need a modern story for getting confidence in what we provide to the Community. A massive 7-hours API testing as done today doesn't hurt but isn't the solution
+
*** Lars: Test Suite is currently inactive for Quick Access - activation is on the roadmap
+
*** Would like some end-to-end scenario testing from the UI
+
** Platform UI would like to start using SWTbot - most lightweight - at least some initial tests as examples
+
*** '''AI Dani''' talk to Mickael to understand what was blocking from adding it
+
** UI tests are good for stable things, problematic for work-in-progress UIs
+
** GUIdancer / Jubula looked very impressive - but seems to require a database, so hard to run locally
+
** Martin: Reach out to projects on top of the Platform and ask them run on an I-build, at least occasionally?
+
*** Sergey thinks that we need to run tests ourselves.
+
*** Alex: Linuxtools could easily run tests against I-Builds; Heavy usage of SWTbot in place but it's unreliable - tests are very fragile, even smallest changes break the tests easily, tests were rewritten very often, making this quite expensive
+
*** Would only verify SuSE 12 if running on HIPP, but that doesn't tell much about other Platforms
+
** McQ would like a "sanity-level check" on commits, to get some level of confidence on the builds ... a quick test which actually checks how people are using Eclipse today
+
** Alex thinks that the current test suites are not in a good shape: many tests fail when run locally, even though good on Foundation hardware - cleaning this up is a lot of effort
+
** McQ: Interested in the "top 10 ways of working with Eclipse" - could we test the top 10 scenarios ? Can we even find them ... and make those small "top 10" set stable so it can run anywhere ?
+
* Lars: '''Push Maven Artifacts to Central'''
+
** What should be the group ID ?
+
*** Dani thinks we cannot use org.eclipse (too generic) - maybe o.e.platform / o.e.jdt / o.e.pde (Q: Also split out o.e.swt / o.e.ui ?)
+
*** Martin wouldn't split out o.e.ui -- would prefer more grouped together in Platform
+
*** '''AGREEMENT''' to group by project name: o.e.platform / o.e.jdt / o.e.pde
+
** Maven has only 3-part-versions : what to do with the qualifier ?
+
*** Alex: Sometime we don't bump the version for Beta releases - cannot override
+
**** Dani: releasing with a new qualifier but without a new version is a bug and should be found by reports and fixed
+
*** Dani: Using n.n.n-BUILDID is perhaps an issue since it's not treated as a release any more (but a snapshot)
+
*** '''AGREEMENT''' to use 3-part versions.
+
*** '''AGREEMENT''' to Stefan's proposal only releasing Neon.2 for now.
+
*** '''AI Dani''' respond to Stefan.
+
 
+
<hr/>
+
'''Dec 6, 2016''' - Dani, Alex, Martin
+
* McQ talked to Tom Watson about Equinox moving to Platform - Tom wants to discuss with the RT PMC
+
* Alex: '''Update on Wayland'''
+
** Fedora 25 shipping with Wayland by default
+
** Wayland back-end for SWT is a patch in progress, some events not delivered, others incorrectly
+
** Hoping to be in good shape by M5.
+
** Until then, Gnome can be started on X11 with additional packages installed.
+
** If Wayland is needed, the XWayland compatibility layer does work although slow (some drawing can be seen)
+
** Some rewrite in the Launcher will be needed due to the security model - each window is isolated
+
* Dani: '''How we test milestones''' - people putting in features sometimes don't seem to participate in the milestone week
+
** McQ: Agrees that a good deal of manual testing is needed to cover flows that developers actually use
+
** Alex: If milestone week overlaps with other duties (outside Platform) those other duties often take precedence
+
** Test automation doesn't help for new features that add UI
+
** Sergey distributes I-Builds so regressions are often found early - but there's no firm data on quality. Alex also distributes / uses I-Builds.
+
** McQ thinks that some confidence in quality is needed, before I-builds are given out
+
** Dani: Dogfooding helps a lot more than test plans.
+
** ''To be discussed next week when there are more people on the call''
+
* 4.6.2 looking good; M4 test pass today for releasing on Friday
+
* Oxygen plan hasn't seen comments, so will only put Java 9 updates in there
+
 
+
<hr/>
+
'''Nov 29, 2016''' - Dani, McQ, Sergey, Alex, Lars, Martin
+
* Sergey: '''[http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg10305.html Understaffed Projects Announcement]''' - should it be sent to a wider audience?
+
** Was sent to eclipse-dev with cc: eclipse-pmc, see http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg10305.html
+
** Dani suggest checking the mailing list archives or via RSS eg [https://dev.eclipse.org/mailman/listinfo/eclipse-dev eclipse-dev mailing list home]
+
** '''AI Dani''': send Sergey some links
+
* Martin: Is it clear enough what contributors could do if they feel not being heard?
+
** There is a forum and developer mailing lists, so for the Eclipse project we are probably good
+
** Dani: The README.txt on top of the repo looks like a very good place for such kind of information
+
** '''AI Martin''' review a couple READMEs and then make suggestions on the eclipse-pmc mailing list
+
* Dani: RC4 - no build currently planned will push RC3. There's also Oxygen M4 next week.
+
** Need to move out some planned bugzilla's targeted M4 (platform.ui: Lars to help, core: Sergey)
+
** JDT UI is tight since Noopur is on vacation and Markus is very busy with Java 9 and HiDPI work
+
* New process in place for the IP Log, IP log for Neon Update 2 (4.6.2) got approved today; Review is scheduled and ends on Dec.21
+
* JDT Language Server: Still some blockers on the IP Work (hackathon contributions)
+
* '''AI All''' Plan Update for Oxygen M4 {{bug|499768}}; Dani will update the Java 9 info
+
* Lars: '''Approvals for Equinox'''
+
** RT PMC don't have meetings or a process in place for approvals
+
** They think that the Eclipse PMC is in a better position to approve Equinox
+
** But why is Equinox on the RT PMC after all, does that still make sense? After all builds are done by Eclipse.
+
** '''AI Dani''' discuss with Tom
+
 
+
<hr/>
+
'''Nov 22, 2016''' - Dani, Martin, Sergey, Alex, McQ (Regrets: Lars - travelling)
+
* McQ: Simplify adding committers to understaffed projects
+
** '''AI Sergey''' final Polish on Lars' proposal + suggestions as discussed
+
* Martin: {{bug|498116}} download servers are hosed every Tuesday
+
** PMC agrees to trying a fix for Neon.2 - this kind of issues is important (Android also ran into this kind of issue 2 years ago)
+
** Dani: we can encourage them to fix it, but EPP and Equinox are not governed by our PMC
+
* Dani: '''Neon.3 Planning'''
+
* Dani: '''FEEP Discussions''' on the [https://dev.eclipse.org/mailman/listinfo/eclipse.org-feep-stakeholders eclipse.org-feep-stakeholders] mailing list
+
** Voting will be more open this time
+
* Dani: '''IP Log for Neon.2''' - Endgame looking good, no planned fixes known at this time, but if there's a fix for {{bug|498116}}, we will consume it
+
 
+
<hr/>
+
'''Nov 15, 2016''' - Dani, Sergey, Alex, Martin, Lars, McQ
+
* Dani: Neon.2 Release Review went out, IP Log will come early Dec.
+
* Dani: RC2 build tomorrow + test pass on Wed - last build before PMC approval is required
+
* Dani: Bugzilla 4.6.3 milestone created - currently too many bugs targeted 4.6.2, suggest moving out except if there's a patch attached
+
* Alex: '''Lucene''' - Using Lucene 6 for Platform.UI Indexing, prebuilt indexes of doc bundles need updating
+
** Prebuilt indexes of older versions will not be used, the impact is just a slowdown on first startup of help
+
** Old-version prebuilt indexes will trigger an entry in the errorlog, so projects will know
+
** Q: How much should we push for having a single Lucene in the Release Train? (In Mars we had two)
+
*** Problem: Moving to Lucene 6 is real porting effort, and it is not possible to be backward compatible
+
*** EGit or XText, who want to support multiple Eclipse versions, may be allowed to bind against other Lucene by exception; but Planning Council message should be to favor the latest by default
+
** Martin: Help Search Result Quality -- Was often critisized due to bad analyzers -- has it improved ?
+
*** Alex: Lucene 6 has apparently improved things, but team has not explicitly tested these cases
+
* All: '''Understaffed Projects Discussion'''
+
** Dani: Would like to send the message in a positive way: As a tool for interested parties to gain access to the code, and a tool for understaffed projects to bring in committers
+
** Alex: Would like to send the message, that Eclipse is open to contributions
+
*** McQ: Yes, but not at the cost of making existing committers feel bad
+
*** '''Lars''' to draft a new note (next week)
+
* Lars: '''Mylyn Notification API'''
+
** Still on Dani's list of items
+
 
+
<hr/>
+
'''Nov 8, 2016''' - McQ, Dani, Sergey, Lars, Dani, Alex
+
* Dani: '''Update on N-Builds'''
+
** Releng team will drop N-builds - will also reduce work on the Releng team
+
** Retention policies will need to be updated on I-Builds (keep weekly I-Builds)
+
** Provide a Hudson job which can mark an I-Build as unstable in case it isn't good
+
* Dani: '''Neon.2'''
+
** Feature Freeze today - Release Review just listing the N&N
+
** There was some new API, but it was backported mostly for bug fixes ... nothing relevant for the N&N
+
** Agreement that release reviews should be minimal effort - there was never community feedback on the reviews.
+
* Lars: '''Code Reviews on Understaffed Projects'''
+
** Make it easier for known, good people to get access to the code base for reviewing patches
+
** We'd still need to know the people - don't offer commit rights to random people
+
** Refactorings: Valuable if done by committers, but reviewing patches that are produced by refactorings is too hard
+
** Making someone a committer is preferred if there is some commitment to doing work moving forward
+
** Sergey: There's too many unreviewed patches against Platform in some areas - we need more committers.
+
** Proposal: '''Offer a shortcut for committers on one component who express interest in another component.'''
+
*** Criteria: Provided contributions in the past, and shows interest moving forward.
+
*** Don't offer commit rights just for one contribution.
+
*** Consider merging components if a component has become so small that it's unnecessarily hard to contribute
+
**** On a case by case basis, only if we think that merging components would solve more problems than creating new ones.
+
** Dani: Who makes the decision on shortcuts - existing committers, or PMC ?
+
*** In most cases, committers should have the say - but PMC may interfere if a project looks dysfunctional.
+
*** '''AI Alex''' will write up proposed statement
+
 
+
<hr/>
+
'''Nov 1, 2016''' - McQ, Sergey, Lars, Dani, Alex
+
 
+
We agreed on the following changes:
+
 
+
* Create maintenance branch immediately after RC1 instead of after the release. Use the maintenance branch to produce the upcoming release.
+
* Eliminate all code freezes on the main branch for RC releases, except for 1-2 days after RC1 before the maintenance branch is created. Freezes to allow test for milestone builds will still be applied (milestone freezes).
+
* We decided that we will only have ‘I’-like builds, using always signing.
+
* We decided to revisit the decision to always ship from master, but that's a longer discussion and won't happen soon.
+
 
+
<hr/>
+
'''Oct 18, 2016''' - McQ, Sergey, Martin, Dani, Alex
+
* Dani: '''PMC Approval for Sergey co-lead on Resources''' (Done)
+
* Alex: '''Lucene Update'''
+
** Looking at updating to 6.x in Oxygen - CQs ongoing for Orbit - hoping to make M4
+
** Others like Mylyn, Pydev, ... use Lucene 5.x at this time; others consume the Platform
+
** There is some potential breaking things but should be fine since multiple Lucene's in parallel can work.
+
** If an old pre-built help index can not be read, a new one is generated (Performance hit on the first run)
+
** Dani: No issue, will also update Jetty in M4
+
* Dani: Would like to open '''eclipse.jdt''' repository and corresponding sub-project to all JDT committers (currently only used for the JDT feature)
+
** The project is almost dead with only 2 active committers, since new JDT leads were not voted in
+
** Changes to feature will be rare, and Dani agrees to review
+
** Allows to put the Oomph setup file into a shared place where all JDT committers have access
+
** PROPOSAL AGREED by all.
+
* EclipseCon Europe next week - Dani, Lars and Alex will be there - will '''cancel next week's meeting'''
+
 
+
<hr/>
+
'''Oct 11, 2016''' - McQ, Dani, Lars, Alex, Sergey
+
* Dani: '''Neon Update 2 Endgame Plan sent''' - thanks for the feedback
+
* Sergey: We should talk about our release process.
+
** McQ asked Sergey to start the discussion via e-mail
+
* McQ: What do you think about Devoxx and Eclipse Converge
+
 
+
<hr/>
+
'''Oct 4, 2016''' - McQ, Dani, Martin, Lars, Alex, Sergey
+
* Dani: '''Neon Update 2 Endgame Plan''' - working on it
+
* Dani: '''Release Review'''
+
** In the past, features were not announced - now for 4.6.2, features + release review must be in by RC1
+
** Will do the minimum necessary / required by EMO, for Update Releases.
+
* Lars: '''p2 merge into Equinox status''' -
+
* Sergey: '''Logistics of dealing with Service Releases'''
+
** Managing version increments is very fragile and error-prone
+
*** Discussion already happened, see {{bug|499164}} -- we'll not increment minor versions on backports even if API is added
+
*** '''AI Dani''' send a note out to eclipse-dev again
+
** '''New & Noteworthy / Features for Update Releases:'''
+
*** If there's new features, there must be a New&Noteworthy for users (everyone agrees)
+
*** What about doing two feature releases per year with one service release each ?
+
**** Dani: Not having features in "some" releases would defeat what the Community wanted
+
**** Alex thinks that allowing features every 6 months would calm down most demand for new features
+
**** PMC Review of feature backports worked fine so far
+
**** '''RESOLUTION''' Will not change the process before having it settle a bit
+
***** McQ would love to see a single development stream all the time ...
+
*** Would the Generic Editor be acceptable in a release before June 2017 ?
+
**** Tentatively yes, it's a separate bundle not affecting other code, it matters to the Community, so why not...
+
**** Martin: OK, but what about newly introduced API ... would it be declared "provisional" initially ?
+
**** Dani: There's no such thing as "provisional API". Teams who decide on backporting must also decide on API.
+
**** Sergey: CDT has done full feature release every quarter for some time now and hasn't screwed up API...
+
**** Martin,Lars,Sergey: What about marking "fresh" API as "@noreference under construction" until it's hardened...
+
***** McQ: Then declare APIs as official only once a year ?
+
***** Wouldn't want to tie to a yearly cycle again ... but then we're back to the Version Numbering discussion...
+
***** '''AI All''' continue discussion on mailing list or next week.
+
 
+
 
+
<hr/>
+
'''Sep 27, 2016''' - McQ, Dani, Lars, Alex + Sergey Prigogin (guest)
+
* Discussion about PMC upstaffing
+
 
+
<hr/>
+
'''Sep 20, 2016''' - Martin, McQ, Dani, Lars, Alex
+
* Resources Leadership - '''AI Dani''' reach out to Szymon
+
* PMC upstaffing: Focus on large installs; UI Freeze monitor, code cleanup, solid solutions, focus on code reviews
+
* Dani: '''Java 9 Moved to July 2017''' - AI Dani talk to the Planning Council, proposing an "Update 1" in July
+
** Better for consumers, available via "just update", though little bit extra work (CQ + Release Review)
+
** Schedule looks still aggressive when looking at specifications; need to keep the team motivated
+
* Dani: '''SelectionListener SWT Change''' - reverted for M2 since more clients were affected than expected
+
** Proposed change turned out to be source-incompatible - will look at a different approach
+
 
+
<hr/>
+
'''Sep 13, 2016''' - Dani, McQ, Lars
+
* Upstaffing the PMC
+
* Build failures due to an SWT Change
+
 
+
<hr/>
+
'''Sep 6, 2016''' - Dani, Lars, Alex, Martin
+
* Dani: Thanks for approving Noopur
+
* Dani: Java Language Server Proposal - at the Foundation, will be called "JDT Language Server"
+
* Dani: RC4 - Fix for an Equinox p2 issue, only known issue being fixed, looking good
+
* Dani: Looking at the generic code editor, would prefer moving some things to M3 (talking to Sopot and Mickael)
+
* LTS: Market for paid fixes on old versions not quite as good as expected
+
* Release Reviews: When is a feature considered an "important feature" ?
+
** Important Features require a full release review thus lots of effort, avoided for Neon.1
+
** '''AI Dani''' discuss in Planning Council call tomorrow
+
 
+
<hr/>
+
<strike>Aug 30, 2016 - No topics</strike>
+
 
+
<strike>Aug 23, 2016 - No topics</strike>
+
 
+
<hr/>
+
'''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/>
+
  
'''Aug 09, 2016''' - Dani
+
'''June 05, 2018''' - McQ, Alex, Tom, Dani, Lars
* no one joined - had private conversation with McQ later
+
* Dani:
** '''guys, please announce when you can't join. I can make better use of my time than waiting for you in the call ;-) - thanks.'''
+
** Image limit for help should be increased? -> Not covered in the call
<hr/>
+
** Will most likely not be able to join the next call
 +
* Alex:
 +
** Support only last LTS version of Linux?
 +
*** Agreement to drop old LTS versions for 4.9 but not to change the target environment for 4.8
 +
** Dropping big Endian -> we all agreed to drop it, MQ found the email to cross, so we can remove it
 +
* Lars:
 +
** Update to EPL 2.0?
 +
*** change of about.html is trivial
 +
*** requires version updates of MANIFEST.MF and pom.xml
 +
*** Script for source update look good, Lars checked manually lots of files
 +
*** Coordindate with Jay or Noopur for the JDT UI update
 +
*** Dani suggested to announce such work via the mailing list so that everyone is aware of the work
 +
 +
** Only one N&N per release? -> Agreed to have one document per release
 +
** Do we get a name for Photon+1 -> Dani: Our SDK is called 4.9, splash screen will only be month year, planning counsil still discussing
 +
** Include Tips and Tricks in the SDK -> Not covered in the call
  
'''Aug 02, 2016''' - Dani, Martin, Alex
 
* Dani: New [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_7_draft.xml Oxygen Plan Format]
 
** '''AI Dani''' ask Denis about aggregating the Sub Wiki's into the master page
 
* Alex: SWT Fragments for ARM64 etc
 
** Tycho doesn't support auto-selecting fragments - in contact with Jan and Tobias
 
** Dani: Would like to revert changes - don't want to punish people who are not interested in fragments
 
** Not really an SWT problem, so editing .target files would be a clean solution
 
** Will probably go with empty (dummy) fragments without natives, as that's the simplest solution
 
* Dani: SWT team - Lakshmi going to Sweden, will not be available until end 2016
 
** Arun is mostly back, Sravan is now on Releng
 
** Need to push further on building at the Foundation!!
 
** Alex: Getting CentOS for building ... but test machines are on SLES11, which is too old, will need at least SLES12
 
*** Dani: Will need an owner at the Eclipse Foundation to ensure this proceeds ! Alex agreed to further drive this.
 
* Target Env: Dropping REL6 -- reference platform for testing will only be REL7 (though will continue to run on REL6)
 
** Reducing support level this year, in order to prepare for only supporting GTK3 next year
 
  
<hr/>
+
'''May 29, 2018''' - Alex, Tom, Dani
 +
* Dani:
 +
** Uploaded IP log
 +
** Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck
 +
** Finalized Photon plan
 +
** Sent Release Review material for approval to PMC mailing list
 +
** RC3 looks good so far
  
'''July 26, 2016''' - no meeting
 
  
'''July 19, 2016''' - no meeting
+
'''May 22, 2018''' - Alex, Tom, McQ, Dani
 +
* EPL 2.0
 +
** Still working with foundation on whether we can gradually move to 2.0
 +
* Will we be supporting updates from release to release in the new 3 month release cycle?
 +
** Yes, unless we explicitly indicate otherwise.
 +
** To simplify this, we should have a "latest" update site
 +
** We need to make this simpler for users, but not get in the way of the EPP, OOMF, etc.
 +
** Alex to write this up in more detail
 +
** Dani reminded us that there had been a previous discussion in the planning council
 +
* Project leads have updated Photon plans
 +
** Dani will be updating the overall plan; PMC to comment on bug 529640
 +
* Dani also working on release review and IP log
 +
** PMC members to approve once it's ready
 +
* As previously discussed our first milestone will be called "M2"
  
<hr/>
 
'''July 12, 2016''' - McQ, Lars, Alex
 
* Dani: Hackathon summary
 
  
<hr/>
+
'''May 15, 2018''' - Alex, Tom, McQ, Lars, Dani
'''July 5, 2016''' - Lars, McQ, Alex, Dani, Martin
+
* GDPR
* Lars: SWT move to Java 8
+
** audit did not report any issues on our project pages
* Alex: Initial builds of GTK 2.24 for AIX - planning to bump minimum GTK version to 2.24
+
* Opening development for 4.9
** Will remove non-cairo drawing, this is where most of the breakage happens
+
** Will branch RC2 and update master with required Releng work
** Ubuntu 12.04: 2.24.10 / 3.4.5
+
** master will be open after RC3
** RHEL 6: 2.24.23-6
+
* EPL 2.0
** AIX, HP-UX, Solaris ? -- Oxygen will only focus on Linux, Windows, Mac
+
** No plans to do anything for 4.8
** Secondary Platforms: Not built on EF Hardware, but interested parties can contribute binaries
+
** Lars will look into it
** Trying to support Platforms which can't move up to modern GTK at a similar pace as Linux is hard
+
** Ideally we gradually move to 2.0
** '''AI Alex''' write up a message to the Community
+
* Lars: {{bug|486961}} extending the Eclipse Text Editor
+
** Dani: Text Editor must remain unchanged, but feel free to provide a new different code editor
+
** https://bugs.eclipse.org/bugs/show_bug.cgi?id=496114#c7
+
** Not against adding extension points ... but having the standard text editor adopt those is a no-go
+
* Dani: Build, and Hackathon
+
  
<hr/>
 
'''June 28, 2016''' - McQ, Martin, Alex
 
* Discussion about Language Server Protocol
 
** MS sponsoring hackathon in Zurich, Dani expected to go there
 
** The protocol has an Open Source license, but there is no Open Source Governance ... who owns the specification?
 
  
<hr/>
+
'''May 8, 2018''' - Dani, Alex, Tom, McQ
'''June 21, 2016''' -  
+
* GDPR
*  
+
** Eclipse Project collects no information from the users on the project websites
 +
** The Error Reporting tool, might be impacted
 +
** Also possibly bugzilla <-- Do we need to delete bugs older than some retention period?
 +
** Impossible to remove emails from all git repos (because of cloning)
 +
** We need to be sure to respond to requests from the foundation
 +
* Jetty
 +
** 9.4.10 is in latest build, and help system is working
 +
** they made the dependencies that were problematic optional
  
<hr/>
 
'''June 14, 2016''' - Dani, McQ, Martin, Lars
 
* McQ: '''Mattermost / Slack''' for communication
 
** not much different than newsgroup or IRC, but very dynamic when everybody is on it
 
* Lars: '''Master is Open'''
 
** Dani: Simple story - if we do need an emergency build we would create the maintenance branch on demand based on the tag
 
** Only limitation: We can't update the parent pom's at this time
 
** Don't have tools to check if the MANIFEST.MF needs to update - only API Tooling for API changes, but nothing for micro changes ({{bug|360703}}) is open to improve that)
 
** We do have an alert if there's no version/source change but the binaries changed (e.g. due to a compiler update) but that's not in the workspace
 
* Lars: '''Upgrade SWT to Java 8 for Oxygen ?''' - to be decided by the SWT team, the PMC is OK with the update if the SWT team decide so
 
* McQ: '''Language API -- Overlap between Orion and Che''' (from [https://dev.eclipse.org/mhonarc/lists/ide-dev/ ide-dev] mailing list and {{bug|496114}})
 
** The protocol is pretty big, but well documented - looks like an improved version of Flux
 
** The protocol is generic, implementations need to be specific -- some implementations already ongoing (Javascript)
 
*** People start working on editors hooking up to the protocol -- does it make sense building a JDT Language Server ?
 
** The tricky part is, that the Che workspace model is very different than the Eclipse workspace
 
** How to create a small lightweight server that would scale -- one workspace per user may not scale
 
*** At the beginning, it would be less powerful than JDT today since context would be lacking
 
*** But the direction is very interesting ... though maybe too many people are implementing the same thing right now
 
* Dani: '''What goes into the Neon Update Releases'''
 
** as discussed on May 17 (see below): Must be in master first, consider for backport after that
 
** '''AI: Dani''' will prepare a note
 
* Dani: '''Using Sound in Eclipse'''
 
** Eric Rizzo uploaded a feature to provide different sounds for successful or failed JUnit tests (see {{bug|496003}})
 
** Martin: CDT has allowed sound for breakpoint actions since long
 
** Lars: Moving the Mylyn notification framework to Platform UI was on the plan already, now considered for Oxygen
 
** McQ: Every Platform has an OS-Level Notification system so '''that''' should really be leveraged
 
** Martin: Mylyn notifications can be "active", can OS notifications also be active ? - McQ thinks yes
 
** Could work on SWT implementation of host platform notifications in parallel to pushing down the Mylyn API
 
** Request on specific JUnit sounds not yet decided.
 
  
'''June 7, 2016''' - Dani, McQ, Alex
+
'''May 1, 2018''' - cancelled due to public holiday in most Europe
* no topics
+
  
<hr/>
 
'''May 31, 2016''' - Dani, Martin, Lars, McQ, Alex
 
* Dani: '''IP Log'''
 
** The tool did not work, but it was manually submitted and approved
 
** In previous years, some people wanted the IP Log to not be so publicly visible, so now only project leads can generate and submit it
 
* Dani: '''Release Review'''
 
** Reply to the public E-Mail with comments or +1
 
* Dani: '''Update Jetty to 3.9.3'''
 
** Consensus to update - Jetty team working on fixing their update site
 
* Dani: '''RC4 Status Update'''
 
** Cooling down - maybe 2 fixes from SWT, 1 in Platform/Text Search, and the approved doc fix for deprecating the mac command
 
  
<hr/>
+
'''April 24, 2018''' - Dani, Lars, Alex, Tom
'''May 24, 2016''' - Dani, Lars, Martin
+
* Target environments
* Dani: '''IP Log Generator''' - New version is unable to deal with Eclipse Project, Wayne is working on it
+
** We will keep Java 8 and 10 and remove java 9 from the list
* Dani: '''Release Review''' - Deadline next week (June 2)
+
** remove JVMs as soon as they run out of support from target environments  - AGREED
* Dani: '''Deprecation Request from Brian'''
+
* javax.annotation
** Command org.eclipse.ui.cocoa.fullscreenWindow -- all PMC agree on the deprecation although late, since it only affects docs
+
** Version  shipped is quite old, should we update it to newer version
* Dani: '''Copyright End Date'''
+
** Update to latest standalone release to be tried
** '''AGREEMENT''' to no longer require updating the end date (though committers are still ALLOWED to update it)
+
** Alex to try to drive this through
** Will no longer run the automated copyright tool (actually haven't run it the past 3 releases)
+
* Notify cross project about removal of ee modules from the JVM
** Will live with the source code notices being inaccurate / incomplete - the accurate state is in Git
+
** People don't follow Java 11 work so will probably be surprised when things start to fail so we better try to spread the information
** This is acknowledged to not be ideal, but the best compromise we can come up with since "bulk changes" are not OK
+
** Dani will send a link to the JEP containing detailed information
* Dani: '''Neon Status'''
+
* Contribution guidelines
** Java 9 launching - affects all Java consumers, not clear yet what Oracle will do, no plan changing Equinox/Launcher at this time
+
** Do not open bugs for simple changes and cleanups
 +
** Actual bug fixes to be split from cleanups in separate patches so the bug commit is straight on the topic
 +
** Dani will update the wiki
 +
* Cancel May 1st call - public holiday in Europe
  
<hr/>
 
'''May 17, 2016''' - Dani, Lars, Martin, Alex
 
* Dani: '''{{Bug|475184}} Neon Plan Update 2'''
 
** Windows 10 and Ubuntu 16.04 will be added as "active" Platforms that people do work on
 
** SWT would like to remove Windows 8 and Ubuntu 12.04 from the list of reference Platforms
 
*** Alex: Ubuntu 12.04 has GTK 3.10 which is hard to support
 
**** Correction (Markus): Ubuntu 12.04 has GTK 3.4.2. Ubuntu 14.04 has GTK 3.10.8
 
*** Message is clear: "Supposed to run on older Platforms, but these are the primary ones" - including last 2 LTS ones
 
** Agreement to keep Windows 7 and remove Windows 8
 
** '''AI Dani''' to check if SuSE 11 is right (12 been out since 2 years)
 
* Dani: '''Copyright End Date''' - EMO: To be decided per project
 
** IBMers will have to continue updating the copyright end date, regardless of what other companies do
 
** Copyright tool: Only the person who made a change is allowed to update the Copyright notice
 
*** gray area: actually fixing the date can be considered a change
 
** Alex is in favor of consistency across the project
 
* Dani: '''Policy for Neon.Update Releases''' - What to allow in, which rules to apply on the endgame
 
** Martin: Fact is, that the Update stream is built less often, and thus also tested less often
 
** Rule: Any fix or feature must be in master first (and may be backported thereafter)
 
** Will want "some" features in Update, but probably not all of them - '''decision''': discuss feature by feature at PMC
 
** Stakeholder who's interested in a backport must send a quick note to the PMC (just like for API change requests)
 
** In case too many requests should come in, could still discuss updating the procedure
 
* Dani: '''Neon RC2 Builds Update'''
 
** Currently looking good, but latest Java 9 Launchers broke the Annotation support - investigating
 
** Quality generally looking good - "Stock GTK3" very stable now
 
** GTK3 on SuSE, Fedora looking much better than Mars (at least with a GNOME shell)
 
** Lars: {{bug|493477}} detached editors broken on GTK2 nominating for RC
 
  
<hr/>
+
'''April 17, 2018''' - Dani, Alex, McQ
'''May 10, 2016''' - Dani, Martin, Alex, McQ
+
* On Java 11...
* Dani: '''Policy for what should go into Neon.Update Releases'''
+
** We are actually shipping the javax annotation support
** Would like to be more flexible than in the past - discussion point for next week
+
** Java 11 is working in 4.8, but isn't in 4.7.x
* Martin: '''RHEL7 -- GTK3 versus --launcher.GTK_Version 2'''
+
*** Tom Watson is investigating why it is not working 4.7.x
** GTK2 rendering still much more reliable than GTK 3 - forced to release commercial software with the GTK2 fallback for now
+
*** Drawback: Even with MATE desktop using GTK2 (for accessibility), the Browser widget webkitgtk2 is not easy to get since not in the official repos
+
** Alex: Desktops are moving faster - adopting change very quickly - cannot keep up with the investment that the Community currently makes in SWT
+
*** Heavily limiting what we support looks like the only viable approach at the moment...
+
*** There's 2 big groups of bugs: (a) "Next" version of GTK, and (b) "Old" version like Ubuntu 13.04 which has 3.10 - can we limit support to "latest" ?
+
*** Martin: Need "LTS" Linux (RHEL 7, RHEL 6, Ubuntu 12, 14 - soon 16).  
+
** Alex: Gnome people have come up with a "Container environment" for GTK - could ship Eclipse that way ?
+
*** Limitations: Updates must come through this application - already using Gimp from such an environment
+
*** Might be able to deliver Eclipse that way next year (Oxygen)
+
  
<hr/>
 
'''May 3, 2016''' - Dani, Martin, Alex, McQ
 
* [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02598.html Brian's request on the PMC list]
 
** McQ: Why would we care about adding small enhancements in RC1 when we should focus on testing and critical fixes
 
** Dani: Two parts in the change - the original one (approvable), but another change also sneaked in (enable the prefix search) - not approvable
 
** Alex: People don't want to wait for getting in an improvement...
 
** McQ: OK for adding as feature to Neon.1 , but Neon.0 should be focused on bug fixes
 
** Keep in Gerrit for now - Neon.1 stream is typically opened when no new changes are expected. Rebasing is relatively easy from Gerrit.
 
** '''ACTION''' McQ to -1 and argue why.
 
  
* Alex: '''Update on Accessibility'''
+
'''April 10, 2018''' - Tom, Dani, Lars, Alex
** broken since GTK 3.8 where accessibility is no longer a module but shipped with GTK itself
+
* Discussed {{bug|533390}}: Eclipse does not launch with Java 11
** due to that, the way accessibility is implemented is totally different - no more factories - experimenting with possible approaches
+
** Discussing the addition of Eclipse to their test infrastructure, at a meeting a month from now
+
*** and even so, not sure how well accessibility is tested in GTK itself
+
** Launching with -gtk_version 2 is not a workaround, because the v2 GTK doesn't register as an accessible application in newer desktops !
+
  
<hr/>
 
'''April 26, 2016''' - Dani, Lars, Alex, Martin, McQ
 
* Mickael's API change request ... tried to address feedback from Markus but then got no additional feedback
 
* Alex: '''Accessibility''' - broken on recent GNOME and probably others
 
** Accessibility is important. Have reports from users who say "Eclipse works for them"
 
** McQ: Need to keep some focus and look at what we can do for Neon.1
 
* Alex: '''Platform.ui generification of project'''
 
** Dani: Won't get a consistent story when done piecemeal - needs to be done "per framework" and not necessarily "per plugin"
 
** McQ: It's a huge effort - enough by itself for one whole release !
 
** Dani: If a meaningful separate unit is found that can be done, but things like e.g. LabelProvider, ContentProvider and TreeViewer can't be done isolated
 
** Lars: If a smaller unit of generification work is possible, that's permitted when somebody signs up for the work and it has been discussed in the public
 
** '''ACTION Alex''' to prepare a message for review and then send that.
 
* Lars: '''Copyright discussion'''
 
** Not having the end date in the copyright notice makes the copyright invalid.
 
** The IP Advisory Board will discuss it again.
 
* Dani: '''Update on FEEP'''
 
** Paul not reached out yet
 
** A list now shows what's done or in progress - but no time
 
* Dani: '''Update on M7'''
 
** Last 4 builds failed due to infrastructure issues - Maven stuff could not be accessed
 
** Will try to enable cache on the build side and re-try until the cache is full
 
  
<br/>
+
'''April 3, 2018''' - Tom, Dani, Mcq, Lars
'''April 19, 2016''' - McQ, Dani, Martin, Alex (regrets: Lars)
+
* 4.7.3a update
* Dani: '''IP Stuff''' on Copyright Updates pinged the Lawyers but no update yet, need to wait
+
** Delivered RC2 on Saturday, so we could fix some badness in handling Java 10 "var" support (tl;dr: rename appeared to allow you to affect "var" as if it were a type (but would not have modified the code))
* Dani: '''FEEP''' discussed on AC, People were sympathetic to our issues.
+
** Currently think we're done
** General direction that FEEP sponsored work is no different than other contributions
+
* Naming milestones
** Wayne took the Action Item setting up a meeting with Paul and interested parties.
+
** As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1".
** Website with ongoing FEEP still pending - Dani is tracking
+
** We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming.
* Dani: '''All PMC please review and +1 API requests''' when you find time
+
** McQ does review and typically ask question but not close enough to the code to +1
+
** '''AGREEMENT''' on "+0" votes to express "no objections but others should approve too
+
* '''Reviews vs. Features'''
+
** Alex: Badge System was quite successful at Fedora
+
  
<br/>
 
'''April 12, 2016''' - McQ, Dani, Martin, Lars, Alex
 
* Lars: '''Get rid of the Copyright Year Update Requirement'''
 
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485257#c13 bug 485257_c13] EMO: All information is in the git repos
 
** McQ: OK lifting the requirement but doesn't want wrong information in files .. get rid of all copyright years ?
 
** Dani: Replacing the end-date by "[see git]" might be an option
 
** '''ACTION''' McQ or Dani talk to IBM Legal, then decide next week
 
  
* Lars: '''{{bug|490012}} Remove Project Settings to force strictly compatible JRE'''
+
'''March 27, 2018''' - Tom, Dani, Mcq, Lars, Alex
** Example: When don't have admin rights on a customer machine, can't install anything
+
* Java packages for configured Java in workspace
** Dani: With the Gerrit Build Validation, the risk of getting unbuildable code is no longer there
+
** Equinox no longer provides hard-coded information about execution environments.  In the past this information was used at runtime for describing the running execution environment within the OSGi Framework.  Other usecases outside the Framework started uses the Java profile data from Equinox.  Equinox no longer has any need for the hard-coded information so no longer provides it.
** Proposal: Project requests a particular JRE, but the workspace configures treating this as an error or warning
+
** JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
** '''DECISION''' to get rid of the strict error per project.
+
** JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
 +
** See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=531642 531642] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=532773 532773]
 +
* SWT clean-up
 +
** Lars reviewed the removal of Windows XP.  Built binaries locally on Windows.
 +
** Found a form data issue deleted some code that was still used
 +
** Tom - Unit tests didn’t catch the issue. Concerning?
  
* Dani: '''{{bug|475934}} API Change on model processing order'''
+
--> Update from Lars after the call: Later testing did show that this is a bug already existing in Eclipse. 4.7 and master and not related to the patch
** Dani: Even if this fixes an issue, M7 is late in the game
+
** McQ: Does API specify the order of events? - No; only on internal method.
+
** McQ: Is this transparent to most consumers, or will 5% have to react in their code ?
+
*** Lars has a few customers hit by this, but had to do a few tricks to mitigate the issue;
+
*** Making the change won't break them, but they could now remove their workaround
+
*** Martin: Not a formal API change and feels like cleanup/polish - M7 as the "performance milestone" feels just right for this
+
** Dani: Can be convinced making the change now if it is widely announced; convinced that this will hit more people than helping
+
** '''DECISION''' to allow making the change and announce widely.
+
  
* Dani: '''FEEP and EMO Hiring Update'''
+
** Lars did review and test
** EMO working on website update to announce the work being done
+
** Dani - put all the code in the branch and produce a build and ask windows community to test it
** Didn't talk about the specific SWT issue around "FEEP should provide clean stuff rather than quick fix"
+
** Mcq - thinks it is a good idea
** Already agreed on hiring a person, communication will come in June/July
+
** Dani - create an official build for testing, not out of master with normal builds
 +
** Lars - what is the risk of putting in master
 +
** Dani - can do the build right away pre-CQ review approval.  Allows for more quick testing.
 +
** Alex, no need for a branch, can be a developer build we publish.  Alex will ask Leo to do this.
 +
* Jetty version
 +
** Jetty added non-optional dependencies on service-loader
 +
** Dani - got reverted, but old versions still caused Gerrit build issue
 +
** We don’t need the service-loader for our usage of jetty
 +
** jetty may be making a hard requirement on an implementation of server-loader (Aries spi-fly)
 +
** Can we move help off jetty? Will be a major undertaking.  Should figure out what it would me to do so.  Currently no interested contributer has stepped up to do the work to figure out what this would mean.
 +
** Equinox will still need jetty for the http service implementation.  Perhaps things are more simple if this is an Equinox only dependency.  Only pull in jetty if the http service implementation is needed and then pull in all of jetty and its dependencies.
 +
** No current plans or interested contributors for providing our own service-loader implementation.
 +
** Our build should start resolving the capabilities are requirements which would catch issues like this early in the build.
 +
** Alex - can we move latest tycho to get the capability/requirements meta-data.  No objections?  Alex will move forward.
  
* Dani: '''IDE-dev proposal'''
 
** People don't find our tips and tricks; suggestion to add to the welcome page
 
** Solstice L&F issue on old Browser
 
*** McQ: Eclipse is a developer tool, and developers run on current browsers ... OK if only old browsers are affected
 
*** OK if there is a way out (such as choosing a different Theme) - not blocking anyone.
 
  
<hr/>
+
'''March 20, 2018''' - Dani, McQ, Tom, Lars, Alex
'''April 5, 2016''' - McQ, Dani, Alex, Martin, Lars
+
* Dani: The IBM SWT team considers the Windows XP removal too risky and in addition has no capacity to look at that big change. Fine if someone else looks at the removal. The type changes will have to wait after Photon (too risky). Lars will ask Conrad and Alex will also look at the patches.
* Dani: '''FEEP Update'''
+
* Databinding generification should be done early 4.9, too late for Photon.
** Foundation pays Patrik Suzzi as a contractor to look at Platform bugs (triage, and fix)
+
* Dani: Eclipse support for Java 10 will be merged to the official branches starting Wednesday. A Marketplace entry for 4.7.3 will be made available once 4.7.3 is released. The first official release with Java 10 support is 4.7.3a scheduled for April 11.
** Will focus on critical / blocker bugs initially, or bugs already tagged by committers for 4.6 M7 and 4.6
+
** Mickael Barbero still quite involved in Releng - Foundation looking for Releng replacement so Mickael can develop (already reviewed autosave - but might be on vacation at the moment)
+
* Dani: '''Solaris 32-bit'''
+
** Will provide Solaris 64-bit binaries, but stop building Solaris 32-bit with Neon
+
** Open question: what does this mean in terms of GTK versions ? (GTK3 would be nice)
+
*** Alex may start asking questions as soon as the binary fragments are in the repo
+
** McQ: Windows 32-bit is still active - future change probably tied to
+
* Dani: '''New Solstice Welcome'''
+
** Some issues with Logo, sometimes it's there sometimes not; Brian working on it, Solstice will become the new default in M7
+
** Currently, ONE product logo must work on all Themes - bad design - probably to be changed
+
** McQ: Do we mirror the welcome for BIDI ? (Dani thinks yes, saw bugs come along)
+
* Alex: '''FEEP Process Discussion (around Themed Scrollbars)'''
+
** "Scrollbar Theming": Contractor doing work without SWT committers knowing, and disregarding suggestions from the committers
+
*** Looks like the proper fix from committers was not even tried ?
+
*** It's OK putting adding a layer if it solves a problem ... but if the proper solution is suggested, it should at least be tried.
+
*** McQ: Accessibility - with 10000 items it's getting slow - should try the native way
+
** Lars: Transparency? - No insight on what FEEP's are actually ongoing
+
*** '''AI Dani''' send note to Wayne and Mike asking for location of FEEP Project List
+
*** '''AI Martin''' compare against AC's requested list, and put on agenda for the next AC call
+
** Lars: Styling is actually an important business driver!
+
** Alex: FEEP feels like "quick and dirty" is favored at the moment over sustainable solutions !
+
*** McQ: Perhaps a problem with the funding model ?
+
*** Dani: Lack of people who want to fix issues on the list of the AC ?
+
*** McQ: FEEP is still early - time to provide feedback now. Goal '''Transparency''' on what's done, and why design decisions are taken.
+
*** McQ: Who cares for StyledText - have Markus have a conversation with the submitter ?
+
**** Lars: We have no API for styling scrollbars (background, foreground) - Alex: '''THIS''' is what the FEEP should have adressed !
+
** Martin: Next step should be conversation with EMO about toplevel transparency, and basic guidelines ("sustainable solution over quick fix").
+
** Alex: Need something like JEP (Java Enhancement Process) for FEEP.
+
*** McQ: Agree this is what we want, but would it discourage submitters ? The lighter-weight the process the better...
+
** Alex: If anyone stepped in and did that work it's fine ... but such work sponsored via FEEP seems putting resources in a wrong direction.
+
* Lars '''Question: Google work on improved Type Hierarchy'''
+
** Main work is a new Index, Type hierarchy will be the first client, planned past Neon (contributor: Stefan Xenos).
+
  
<hr/>
 
'''March 29, 2016''' - McQ, Lars, Martin, Dani, Alex
 
* Lars: '''PDE Build in Maintenance''' - Officially state this ?
 
** PDE Build still works; and we're not yet in a position to replace it (it's needed for manual export)
 
** Alex: What about not quite declaring maintenance mode, but state something like "for a new project, you might consider Tycho or something else"
 
** McQ: '''DECISION''' Ensure that on the PDE Build Homepage, we clarify the relationship between PDE Build and other technologies (like Tycho)
 
* Lars: '''Integrate more projects into Platform UI?'''
 
** Having few commits on a component, or overlapping committer list, is not an argument for merging projects
 
** Arguments for merging would only be if existing committers struggle with handling incoming contributions (or if component leads want to get merged) ... but that's not quite the case right now. Being able to look at a component by itself has also some value.
 
** Alex: Being able to handle Team/UI would make sense for Platform/UI ... but not for the native resources
 
** '''DECISION''' to not merge projects at this time.
 
* Lars: '''Request for API Changes on eclipse-pmc mailing list'''
 
** McQ: OK for a single PMC member to +1 the obvious ones, but should do due diligence on API changes (eg ping consumers etc)
 
** Alex: OK for API Additions, but should discuss API changes
 
** Compromise: API change requests must be requested on eclipse-pmc mailing list; PMC members must "speak up" on the mailing list if they want an item discussed, otherwise any PMC member can just approve. '''AI Dani''' notify mailing list.
 
* Dani: 900 Bugs targeted Neon
 
** Need to move away from "just moving bugs from one milestone to the next"
 
  
<hr/>
+
'''March 13, 2018''' - Dani, McQ, Tom
'''March 22, 2016''' - McQ, Dani, Alex, Martin
+
* Alex had troubles to join; Lars still in vacation
* Dani: we shipped M6 on time. Watch out for API change requests on the PMC mailing list.
+
* Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
* Dani: public holiday on Friday (Good Friday) and/or Monday (Easter Monday)
+
** ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project
* Alex: gave an update on tests running on CentOS with GTK+ 3
+
* Discussion about Che
+
** McQ: Che still feels monolithic - unfortunate that the Eclipse Resource Model was not considered
+
** Dani: Preferences in Che vs. the IDE
+
** McQ: What would it take to unify Che, Orion and the Eclipse IDE ?
+
  
<hr/>
 
'''March 15, 2016''' - McQ, Dani, Alex, Martin
 
* Dani: '''Platform/UI got awarded as the Most Open Project :)'''
 
* Dani: Mention PDE/Build as in maintenance? - discuss next week when Lars is back
 
* McQ: Merge Subproject Committers Groups? - Membership based on expertise is important
 
* Dani: Test Failures due to hidpi work - not entirely done yet but looking good for M7
 
* Dani: Lots of failures due to "Widget Disposed" failures
 
** Gerrit tests didn't fail, probably sine the event timing on VNC is a little bit different than running manually
 
** Alex: VNC/Gerrit tests run on GTK2 whereas all the rest defaults to GTK3 now
 
** Looking for a machine with GTK3 to enable them -- working with Mikael Barbero to get this for David
 
* VS Code Open Sourced - plugin model is very similar to Orion
 
** Excellent with TypeScript, not quite as good as Orion for JavaScript
 
** Ideally, would love to see some unification of web-based IDEs (like Che already using Orion editor)
 
  
'''March 8, 2016''' - No call
+
'''March 6, 2018''' - McQ, Tom, Alex
 +
* Short call without any interesting topics
  
<hr/>
 
'''March 1, 2016''' - Dani, Martin
 
* Dani OOO next week
 
* Alex: '''{{bug|179924}} SSH-agent authentication''' 3rd party code for SSH using JVM internals
 
** Dani: Suggest asking on the bug for confirmation what's the JNA team's plan ... they have a full year time
 
** Martin: JNA seems quite widely used these days...
 
* EclipseCon next week - Dani and Alex out - Martin will open the Bridge but might be canceled.
 
  
<hr/>
+
'''February 27, 2018''' - Lars, Dani, McQ, Tom, Alex
'''February 23, 2016''' - McQ, Martin, Dani, Alex
+
* JDT support for new Java releases
* Dani: '''Mars.2 is on track'''
+
** McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible
* Dani: '''FEEP Update'''
+
** Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community
** EMO still looking for people bidding on items prioritized by the AC - Pascal to look at some p2ish issues in April
+
* Dropping XP support
* Dani: '''Update on Welcome'''
+
** Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release
** Brian de Alwis contributed Solstice based Welcome - looking nice and done right, just a 4th theme to select (some artwork needs IP review)
+
** Mail to be posted to cross project by Dani to gather feedback
* McQ: '''Scrollbars on Windows''' and their appearance
+
** Alex: 1 week for gathering input on cross-project - '''AGREED'''
** Dark Theme Scrollbars don't currently look good on Windows - proposal to paint in SWT - currently proposed on StyledText only
+
** If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex
** Dani agrees with Alex that this would open the door to hell
+
** To be formally voted after the mail to cross-project
** McQ: Having seen AWT take ages in terms of emulating OS appearance makes the idea of painting ourselves not too appealing
+
* Release names
** Also concerned about special cases (like performance with ultra-long lines etc)
+
** Version only, release names are irrelevant from Eclipse TLP side - '''AGREED'''
** Alex: Any approach in this direction will have bad effects in terms of SWT maintainability and its cross-platform support (think Wayland, RAP, ...). API additions designed with not at least 2 out of the 3 WSs supported are probably not good cross platform APIs considering how different the WSs are.
+
* Inactive committers pruning
** Could a GTK version on Windows perhaps be an alternative? Alex(after meeting additions): GTK is supposed to run fine there and Broadway on Windows can be driving for it as figuring the build on Windows should give working SWT (thanks to Wayland work making GTK port quite crossplatform).
+
** Lars: no access to committer emails so sending just to the mailing list
 +
** Wait 2 months for reply before action
 +
** McQ: ask foundation to send direct mails on behalf of the project, if foundation is not fine - remove committers directly
 +
** Alex: only public replies to the mailing list are accepted so people wanting to remain committers at least follow the mailing list
 +
* Tip of the day -
 +
** Lars: CQ approved, to be merged today/tomorrow
 +
** Alex: we should have it part of the build and part of the p2 repo for easy testing
 +
** Dani: unclear APIs to be removed and to be simplified so we don't end up maintaining useless parts
 +
* GTK 2 vs. 4
 +
** Alex: Gtk 4 release aiming at late 2018, it's big change in drawing so conflicts with Gtk 2 badly
 +
** Alex: Gtk 2 support to be removed in future one of the next 2 releases, whether Sep or Dec to be discussed later in the Photon release train
 +
** Alex: mail to cross project list around Photon M7 or RC when more information on both Gtk 4 release plans and SWT bugs will be known
 +
** McQ: what is our statement on supported Gtk version?
 +
** Alex: Statement should be: Once SWT switches to latest Gtk version as default, support for previous versions goes into deep maintenance mode but will kept until it starts hurting new development and support for the default version at which point to be removed.
 +
** To be discussed further.
  
<hr/>
 
  
'''February 16, 2016''' - Alex, Dani, Martin
+
'''February 20, 2018''' - Lars, Dani, McQ, Tom
* no topics
+
  
<hr/>
+
* Dani: Update on 4.7 RC3
 +
* Lars: Can we drop Windows XP support?
 +
** Lars: Big contribution comes in (https://bugs.eclipse.org/bugs/show_bug.cgi?id=531097), dropping XP support might be a good motiviation to contribute more also to other people. Removing lots of code including the version checks will also result in a cleaner code base for maintenance and might improve performance.
 +
** Dani: IBM investigate if they officially drop XP
 +
** Tom: Do we need support XP with the latest Eclipse version?
 +
--> Pending on the answer of the IBM team, will be discussed in next weeks call
 +
* Tom: OSGI CQs updated and approved for OSGi Service Platform 7.0 version
  
'''February 9, 2016''' - Alex, McQ, Dani
 
* Dani: looking good for Mars.2 (4.5.2) - no RC4 planned
 
* Dani: please take a look at {{bug|466370}} Welcome Screen redesign
 
* Dani: please take a look at {{bug|472614}} Smart Project Importer
 
  
<hr/>
+
'''February 6, 2018''' - Lars, Dani, McQ
 +
* Lars: Can we mark MInput and MInputPart for deletion ({{bug|509868}})?
 +
** Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references.
 +
*** McQ agrees
 +
* Dani: [https://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00743.html Topic on ui-best-practices-working-group list]: Replace "..." with an ellipses Unicode character
 +
** Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
 +
** McQ:
 +
*** Mac OS UI guidelines specify to use the ellipses character
 +
*** SWT could do the right thing depending on the platform
 +
* Lars: view menu, minimize and maximize buttons look bad to him. Would like to replace the view menu with ellipses
 +
** Dani: Would have to change all three together. View menu is always there and not indicating an overflow
 +
** McQ: Windows 10 also uses a triangle, but upwards. Current view menu is used and familiar to users for at least more than 10 years.
 +
** Lars to file a bug report and send the bug number to the PMC
 +
* McQ: Should discuss in one of the next meetings how JDT can handle the new release cadence for Java
 +
** Dani: We will see how it goes with Java 11 (18.3)
 +
* Dani: How will we name the milestones in our new new release scheme?
 +
** Consensus to start with M1 after each release.
 +
** Up to planning council to decide the release naming convention. Lars: Would prefer year/month
  
'''February 2, 2016''' - Dani, Alex, Martin, McQ
 
* Dani: '''Foundation Hires''' - Dani hopes they'll find someone in Europe to deal with Releng issues
 
* Dani: '''Neon M5''' went smoothly - M6 will be the API freeze; tomorrow is the last planned RC for Mars.2
 
* Dani: '''CQ Deadline''' on Feb.12 for Neon
 
* Dani: {{bug|486647}} for changing the strategy when opening files not associated with Eclipse
 
** With M5, can now use the System Editor (default) or Text Editor - there's a request to always use the text editor
 
** Dani thinks that for JPG one wants to use the OS
 
*** Martin agrees, OpenWith and choosing an editor remembers the choice, and one can also remember;
 
*** We also show the System Icon in Project Explorer, so using the System Editor by default is natural
 
*** Alex set it to "ask via popup" - can be quite noisy, but avoids trouble when KDevelop or something associated itself with Makefiles or so
 
** Agreement that flexibility is fine - see no case for changing the default
 
  
<hr/>
+
'''January 30, 2018''' - Alex, Lars, Dani, Tom
'''January 26, 2016''' - Dani, McQ, Alex, Martin, Lars
+
* General Updates (Dani)
* Official PMC representation on AC calls - keep McQ listed since he is interested but nominate Dani instead of John
+
** Shipped M5, still working some p2 issues
* Next round of FEEP coming up - discussed pro and cons
+
** RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates
* Dani: busy week for the team: Mars.2 (4.5.2) RC2 and Neon (4.6) M5 due this Friday - on track
+
** Discussion about the incubation for Java.  Ongoing thread in jdt-dev list https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00964.html.  The incubation features will be part of the release specification which implies they need to be implemented to be compliant.  Spend time putting them into a release only to pull out later if they don’t finalize.  Not clear there are tests added to the TCK.  Alex asks if this effects us for Java 10, no not for Java 10.  Java 10 only has local type reference, not huge delta of function from Java 9.  No incubation in Java 10.  But incubation may affect us for Java 11.
 +
* Info about infrastructure (Alex)
 +
** Foundation push to move to Jenkins.  Releng has moved, uncovered issues with rest API and token exchange … disabled for now for Jenkins.  Issue is being worked but only can be fixed once all is moved to Jenkins.
 +
** Platform HIPP moving to Jenkins tomorrow.  Will be some downtime, should be less than an hour or so.  May cause several issue.  Issues in non-standard jobs with multiple repos etc.  For Gerrit verifications should be fine.  Let Alex know if there are issues.  Alex to send a note when the migration occurs.
 +
** p2 issue is real.  Other issues are pressing (infrastucture/build).  Todor has a bug that he should be looking at.  Not something happening in the past, but now the capabilities are being resolved.  Issues happened with a hand crafted p2.inf file.  Hopefully will scope down the p2.inf files.  Alex to drive to determine if a respin is needed.
 +
** Need to monitor the p2 issue, determine how many are broken.  Cannot just break 100s of folks without serious consideration.  Why not revert?  Alex says it is not an option and we should do everything possible to fix.
 +
** Lars asks about nominating more committers, perhaps that were rejected in the past.  Now the Eclipse PMC can overlook the nomination process.  Work with existing contributors showing interest and look for opportunities to sponsor them for committership.
 +
* Tip of the day (Clippy)
 +
** See [https://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg08006.html Tips Framework]
 +
** Tip of the Day or (Clippy) in coming contribution … looking for integration M6?
 +
** Lars thinks it is worth it.  Dani disables such things by default, and also Lars. Alex find the function interesting.  Others are also reviewing the patch. 
 +
** Lars is moving forward with it.  If it is very easy to disable and is stable on all platforms then it should be good.
 +
** Is there a concern about a solution that requires network … it doesn’t appear to be a concern.
  
<hr/>
 
'''January 19, 2016''' - Dani, Alex, Martin
 
* Upstaffing PMC - meet next week
 
* Update Eclipse PMC representation on the AC
 
** Since only Alex will represent the Eclipse PMC at EclipseCon, should push for not making formal decisions unless there is remote attendance support
 
* Dani: {{bug|485429}} '''PDE Build''' - looks like a lot of people still use it; OK if moving to a different component, but there's still a dependency:
 
** Plugin or feature export still needs PDE Build -- Whoever wants to remove it, will need to implement a replacement '''in the Platform'''
 
** Alex: Platform build currently does double bootstrapping Tycho already ... making this more complex would be a problem
 
** Introducing other build system into the Platform would be a wrong approach
 
** Will go ahead with what we have for 4.6
 
* Alex: As of today's GTK3 build, Eclipse is working fine on Wayland :) thanks to a number of fixes in GTK
 
** Some GTK developers are now considering Eclipse as part of their regression suite :)
 
* SWT move to Java 7 was much appreciated; moving forward, how to deal with functional interfaces ?
 
* Alex would be interested in some styling support in SWT - would simplify some things, at least on GTK
 
** Could be a very simple API like setStyle(String) - win32 also seems to have some styling support
 
* Martin: '''Stability of GTK3 on Mars.2 ?'''
 
** Alex: Many distros do their own hacks, so hard to tell... Mars.2 should be stable on every distro that has a stable GTK3 distro without too many patches
 
** Can't recommend GTK3 on Ubuntu yet; few things improved lately, but still causes troubles whenever Ubuntu updates their GTK, requires more fixes in SWT; Kubunutu and derivatives might be even worse
 
*** Good news is that GTK3.16 dropped support for custom theming engines - causes some ugliness but at least it's stable
 
** Debian or SuSE should be OK;
 
** Expect Neon GTK3 to be more stable everywhere than GTK2
 
  
<hr/>
+
'''January 16, 2018''' - Alex, Lars, Dani, Tom
'''January 12, 2016''' - McQ, Dani, Alex, Martin
+
* Native builds at eclipse.org status (Lars):
* Dani: '''Upstaffing the PMC'''
+
** Dani: swt is done for some time already
** Considering "one-time invitation" to get to know candidates better; not so comfortable with a "trial period"
+
** Dani: launchers after M5 is released to prevent breakage
* Dani: '''Remove Kim Moir from Platform Releng''' - ideally talk to Kim before moving forward
+
* GTK launcher changes (Alex):
* Dani: {{bug|485429}} '''Remove PDE Build from our drops?'''
+
** Changes to not rely on X11 atoms but on dbus ready for review
** Removing PDE Build is one thing - adding a different technology would be wrong, as wrong as adding EGit
+
** Linux only as no other GTK platforms are currently built
** McQ and Dani will reach out inside IBM;
+
* Equinox CQs (Tom):
** Patches are still being submitted; middle ground would be remove from the delivery but keep in repo (and deprecate since not adding features)
+
** P2 capabilities patch from Todor and felix.scr update
* Dani: {{bug|485257}} '''Copyright Policy Change''' - waiting on EMO/Legal input
+
** Slow process risking M5
* Alex: '''Updating SWT to Java7'''
+
** Alex: Ping Sharon asking for speedup if possible
* McQ: '''Travel for EclipseCon'''
+
* Updates from Dani:
 +
** Photon plan update - BREE to be part of the build info
 +
** End game - Oxygen.3 and M5 - send to the list
 +
** Running tests against Java 9
 +
* Java 10 eclipse release (Dani):
 +
** Oxygen.3a or marketplace feature only - Agreement for oxygen.3a
 +
** Dani: Local Variable type inference support in a branch
 +
** Future releases - to be aligned with JVM releases if they prove to release on time
 +
* BREE updates recomendations
 +
** Dani: There are reasons to stay on older BREE
 +
** Alex: ease of getting jvm is the main concern here - if a contributor can't get jvm at that version easily we can't call it supported
  
<hr/>
 
'''January 5, 2016''' - McQ, Dani
 
* Dani: '''PMC Membership'''
 
  
<hr/>
+
'''Januar 09, 2018''' - McQ, Alex, Lars, Dani
 +
* Updates from Dani:
 +
** Ian Skerrett is leaving the Eclipse foundation
 +
** Dani got nominated as committer representive
 +
* Planning council update
 +
** Dani: low participation in the last calls
 +
** Dani will talk with Melanie about it
 +
** Input  required for the planning council for the API and feature freezes for the platform
 +
* API and feature freeze policy in platform
 +
*** Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build
 +
*** everyone agrees to Alex suggestion-> agreed
 +
* Alex: SWT linux currently uses X-Windows specific API, which does not work on Wayland. This will be moved to a DBUS API to open file and open URL
 +
* Dani: Plan update, biggest change is for the component plan
 +
** Equinox plan has been added
 +
** Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build
 +
* Launcher and natives build move from IBM to the foundation still in progress
 +
** ({{bug|528230}}) Build FileSystem native component on Eclipse Foundation Infra
 +
** ({{bug|528230}}) Build launcher on Eclipse Foundation Infra
  
 
= Archive =
 
= Archive =
 +
* [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]]
 +
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]
 
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]

Revision as of 11:15, 12 June 2018

Documents

Some documents written and/or used by the PMC:

Meeting Schedule

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

Meeting Minutes

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

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

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

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


May 29, 2018 - Alex, Tom, Dani

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


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

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


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

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


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

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


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


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

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


April 17, 2018 - Dani, Alex, McQ

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


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

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


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

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


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

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

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

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


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

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


March 13, 2018 - Dani, McQ, Tom

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


March 6, 2018 - McQ, Tom, Alex

  • Short call without any interesting topics


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

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


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

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

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

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


February 6, 2018 - Lars, Dani, McQ

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


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

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


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

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


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

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

Archive

Back to the top