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"

(132 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
= Documents =
 
= Documents =
 
 
Some documents written and/or used by the PMC:
 
Some documents written and/or used by the PMC:
  
Line 8: Line 7:
 
= Meeting Schedule =
 
= Meeting Schedule =
  
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every Wednesday at 10.30am EST'''.
+
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every Tuesday at 11.00am EST'''.
  
 
= Meeting Minutes =
 
= Meeting Minutes =
'''October 14, 2015''' - McQ, John, Alex, Dani
 
* Dani: Community asked to move platform.text into platform.ui (see [https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html])
 
** 3 solutions:
 
*** make the move
 
*** make a more radical move to merge everything into 'Platform'
 
*** leave things as is and let new people join platform.text
 
** McQ: merging everything together is not an option. Skills are too different. Resources, Debug and SWT need to be kept separate.
 
** Dani: fine with the move as long as it does not serve as argument to merge everything into one pot
 
** Alex: committers need to accept the move
 
** PMC decision: OK with the move but Dani to ask the platform.text and platform.ui committers whether they are both OK with it.
 
  
* John from Board Meeting: Eclipse Foundation wants to change perception that Eclipse is just an IDE. Therefore they would like to change the name of our project ("Eclipse").
+
'''Apr 25, 2017''' - Dani, Alex, Martin
** McQ:
+
* Dani: '''Neon.3a'''
*** this will not be for free. The name is used at many places (code, webpage, Help) and also by companies in their marketing
+
** Respin done -- problem: Updating from Neon.3 to Neon.3a , the problematic bundles are not removed
*** maybe we just have to accept we made a mistake in the beginning and now live with it
+
*** '''AI Alex''' tell Jeff to ask Pascal or Tom about how to disable the bundles on update
*** can't think of a good name - which indicates we shouldn't change it ("Platform" is not good and "Eclipse SDK" or "Eclipse IDE" hide that it is the base for "RCP" apps)
+
*** Martin: If this problem can't be resolved could live with it ... better not take too much risk trying to resolve this very special problem
** decided to talk about this again in the next call
+
  
 
<hr/>
 
<hr/>
 
+
'''Apr 18, 2017''' - Dani, Lars, Martin, Alex, McQ
'''October 7, 2015''' - McQ, John, Alex, Dani, Martin
+
* Dani: '''RH and Java9 Jigsaw'''
* Dani: '''{{bug|108668}} Default Text Encoding UTF-8 ?'''
+
** Very good write-up linked from the [https://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg03385.html AC Mailinglist] - see also [https://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg03389.html follow-up]
** On Linux and Mac, the Platform encoding is UTF-8 ; on Windows it's Cp1252 in most countries around the globe, even with Windows 10
+
** Eclipse JDT team concerns that the Spec is not complete brought forward to Wayne
** Using the Platform encoding ensures interoperability with all local tools (editors, compilers, ...)
+
* Dani: '''Neon.3 Respin'''
*** '''Desire for UTF-8 only for Windows exchanging files with users on other systems'''
+
** Last action was with Ed Merks to validate that the Fix from Tom Watson actually works - no update so far
*** '''Changing the encoding of an existing workspace after the fact is a no go''' (risk of data corruption when loading/saving a file, some encodings are lossy)
+
* Lars: '''[https://marketplace.eclipse.org/content/glance#group-details Glance] Migration''' to e4 and/or Platform
*** '''Using an encoding different than the OS encoding is problematic too''' (risk of data corruption when importing or D&D files from the OS)
+
** e4 incubator was always intended to have very low entry barrier - can give the Glance team access quickly
** Proposal 1: UTF-8 on new empty workspaces on Windows ? --&gt; Might mean that external tools don't work as expected
+
* Lars
** Proposal 2: Make users aware (Restore Oomph Welcome, which was disabled via {{bug|459486}}) ? --&gt; But many users don't understand implications, other tools also don't do this
+
** JUnit 5 licensing - EPL + Apache
** Proposal 3: Ask for encoding when team-sharing since only team-shared projects cause issues (eg EGit hook) ? --&gt; But on "push" it may be too late
+
** Martin: Encoding describes content, so should be managed with the content (as a project setting)
+
*** '''--&gt; Proposal 4: Move to a model where we encourage setting the project-level encoding preference'''
+
**** When creating a project, set the workspace default on project level automatically --&gt; ensures that projects remain sane over their lifetime
+
**** For projects lacking the project-level preference, introduce a Problem Marker (Warning) with quick fix to either UTF-8 or workspace default
+
** '''Decision:'''
+
*** '''We won't change the workspace default''' -- no use breaking existing users
+
*** '''We'll set the project encoding pro-actively'''
+
** Open questions:
+
*** Do we need tooling to convert project from encoding A to encoding B (if project preference was set incorrectly initially) ?
+
*** Shall we try setting source encoding on drag-and-drop, or shall the project dictate the policy ?
+
  
 
<hr/>
 
<hr/>
'''September 30, 2015''' - McQ, John, Alex, Dani
+
'''Apr 11, 2017''' - McQ, Lars, Alex, Dani
* Dani: will send a note to PMC list asking to approve new Debug leadership (Sarika)
+
* Dani: Update from last Planning Council call:
* Dani: we should finalize our API removal discussion from last week
+
** There will be a special drop for Java 9 in July, but it has not yet been decided whether it will be a release where users automatically get the update, or a special p2 repository or Marketplace entry where the update can be done on demand.
** agreed that APIs marked for removal have to be annotated with @noreference, @noextend and @noimplement
+
** Issues with Neon.3. A respin might be necessary. For details see https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02741.html.
** agreed that components should be allowed to remove API but they have to provide good reasons
+
* Dani: Asked Lars to review the Dark theme bug. Lars, said, he's not a user of it, but has one in his team. Dani: Ask him to review the change.
** agreed that we won't allow to delete APIs simply because they are deprecated
+
** agreed that the PMC will decide case by case i.e. there will be no general rule
+
** regarding version numbering we decided to also decide this case by case
+
** Dani to update the removal document and have it reviewed by the PMC
+
  
 
<hr/>
 
<hr/>
 
+
'''Apr 04, 2017''' - Dani, Martin, Alex
'''September 23, 2015''' - Dani, John, Alex, Martin
+
* Martin: {{bug|514257}} and [https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14316.html cross-project Neon.3 wiring issue]
* Dani: '''JDT Core''' - Co-lead going to step up
+
** Problem: External libs don't deal with versions the same way we do
* Dani: '''API Removal Discussion'''
+
** Dani thinks that the problem is that Release Train projects don't agree on one version to use
** Q1: When do we actually delete API? What's the benefit compared to the pain that we cause ?
+
** Martin saw a similar problem related to some bundles doing import-package and others doing require-bundle:
*** Example of methods that don't do anything any more or do wrong things -- those should be removed
+
*** Commons Logging is not a Singleton
*** Example TableTreeViewer : Continue having the API doesn't hurt, there's no significant benefit removing it
+
** Dani has a call with Tom later today; hoping a respin can be done after fixing in Equinox
**** Alex: TableTree was completely broken on GTK for 2-3 years ... keeping such components that don't work properly lowers the quality
+
* Dani: Heads up on upcoming Planning Council discussion re: Java 9 and Junit 5
**** Dani: Is there actual proof of bugs ? Or could it be working fine on Windows RCP ? If it's deprecated, people use it at own risk; do we really need to break them, if it provides value to some people on some Platforms ?
+
* Dani: '''PPC''' - No response on McQ's message regarding PPC, Dani will update the Plan after another week
**** John: In TableTreeViewer case, EMF had some generic code (was unclear if the path was ever taken) and CDT could update easily
+
*** '''Summary''': scheduling for removal is OK with good arguments. Give Adopters a chance to respond before removal takes place.
+
 
+
** Q2: '''How to deal with the versions?'''
+
*** Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
+
**** Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
+
**** For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
+
**** Plugins who don't care recompiling may have to live with ClassNotFoundException
+
**** Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
+
*** '''Summary:''' Handle the Major with care -- in most cases, the cost of updating the major is not justified by the benefit.
+
 
+
** John: '''Announcement''' When thinking about removing something, we should announce that far and wide and ask for feedback
+
*** Martin: But which channel is as effective as actually removing it ? There's always who don't actually listen...
+
*** John: Still, giving a possibility to listen is important. Agree that mentioning in the release docs is not enough.
+
*** Dani: When making a release, also send message with a link to the removals page (for all removals that are planned)
+
** John: Mechanisms for maintaining binary compatibility while only breaking source compatibility (but it's a lot of work!)
+
*** Dani: Agree, in this case better just leave it in there
+
 
+
** Alex: What to do next time, can we remove more stuff ?
+
*** Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
+
 
+
** John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
+
*** Eg release but without all the deprecated at certain well-known point in time eg every 3-5 years
+
*** '''AI''' ''continue that discussion on the Architecture Council''
+
 
+
** '''Summary:''' Essentially do what we did, plus more communication upfront, allow people to respond before deletion happens (to avoid churn)
+
*** Committers still need to be able to delete stuff when they find it necessary.
+
*** Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
+
 
+
* Alex: '''Bumping the minimum GTK version again''' (may cause issues on Platforms like AIX -- to be discussed when it's time)
+
 
+
  
 
<hr/>
 
<hr/>
'''September 16, 2015''' - John, Martin
+
'''Mar 28, 2017''' - McQ, Alex, Lars, Dani
* John: '''API Removal Discussion'''
+
* Replacement for Sergey
** No urgency now -- changes have been reverted for now, and scheduled for 2017
+
** let's wait and see how things go
** Updating the major of a bundle knowingly breaks everyone/most adopters
+
** next candidate would be Tom Watson once Equinox is moved back to the Eclipse top-level project
*** In the past, breaking changes have often been small enough to work without increasing the major
+
* Dani: PPC strategy: drop 32-bit, provide 64-bit with Oxygen (4.7) and drop 64-bit BE with Photon (4.8)
*** One can argue that removing TableTreeViewer is big enough to warrant updating the major
+
** all agree
** Versioning packages has not been done in the past due to the huge upcoming maintenance effort when starting to do so
+
** McQ will send a note to cross-project-issues-dev
** "Release Version" is decoupled from "bundle versions" already (and may move to date-based versions eg "2016.1" with rolling updates moving forward
+
* Lars will nominate Mikaël Barbero for Platform UI
** --&gt; will have more discussion next week
+
* Lars plans to bring a IDE search plug-in to e4 (http://ystrot.github.io/glance/)
  
 
<hr/>
 
<hr/>
'''September 9, 2015''' - Dani, Alex, Martin, John, McQ
+
'''Mar 21, 2017''' - Dani, Martin, Alex
* John: '''Planning Council Updates'''
+
* Dani: '''Dirk Fauth''' [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02891.html Requests on eclipse-pmc]
** 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
+
** Alex agrees with Dani
** Mid December rather than end to avoid churn, so this one is a little shorter
+
** Where does the "0.x version before graduation" requirement come from? - Development Process, but maybe didn't apply to plugin versions
** Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
+
** Dani thinks that forcing a 0.x version causes forced breakage once something goes API thus doesn't make much sense
** McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
+
* Dani: '''Szymon Ptasiewicz'''
 
+
* Software is getting more important - would be good to better support multicore
+
 
+
* John: '''IntelliJ change in licensing / sales model'''
+
** Many eclipse-positive comments on the announcement blog
+
** Possibility putting Money on Eclipse Development may become interesting for companies in this context
+
  
 
<hr/>
 
<hr/>
'''September 2, 2015''' - Dani, Alex, Martin, John
+
'''Mar 14, 2017''' - Dani, Martin, Alex
* Dani: '''EclipseDay India''' on Saturday, 200 attendees wanted to join, hat to cut to 150
+
* Dani: '''Java 9 readiness''' - see [https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev cross-project-issues-dev]
** Keynote by Mike Milinkovich - large Community
+
** Step 1: For testing, just download a Java 9 beta JVM, add the module -- all testing is possible from commandline
 
+
*** Platform team has an install, but Mike was concerned about legal issues - a bug is open to allow all simrel access
* Dani: '''Policy for and Mars.2'''
+
** Step 2: Running the JDeps tools as per the [[Java 9 Readiness]] wiki can show violations
** Do we want to stick to the "Service" model or allow feature updates ?
+
*** Can even run with Java 8, Dani ran it on simrel, it's looking mostly good, only Orbit shows violations
** Mars.1 winding down -- sticking to "Critical Fixes Only" for that
+
*** Platform team has some scripts; for Hudson there's even a Mojo, but it aborts when it finds a violation.
** Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
+
** Step 3: Reflection - Will only figure out when knowing the code or testing
** Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
+
** All these 3 tests can be done without the Java 9 patch in PDE. Only for debugging, one needs to self-host.
*** Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
+
*** This can be done either with Ed's Oomph support, or via the Marketplace
*** Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed
+
** Platform team is still negotiating options for better support with Oracle
 
+
* Dani: '''JUnit 5''' considers cutting down features for aligning with Oxygen
'''August 26, 2015''' -
+
** Decision to align, contributing support to Oxygen Update 1 in September
* Dani/Alex/Martin can't join (traveling)
+
* Dani: '''2 Platform Issues in M6'''
 +
** platform.ui reexports everything including jface - lower bundles not updated - JDT may fail if installed (fixed for M7)
 +
** major version uprev: interface not marked as @noimplement; reverting the version, people who loaded Friday's M6 would never get any updates any more; decision to stick to the version uprev, since the respective bundle is not used a lot
 +
*** In general, accidental major version uprev should be reverted because the error would stay around for long and might break existing binary bundles who can't be fixed any more
 +
*** In this case, it was OK to keep since the bundle isn't used much
 +
* Alex: '''Generic Editor and Testing'''
 +
** Looking very good already - only 1/3 of the code needed for getting the same feature set as with existing methods for creating editors
 +
** Looking for features to add missing documentation (workflows, use-cases like converting existing editors): End goal is to provide everything that the JDT Editor is providing
 +
** Dani: Likes replacement of pages on multipage editors, and some new editors; would not consider replacing the JDT editor
 +
** In the Platform.ISV docs bundle, there should be a section for "how to write your own editor"
  
 
<hr/>
 
<hr/>
'''August 19, 2015''' - Alex, Dani
+
'''Mar 7, 2017''' - Dani, Martin, Alex, Sergey, Lars
* nothing to discuss
+
* Dani: '''4.6.3 Updates''' - Looking good, Equinox bugs moved out by Tom
 +
* Dani: '''4.7M7 Update''' - Infrastructure issues but testing looks OK (except Mac which is not built yet)
 +
* Dani: '''Java 9 / Planning Council Update''' - Postponing Oxygen was discussed but denied; late July update being considered
 +
** See the [https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/ eclipse.org-planning-council archives]
 +
* Lars: '''Platform.Resources Leadership''' after Sergey Leaving
 +
** Dani pinged Szymon, will continue discussion when we hear back; merging with platform.ui is one option
 +
** Sergey: The "Team" and "Resources/Filesystem" parts could be considered separately. Consider merging Team into UI.
 +
** Alex: One top Platform Project would make sense now...
 +
** Dani: reconsider when McQ is back. In the past, SWT was seen as separate.
 +
** Dani: Releng needs to be separate and protected because Releng committers can also change Hudson jobs, shut down servers etc where no history is kept
  
 
<hr/>
 
<hr/>
'''August 12, 2015''' - John, Dani
+
'''Feb 28, 2017''' - Sergey, Alex, Martin, McQ
* John asked whether we run on Windows 10
+
* Alex: '''Short update on Neon.3'''
** Dani: yes, the team already tested on it a few weeks ago. Runs smoothly one bug so far. Browser widget works despite new browser (Edge)
+
** 2 jdt.core bugs asking for PMC approval - regressions compared to Neon.2, approved
** ''Martin (added after the meeting): A CDT update is needed to keep the Terminal from hanging (see {{bug|474327}}, will release with Mars.1). Got some duplicates already. Workaround is switch the Win10 Console to "Legacy Mode".''
+
** PPC rebuild is in, so looking good
* Dani would like to get plan feedback by Friday EOD
+
* Sergey will leave Eclipse work after end of March
 +
* Martin: '''RCPTT / Reddeer / Testing'''
 +
** Reddeer: No tests that check Platform only - everything is on higher level today (WTP, server connectors etc)
 +
** Runs on Neon.2 right now inside RH - the infrastructure isn't built for consuming daily builds
 +
** Would take some effort reducing to Platform only - no time for this in the RH team at the moment
 +
** '''AI Martin''' will look at integrating RCPTT as time permits; would like {{bug|505826}} resolved ideally
 +
* McQ will be out next 2 weeks
  
 
<hr/>
 
<hr/>
'''August 5, 2015''' - McQ, John, Dani, Alex, Martin
+
'''Feb 21, 2017''' - Dani, Alex, Martin, Lars, Sergey
* PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
+
* Lars: {{Bug|512273}} Allow any committer to retrigger Gerrit validation, and {{Bug|512319}} allow rebase
** adding another release before Christmas might be a next step - even if Platform contributes identical bits
+
** '''Agreement''' to allow retrigger for anyone, but rebase should be done by committers working on a contribution
 
+
** Dani: Not clear where to retrigger (Sergey: it's discoverable once permission is there)
* Dani: '''[[Eclipse/Mars Retrospective]]'''
+
** '''AI Lars''' follow up on the bug
** Move more components to Tycho build? (Would still need Ant to test against final build/bits)
+
* Martin: '''UI Testing'''
** Contribution Review Dates: joined by some components but not all
+
** [http://eclipse.org/rcptt RCPTT] is completely Open Source; commercial server could be used for load balancing tests but this is not necessary
** Error Reporter: Interesting to look at top ten but the sheer number is too big
+
** Alex: Interested in Reddeer for upstreaming tests that already exist at RH; good reports about stability and scalability at RH
*** John - based on Orion experience with similar error reporting :  
+
** When we decide which way we go, we need a plan who's doing the work (create the tests). Maintenance would depend on their structure.
**** Looking at changes in reported issues is more interesting than looking at reports themselves
+
** Some Reddeer tests already upstreamed with WTP and Linuxtools
**** Reports help getting contributions (But, Dani finds that "just adding a null check" is often not what's desired for Java .. though helpful for Javascript)
+
** Lars: Where would the tests live? - In a common project accessible to all, or with the component they test ?
 
+
*** Lars, Dani: Since these are functional end-to-end, should live in their own repository, accessible by all committers.
* Dani: Foundation IP team doesn't require updating copyright notices per contribution any more (since that information is in git anyways)
+
** '''AI Martin''' follow-up with Jubula. Try RCPTT on Windows and Linux. Give feedback till next week.
** The Project has to agree
+
** '''AI Alex''' share list of Reddeer tests existing at RH
** Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
+
** '''AI Lars''' play with the Reddeer API
** Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
+
* Dani: '''Update on PPC''' drop 32-bit, build 64-bit both le and be on RH VMs {{bug|512224}}
** Dani to sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02422.html request for voting]
+
** Alex: ppc64 currently built on Fedora 25; could build on REL7 if foundation requests a machine from RH Brno Farm '''AI Alex and Dani''' ask Denis
 
+
* Dani: '''Neon.3 RC3''' please keep an eye on builds
* Dani: Switching to '''Jetty 9.3.x (which requires JRE 8)'''
+
* Dani: Away this Friday afternoon and whole next week
** JRE 8 from Oracle (and also from IBM) exists for all Reference Platforms
+
** Except Solaris, because we only support Solaris 32-bit and the JRE only exists as 64-bit
+
** But the Plan for Neon is to have 64-bit Solaris support
+
** New Language features in Java 8 are adopted, contributors would like to start using Java 8
+
** McQ: In the past, staying on older Java was desired to enable more widespread use ... today, this argument does not seem valid any more, in fact likely more contributions / community is enabled by moving to Java 8
+
** Dani: Only concern is some "non reference" Platforms like HP-UX might not have JREs initially; but that's OK as long as the reference platforms are good
+
** '''AGREEMENT''' to move to JRE 8 and allow projects to use Java 8 in their code.
+
 
+
* Dani: Looking for a contributor for SWT improvements for GTK3
+
 
+
* Martin: '''libwebkitgtk-3 on Ubuntu 14 forcing GTK 2''' not working ?
+
** Alex: Using libwebkitgtk-4 which is much more stable, but not implementing the full SWT API
+
** Most distros don't ship libwebkit for gtk-2 any more since it's not supported upstream any more and has many security issues
+
 
+
* Alex: '''Build SWT at the Foundation'''
+
** Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month
+
 
+
  
 
<hr/>
 
<hr/>
'''July 15, 22 and 29, 2015''' -- no meeting
+
'''Feb 15, 2017'''
  
 
<hr/>
 
<hr/>
'''July 8, 2015''' - McQ, Dani, John, Martin, Alex
+
'''Feb 8, 2017''' - Dani, Alex, Martin, Lars
* John: '''Cross-Language Tooling Discussion''' on the eclipse.org-architecture-council and ide-dev mailing lists
+
* Dani: '''{{bug|509412}}''' - Adopt newer JSch for Platform 4.6.3
* decided to cancel the upcoming July meetings
+
** Alex is fully consumed with Webkit work for Oxygen
 +
** 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'''
 +
** Dirk from 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)
  
 
<hr/>
 
<hr/>
'''July 1, 2015''' -- no meeting
+
<strike>Feb 1, 2017 - cancelled</strike>
 
+
 
<hr/>
 
<hr/>
'''June 24, 2015''' - McQ, Dani, Martin, Alex
 
* Dani: '''Java 9''' - <a href="http://marketplace.eclipse.org/content/eclipse-java%E2%84%A2-9-support-beta-mars">EAR Feature Patch</a> on the Marketplace NOW
 
** No JARs any more - JRE is doing things internally using "jimage" format; updated search etc to create projects and work against them
 
** If the Jimage filesystem provider isn't backported, one has to run the IDE on Java9 in order to code Java9
 
** Modules are just a list of packages (and can refer to other modules) - no real JSR describing the plan yet - seems like just a replacement of "Profiles" (and JARs)
 
  
<hr/>
+
'''Jan 24, 2017''' - Dani, Lars, Martin, Alex
'''June 17, 2015''' - Dani, John, Martin, Alex
+
* Dani: '''New Jetty Version''' - Alex will look at it after FOSDEM (Feb 7)
* John: '''Mars''' Platform in good shape for Mars - EPP respin for Error Reporting
+
* Dani: '''javax.xml''' - Plan to announce removal from the feature on cross-project for M6
* Dani: '''Crashes with Java 8''' - Potentially will add to the online README
+
** Cannot remove from the compile prerequisites, because plugins still on Java 5 need it
** Happens in the JIT, with latest Oracle Java 8 (with 8 Cores and very specific circumstances)
+
* Alex: '''[http://jboss-reddeer.github.io/reddeer/ Reddeer Testing Framework]'''  
** See {{Bug|465693}} - Probably https://bugs.openjdk.java.net/browse/JDK-8078262
+
** JBoss Tools uses Reddeer for overall user story validation
* Alex: '''XDG Application''' - looks like Docker but a similar idea
+
** Lars: Why wasn't the framework added to SWTBot? -  
** Environment description of the runtime - helps specifying the line-up of library versions that we test against and use
+
*** Reddeer is not a framework, it's meant as a test harness library - smaller scope than SWTBot or Jubula
** Big part of GNOME / GTK already pushing for it, might make sense to consider alignment
+
*** API Stability across multiple Eclipse versions is out of scope, thus created outside Eclipse for now
** GNOME working towards compiling with a really old compiler, such that the physically identical bits can run against a large set of distros
+
** Martin: Any improvements in object recognition compared to plain SWTBot?
** See https://wiki.gnome.org/Projects/SandboxedApps
+
*** 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
** But if you want to try it out please read https://blogs.gnome.org/alexl/2015/06/17/testing-rawhide-apps-using-xdg-app/  
+
*** 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/>
+
<hr>
 
+
'''Jan 17, 2017''' - Dani, Sergey, Alex, Lars, Martin, McQ
'''June 10, 2015''' - Dani, Alex, Martin
+
* Sergey: '''Merging platform.resources with platform.ui'''
* Dani: 4.5RC4 looking good, no more fixes planned
+
** 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)
* Dani: Working on Java 9 feature patch
+
*** Opening up to Platform UI would encourage more people to actually contribute to resources. Strive for shared access on components that are interrelated
* Alex: PC discussing a change in the release train
+
** Dani: Merging into platform.ui would mean making Dani and Lars the leaders for signoff - that causes too much burden
** Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
+
** Sergey: Platform/Team has actually more synergy with Platform/UI than resources
** From Platform point of view, stability is key. Some key contributors not interested doing
+
** Alex: For gcc for example, there is a notion of "maintainers" per git repo for signoffs - that's independent of leadership or commit rights
** Martin: How to also cater to contributors who want their contributions released soon ?
+
*** McQ: Not sure how adding another role would simplify things ?
*** Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
+
** Sergey: The problem for signoffs is not is much the volume of commits, but the volume of failing tests
*** Or, open up a new "experimental" stream ?
+
** 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
*** Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
+
** 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 ?
* Martin: Tested eclipse-installer (Oomph), looking really really good now
+
** McQ: Propose applying the recent simplification of gaining commit rights (for "known" committers)
 
+
* Lars: '''Removing javax.xml'''
<hr/>
+
** Was introduced only for very old JRE's , it is part of the JRE now
'''June 3, 2015''' - Alex, Dani, Martin, McQ, John
+
** 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
* Dani: '''Mars Endgame'''
+
** Lars: With javax.annotation, that was solved with smart reexporting
* Dani: Please vote for release review
+
** 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.
<hr/>
+
**'''AI Lars''' send a note to Tom Watson as the submitter.
'''May 20, 2015''' - Dani, Alex, Martin, McQ
+
* Dani: '''Project Updates'''
* Dani: '''Security Update''' - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
+
** Deadlines upcoming for CQs and APIs - see Endgame Plan, please provide feedback
* Dani: '''RC2 Build''' - too many bugs assigned, Lars on Vacation, Dani will fill in
+
* McQ: '''UI Testing and Jubula'''
* McQ: '''Too Many Platforms Built?''' - Who's really hurt by "too many builds" ?
+
** Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).
+
 
+
<hr/>
+
'''May 13, 2015''' - McQ, John, Alex, Martin
+
* John, Dani - Mars Endgame looking good
+
* Alex - {{bug|465874}} Lucene 5 looking good, almost done - Ready to commit as soon as CQs are in and Mars+1 is open
+
* JDT for Java 9 - will need a wider discussion with EMO on make it easier to publish the work, e.g. in normal builds
+
 
+
<hr/>
+
'''May 6, 2015''' - McQ, Dani, Martin, John
+
* Dani: '''Java 9 timing''' - slight delay
+
* Dani: RC1 preps
+
** 2-day test pass went fine - 2 severe issues found, will be addressed
+
** Request to watch PMC mailing list for API exceptions and defect approvals
+
* John: '''PC Discussion on Release Cycles'''
+
** Multiple releases per year PLUS maintenance streams seems like overkill
+
** Consider an approach like Orion that just moves constantly forward
+
** Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
+
*** A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
+
*** Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
+
*** Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?
+
 
+
 
+
'''April 15, 2015''' - Dani, John, McQ, Alex, Martin
+
* Dani: '''Java 1.7 Changes'''
+
** Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
+
** Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
+
*** Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
+
*** Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
+
** Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
+
* Dani: '''Batik 1.6 update'''
+
 
+
<hr/>
+
'''April 8, 2015''' - Dani, Martin, Alex, John, McQ
+
* Dani: '''Batik''' - Platform is good, Train may need to update, perhaps updating one bundle only would suffice. John will follow up.
+
* Alex: '''SWT for GTK 3 News'''
+
** GTK port finally decoupled from X11 - it renders on Wayland now, can switch the renderer to a pure HTML one
+
** This opens up opportunities (but depends on hosts that have GTK).
+
 
+
 
+
<hr/>
+
'''April 1, 2015''' - McQ, Alex, Martin, Dani (Regrets: John travelling)
+
* Alex: '''GTK 3.16''' seeing issues again - fixed some crashes, but scrolling is still entirely broken
+
** SWT uses a number of things that GTK declares as "implementation detail"
+
* PMC approval on piggyback CQ's (AC question forwarded by John)
+
** Dani sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02332.html our position] to John in order to update the AC
+
 
+
<hr/>
+
'''March 18, 2015''' - Dani, Alex, Martin, McQ, John
+
* John: '''EclipseCon''' - Bigger this year due to LocationTech (750 attendees)
+
** Mark Reinhold keynote and "after-session" on Java 9
+
** Much interest in Orion JS tooling / editor, also on desktop
+
** Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
+
* Dani: {{bug|458730}} '''Mars Plan Update'''
+
* Dani: '''e4 project leadership''' approved by EMO
+
* Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list
+
 
+
<hr/>
+
 
+
'''March 11, 2015 - no meeting (EclipseCon)'''
+
 
+
<hr/>
+
 
+
'''March 4, 2015''' - Dani, McQ, Martin, John
+
* Dani: '''e4 leadership''' - Dani will volunteer to co-lead
+
* Dani: '''BREEs''' - documentation about how to pick the EE
+
** Recommending the "earliest generally supported JRE that provides the capabilities you need"
+
** Would like an URL on the page pointing to the most recent plan (talking to Wayne)
+
* John: '''greatfix contest'''
+
** Dani: Working well - some very small contributions but some also very large (eg Customize Perspective fixes)
+
* John: '''EclipseCon''' - numbers looking good; join Planning Council Breakfast as delegate for Dani
+
 
+
<hr/>
+
'''February 25, 2015''' - Dani, Martin McQ
+
* No topics
+
 
+
<hr/>
+
'''February 18, 2015''' - Dani, Alex, Martin
+
* Alex: '''Building Native Launchers'''
+
** Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
+
** Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
+
** Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
+
* Dani: Great initiative, but other (non-EF) builders must not be broken
+
** EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
+
* Alex is willing to spend time to get Linux builds running; but can't help with other architectures
+
** Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
+
* Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
+
** Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
+
** Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
+
 
+
* Alex: '''{{bug|459399}} - Policy for recommended minimum execution environments for bundles'''
+
** Dani: It works today
+
*** To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
+
*** To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
+
** Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
+
*** But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
+
*** Suggested BREE for new bundles has already been changed by Lars
+
* Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
+
* No conclusion so far (Alex and Dani disagree)
+
 
+
* Dani: '''e4 leadership'''
+
** Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier
+
 
+
<hr/>
+
'''February 11, 2015''' - Dani, Alex
+
* no topics
+
 
+
<hr/>
+
 
+
'''February 4, 2015''' - Dani, Alex, Martin
+
* Alex: With GTK-3.15.[345] , Eclipse is entirely unusable
+
** Alex has some dirty workarounds to make it start, but still many issues like trees not painted, ...
+
** Crash on startup identified to be GTK bug. Fix to be released in 3.15.6 https://git.gnome.org/browse/gtk+/commit/?id=edec64cda3d4518b4e87d5ea5d287d4570ba9933
+
* Dani: Working on Solaris 64-bit
+
 
+
<hr/>
+
 
+
'''January 28, 2015''' - Dani, Alex, John
+
* Dani: Switch Mac OS X 10.9 with 10.10 in Mars target environments
+
** No objections
+
* Alex: Looking for any Eclipse related activity @Fosdem
+
<hr/>
+
 
+
'''January 21, 2015''' - Dani, Alex, Martin, McQ
+
* Alex: '''Process for allowing non-committers extended bugzilla privileges (for bug triage)?'''
+
** Dani: Yes a process exists. Send bugzilla username to Dani.
+
* Alex: '''New resource for helping with SWT'''
+
* Dani: '''Platform/UI co-lead'''
+
* Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --&gt; IBM SWT Team considering to invest in getting patches in for 64-bit Solaris
+
 
+
<hr/>
+
'''January 14, 2015''' - Dani, Alex, Martin, McQ, John
+
* Dani: Update on Platform/UI Leadership: Daniel Rolka left IBM and for now has no time to contribute. He stepped down as co-lead and nominated Lars Vogel
+
* Dani: Solaris x86 64-bit support - patches exist, but no machine available. No luck to get one from Oracle or via Eclipse Foundation. We will not support Solaris x86 64-bit unless someone makes a machine available
+
<hr/>
+
  
'''January 7, 2015''' - Dani, Alex, Martin, McQ, John
 
* Dani: '''Platform/UI Leadership'''
 
* John: '''Git security issue''' - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP
 
 
<hr/>
 
<hr/>
 +
'''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
  
 
= Archive =
 
= Archive =
 +
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 +
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]
 
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]

Revision as of 11:21, 25 April 2017

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

Apr 25, 2017 - Dani, Alex, Martin

  • Dani: Neon.3a
    • Respin done -- problem: Updating from Neon.3 to Neon.3a , the problematic bundles are not removed
      • AI Alex tell Jeff to ask Pascal or Tom about how to disable the bundles on update
      • Martin: If this problem can't be resolved could live with it ... better not take too much risk trying to resolve this very special problem

Apr 18, 2017 - Dani, Lars, Martin, Alex, McQ

  • Dani: RH and Java9 Jigsaw
    • Very good write-up linked from the AC Mailinglist - see also follow-up
    • Eclipse JDT team concerns that the Spec is not complete brought forward to Wayne
  • Dani: Neon.3 Respin
    • Last action was with Ed Merks to validate that the Fix from Tom Watson actually works - no update so far
  • Lars: Glance Migration to e4 and/or Platform
    • e4 incubator was always intended to have very low entry barrier - can give the Glance team access quickly
  • Lars
    • JUnit 5 licensing - EPL + Apache

Apr 11, 2017 - McQ, Lars, Alex, Dani

  • Dani: Update from last Planning Council call:
  • Dani: Asked Lars to review the Dark theme bug. Lars, said, he's not a user of it, but has one in his team. Dani: Ask him to review the change.

Apr 04, 2017 - Dani, Martin, Alex

  • Martin: bug 514257 and cross-project Neon.3 wiring issue
    • Problem: External libs don't deal with versions the same way we do
    • Dani thinks that the problem is that Release Train projects don't agree on one version to use
    • Martin saw a similar problem related to some bundles doing import-package and others doing require-bundle:
      • Commons Logging is not a Singleton
    • Dani has a call with Tom later today; hoping a respin can be done after fixing in Equinox
  • Dani: Heads up on upcoming Planning Council discussion re: Java 9 and Junit 5
  • Dani: PPC - No response on McQ's message regarding PPC, Dani will update the Plan after another week

Mar 28, 2017 - McQ, Alex, Lars, Dani

  • Replacement for Sergey
    • let's wait and see how things go
    • next candidate would be Tom Watson once Equinox is moved back to the Eclipse top-level project
  • Dani: PPC strategy: drop 32-bit, provide 64-bit with Oxygen (4.7) and drop 64-bit BE with Photon (4.8)
    • all agree
    • McQ will send a note to cross-project-issues-dev
  • Lars will nominate Mikaël Barbero for Platform UI
  • Lars plans to bring a IDE search plug-in to e4 (http://ystrot.github.io/glance/)

Mar 21, 2017 - Dani, Martin, Alex

  • Dani: Dirk Fauth Requests on eclipse-pmc
    • Alex agrees with Dani
    • Where does the "0.x version before graduation" requirement come from? - Development Process, but maybe didn't apply to plugin versions
    • Dani thinks that forcing a 0.x version causes forced breakage once something goes API thus doesn't make much sense
  • Dani: Szymon Ptasiewicz

Mar 14, 2017 - Dani, Martin, Alex

  • Dani: Java 9 readiness - see cross-project-issues-dev
    • Step 1: For testing, just download a Java 9 beta JVM, add the module -- all testing is possible from commandline
      • Platform team has an install, but Mike was concerned about legal issues - a bug is open to allow all simrel access
    • Step 2: Running the JDeps tools as per the Java 9 Readiness wiki can show violations
      • Can even run with Java 8, Dani ran it on simrel, it's looking mostly good, only Orbit shows violations
      • Platform team has some scripts; for Hudson there's even a Mojo, but it aborts when it finds a violation.
    • Step 3: Reflection - Will only figure out when knowing the code or testing
    • All these 3 tests can be done without the Java 9 patch in PDE. Only for debugging, one needs to self-host.
      • This can be done either with Ed's Oomph support, or via the Marketplace
    • Platform team is still negotiating options for better support with Oracle
  • Dani: JUnit 5 considers cutting down features for aligning with Oxygen
    • Decision to align, contributing support to Oxygen Update 1 in September
  • Dani: 2 Platform Issues in M6
    • platform.ui reexports everything including jface - lower bundles not updated - JDT may fail if installed (fixed for M7)
    • major version uprev: interface not marked as @noimplement; reverting the version, people who loaded Friday's M6 would never get any updates any more; decision to stick to the version uprev, since the respective bundle is not used a lot
      • In general, accidental major version uprev should be reverted because the error would stay around for long and might break existing binary bundles who can't be fixed any more
      • In this case, it was OK to keep since the bundle isn't used much
  • Alex: Generic Editor and Testing
    • Looking very good already - only 1/3 of the code needed for getting the same feature set as with existing methods for creating editors
    • Looking for features to add missing documentation (workflows, use-cases like converting existing editors): End goal is to provide everything that the JDT Editor is providing
    • Dani: Likes replacement of pages on multipage editors, and some new editors; would not consider replacing the JDT editor
    • In the Platform.ISV docs bundle, there should be a section for "how to write your own editor"

Mar 7, 2017 - Dani, Martin, Alex, Sergey, Lars

  • Dani: 4.6.3 Updates - Looking good, Equinox bugs moved out by Tom
  • Dani: 4.7M7 Update - Infrastructure issues but testing looks OK (except Mac which is not built yet)
  • Dani: Java 9 / Planning Council Update - Postponing Oxygen was discussed but denied; late July update being considered
  • Lars: Platform.Resources Leadership after Sergey Leaving
    • Dani pinged Szymon, will continue discussion when we hear back; merging with platform.ui is one option
    • Sergey: The "Team" and "Resources/Filesystem" parts could be considered separately. Consider merging Team into UI.
    • Alex: One top Platform Project would make sense now...
    • Dani: reconsider when McQ is back. In the past, SWT was seen as separate.
    • Dani: Releng needs to be separate and protected because Releng committers can also change Hudson jobs, shut down servers etc where no history is kept

Feb 28, 2017 - Sergey, Alex, Martin, McQ

  • Alex: Short update on Neon.3
    • 2 jdt.core bugs asking for PMC approval - regressions compared to Neon.2, approved
    • PPC rebuild is in, so looking good
  • Sergey will leave Eclipse work after end of March
  • Martin: RCPTT / Reddeer / Testing
    • Reddeer: No tests that check Platform only - everything is on higher level today (WTP, server connectors etc)
    • Runs on Neon.2 right now inside RH - the infrastructure isn't built for consuming daily builds
    • Would take some effort reducing to Platform only - no time for this in the RH team at the moment
    • AI Martin will look at integrating RCPTT as time permits; would like bug 505826 resolved ideally
  • McQ will be out next 2 weeks

Feb 21, 2017 - Dani, Alex, Martin, Lars, Sergey

  • Lars: bug 512273 Allow any committer to retrigger Gerrit validation, and bug 512319 allow rebase
    • Agreement to allow retrigger for anyone, but rebase should be done by committers working on a contribution
    • Dani: Not clear where to retrigger (Sergey: it's discoverable once permission is there)
    • AI Lars follow up on the bug
  • Martin: UI Testing
    • RCPTT is completely Open Source; commercial server could be used for load balancing tests but this is not necessary
    • Alex: Interested in Reddeer for upstreaming tests that already exist at RH; good reports about stability and scalability at RH
    • When we decide which way we go, we need a plan who's doing the work (create the tests). Maintenance would depend on their structure.
    • Some Reddeer tests already upstreamed with WTP and Linuxtools
    • Lars: Where would the tests live? - In a common project accessible to all, or with the component they test ?
      • Lars, Dani: Since these are functional end-to-end, should live in their own repository, accessible by all committers.
    • AI Martin follow-up with Jubula. Try RCPTT on Windows and Linux. Give feedback till next week.
    • AI Alex share list of Reddeer tests existing at RH
    • AI Lars play with the Reddeer API
  • Dani: Update on PPC drop 32-bit, build 64-bit both le and be on RH VMs bug 512224
    • Alex: ppc64 currently built on Fedora 25; could build on REL7 if foundation requests a machine from RH Brno Farm AI Alex and Dani ask Denis
  • Dani: Neon.3 RC3 please keep an eye on builds
  • Dani: Away this Friday afternoon and whole next week

Feb 15, 2017


Feb 8, 2017 - Dani, Alex, Martin, Lars

  • Dani: bug 509412 - Adopt newer JSch for Platform 4.6.3
    • Alex is fully consumed with Webkit work for Oxygen
    • 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
    • Dirk from 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 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 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)

Feb 1, 2017 - cancelled


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

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

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

Archive

Back to the top