Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

(Meeting Minutes)
 
(328 intermediate revisions by 11 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 =
'''September 19, 2012''' - McQ, Martin, John, Andrew, Dani
 
* Martin: Juno patch feature for {{bug|381407}} and {{bug|383890}} ?
 
** This got fixed by a re-spin of RC4
 
* McQ: '''4.x Performance''', and Platform committers
 
** Team is working on issues... like [http://eclipsesource.com/blogs/2012/09/17/so-long-and-thanks-for-all-the-fish/ Jochen Krause's blog]
 
** LTS going to improve things
 
  
<hr/>
+
'''Mar 21, 2017''' - Dani, Martin, Alex
'''September 12, 2012''' - Andrew, Dani, John, Martin
+
* Dani: '''Dirk Fauth''' [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02891.html Requests on eclipse-pmc]
* John: '''CBI Build''' - good progress with Thanh from EMO visiting Platform Team's offices this week
+
** Alex agrees with Dani
** Focus on Juno Stream because LTS builds need to get done
+
** Where does the "0.x version before graduation" requirement come from? - Development Process, but maybe didn't apply to plugin versions
** Can produce an SDK but cannot produce many of the other artifacts (That's good enough for LTS which only needs a p2 repo)
+
** Dani thinks that forcing a 0.x version causes forced breakage once something goes API thus doesn't make much sense
** Can claim readiness only when binary bits are the same (p2 comparator tool from Olivier - which does byte code level compare of class files, and binary comparison of other files)
+
* Dani: '''Szymon Ptasiewicz'''
* John: '''4.x Performance''' - Several people on the team actively looking at issues, some problems identified, some not yet reproduced
+
** Some work started on re-enabling Performance tests
+
** start running on virtual machines to see whether dedicated machines are needed or not
+
** How to improve the process integrating people / resources / donations from companies (EMO pushes towards more contributions)
+
*** Need more committers for longer term, not only short-term patch contributors
+
* Andrew: '''FOSDEM''' Europe (Brussels) coming up - Ian Skerret going to reserve a room, asking for people to join, good conference, lots of cross-pollination
+
  
<hr/>
+
'''Mar 14, 2017''' - Dani, Martin, Alex
'''September 5, 2012''' - Andrew, Dani, Martin
+
* Dani: '''Java 9 readiness''' - see [https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev cross-project-issues-dev]
* Martin: '''Windows 8''' testing ? - Filed {{bug|388560}} to get "Windows 8" added to bugzilla
+
** Step 1: For testing, just download a Java 9 beta JVM, add the module -- all testing is possible from commandline
** Dani: Initial testing by SWT team didn't reveal anything; Dani in favor of getting W8 deployed on Hudson once it is out officially
+
*** Platform team has an install, but Mike was concerned about legal issues - a bug is open to allow all simrel access
** Should consider adding to the Kepler plan; consider backports to Juno SR for issues found
+
** Step 2: Running the JDeps tools as per the [[Java 9 Readiness]] wiki can show violations
* Martin: '''3.8 vs 4.2''' - posting on [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08123.html cross-project list]
+
*** Can even run with Java 8, Dani ran it on simrel, it's looking mostly good, only Orbit shows violations
** Need to look at stack traces in detail eg {{bug|385272}}. Watch how that E-Mail thread evolves.
+
*** Platform team has some scripts; for Hudson there's even a Mojo, but it aborts when it finds a violation.
* Dani: '''Go/No-Go''' decision process for RC's - to be discussed in the Arch call
+
** 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"
  
 
<hr/>
 
<hr/>
'''August 29, 2012:''' - John, Dani, Martin
+
'''Mar 7, 2017''' - Dani, Martin, Alex, Sergey, Lars
* John: Bugzilla's new auto-duplicate-find ... Dani likes it but moved suggestions somewhere else with Greasemonkey to avoid interfering with typing
+
* Dani: '''4.6.3 Updates''' - Looking good, Equinox bugs moved out by Tom
* Tom Watson: Big changes coming in Equinox for Java modularity - thought about Kepler but will wait for another year in a branch
+
* Dani: '''4.7M7 Update''' - Infrastructure issues but testing looks OK (except Mac which is not built yet)
** Java 8 also won't be in Kepler ... so will likely be kind of a Maintenance Release
+
* Dani: '''Java 9 / Planning Council Update''' - Postponing Oxygen was discussed but denied; late July update being considered
* Dani: [[Version Numbering]] document is a bit unclear about upreving from a n.n.2
+
** See the [https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/ eclipse.org-planning-council archives]
** RESOLUTION: desire is clarifying the next is n.n.100
+
* Lars: '''Platform.Resources Leadership''' after Sergey Leaving
* Dani: '''Delete files from CVS projects''' and add a README ?
+
** Dani pinged Szymon, will continue discussion when we hear back; merging with platform.ui is one option
** Yes if it can be done in an automated way .. to avoid confusion about outdated sources
+
** Sergey: The "Team" and "Resources/Filesystem" parts could be considered separately. Consider merging Team into UI.
*** eg README points to a Wiki page
+
** Alex: One top Platform Project would make sense now...
*** John: Keep the .project in place such that jumping from version to version doesn't break a workspace
+
** Dani: reconsider when McQ is back. In the past, SWT was seen as separate.
*** Martin: Acceptance criterion that importing from scmurl in MANIFEST.MF still works (when choosing the tag ... choosing HEAD should bring up the README)
+
** 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
* John: '''Plan Update upcoming'''
+
  
 
<hr/>
 
<hr/>
'''August 15, 2012:''' - John, Dani, Andrew
+
'''Feb 28, 2017''' - Sergey, Alex, Martin, McQ
* Do we support removal of bugzilla CLOSED state? Resolved: yes we do
+
* Alex: '''Short update on Neon.3'''
* Discussion of long term release plans beyond Kepler
+
** 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
  
 
<hr/>
 
<hr/>
'''August 8, 2012:''' - McQ, Dani, Martin, Andrew
+
'''Feb 21, 2017''' - Dani, Alex, Martin, Lars, Sergey
* Dani: News from Jeff
+
* Lars: {{Bug|512273}} Allow any committer to retrigger Gerrit validation, and {{Bug|512319}} allow rebase
* McQ vacation from August 13 to August 31
+
** '''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'''
 +
** [http://eclipse.org/rcptt 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
  
 
<hr/>
 
<hr/>
'''July 25, 2012:'''
+
'''Feb 15, 2017'''
* '''CBI Build'''
+
** For SR1, the build can produce what the Release Train needs ... but not all the extra validation
+
** Need to run both builds for now ... until the CBI team's bytecode verifier produces the same output
+
** CBI team continues to look at the list of diffs and improve their builder
+
** Platform team would be OK dropping the legacy build once the bytecode validator has no diffs
+
** Platform team can't commit more resources to CBI now (Paul Webster already heavily involved)
+
* '''Losing Commits on the Orion git repo'''
+
** Dozen commits or so
+
** Might be a defect in the Orion git tools, but the server side should prevent that !!!
+
** DenyNonFastForward should have protected ... need an extra layer of protection ?
+
  
 
<hr/>
 
<hr/>
'''June 27, 2012:''' - McQ, Dani, Martin, John
+
'''Feb 8, 2017''' - Dani, Alex, Martin, Lars
* Eclipse Demo Camps - none in Ottawa
+
* Dani: '''{{bug|509412}}''' - Adopt newer JSch for Platform 4.6.3
* Going to skip the arch calls for all of July - leave the PMC slot in place.
+
** Alex is fully consumed with Webkit work for Oxygen
* Should keep an eye on the Community feedback for Eclipse 4
+
** 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/>
'''June 13, 2012:''' - McQ, Dani, Martin, John
+
<strike>Feb 1, 2017 - cancelled</strike>
 
+
* Discussed the ECF rebuild request ({{bug|382206}}). Arguments in favor: it is a safe change, it reverts the situation to where it was in RC3 and earlier. Arguments against summarized in https://bugs.eclipse.org/bugs/show_bug.cgi?id=382206#c20.
+
* We will need to tag the release but we can wait until we are officially done (week of June 25th).
+
 
+
 
<hr/>
 
<hr/>
'''June 6, 2012:''' - McQ, Dani, Martin, John, Andrew
 
  
* Discussion of how to handle test failures for final build. Most of the remaining failures are infrastructure issues related to our move to Hudson for tests. We will document the failures through bugs, and include a note on the build results page for the final build explaining the failures
+
'''Jan 24, 2017''' - Dani, Lars, Martin, Alex
* Discussion of whether we need a 3.9 release. Unanimous conclusion was that we do not see a need for it. Reducing to one stream will greatly reduce our development overhead and encourage consolidation around the single stream.
+
* Dani: '''New Jetty Version''' - Alex will look at it after FOSDEM (Feb 7)
* Discussion of how to handle the disappearance of org.eclipse.equinox.concurrent from our RC3 builds. This was never deliberately included in the platform, but was present due to a greedy optional dependency from ECF. By very close 3/2 decision PMC decided to leave it alone and document the disappearance in porting guide, readme file, release review material, and cross-project list.
+
* 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/>
+
<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'''
  
'''May 23, 2012:''' - McQ, Dani, Martin
 
* McQ: '''CBI / Tycho builder''': Paul Webster driving Platform efforts (AI Martin notify about {{bug|359719}})
 
* Martin: {{bug|380984}} ant / Orbit respin? - Unclear for now
 
* McQ: Finally figured out some long-standing bug eg "Variables view sometimes empty"
 
** Dani: It's 2 issues: First-time switch to Perspective deferred to 4.2.1, but {{bug|379818}} is finally fixed
 
** The actual underlying defect had been in there for years
 
 
<hr/>
 
'''May 16, 2012:''' - McQ, John, Dani, Martin
 
* Dani: '''Version Number''' in branding features gets auto-generated and 3.8 version is now higher than 4.2 (since 3.8 build runs after 3.8)
 
** John thinks it's not a big deal
 
* John: '''CBI Patches''' - CBI has lots of patches downstream in their POM's ... RC2 is the last chance getting that in
 
** Auto-generating the POM.XML would be nice but that's not how things work today
 
 
<hr/>
 
'''May 9, 2012:''' - McQ, John, Dani
 
* John: Classic update can still be enabled via capabilities - should we remove it?
 
** Dani: in general "yes", but too late now
 
** McQ: too late, but make sure we do it for Kepler
 
 
<hr/>
 
'''May 2, 2012:''' - McQ, Dani, Martin, Andrew, John
 
* John: '''Forking of SWT''' 3.8 and 4.2 are now separate Streams with CTabFolder implementation being the only difference
 
* Dani: '''Icons''' (not discussed)
 
 
<hr/>
 
'''April 18, 2012:''' - McQ, Dani, Martin, Andrew, John
 
* Martin: [[E4/Scripting]] initiative
 
** McQ thinks the E4 Application Model should be exposed as a DOM to scripting .. anything other than utilizing the e4 DOM for hiding a view feels wrong
 
*** Martin: Approach is very pragmatic - don't see anybody investing into new Frameworks at this point but converging on what already exists
 
*** If this goes towards macro recording, the recorder should utilize the e4 app model
 
** Signing up on the [https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev eclipse-scripting-dev] mailing list will keep people in the loop (expect low volume)
 
* Dani: '''API Approval Process''' Approval on Bug plus sent to eclipse-pmc list (like last year)
 
* John: '''PDE Committers''' - perception of not being open
 
** McQ would like to see a plan item for next year "actively promote more committers from outside"
 
* Martin: [[Asterisk]] - will need a dialin for Dani in Switzerland; '''AI Dani''' forward his dialin to Martin for the time being
 
 
<hr/>
 
'''April 11, 2012:''' - McQ, Dani, Martin, Andrew, John
 
* Martin: '''LTS vs Quality/Fixes in Current Stream''' - Like John's reply making the link between the two
 
* McQ/John: '''Builds''' - Moving forward
 
* McQ: '''CBI Builds''' - Platform not going to take any ownership but will be a consumer like others - still shooting for Juno SR1
 
* Andrew: '''4.2 Builds in Fedora 17''' - Testing now
 
* McQ: '''IBM Ottawa Team moving to new building''' - expect delays during next couple days
 
 
<hr/>
 
'''April 4, 2012:''' - McQ, Dani, Martin, Andrew
 
* Dani: '''VM Requirements''' - Help no longer works on Java 5, this surprised some people... but Project Plan talks about a Java 6 req now
 
** Martin suggestion: on the "Required JVM" table in the Project Plan, add a 2nd column with closure of BREE including all pre-reqs (continue having 1st column the BREE of the bundle itself auto-generated)
 
* Dani: '''Jeff still mentioned as PMC member'''
 
** '''AI Dani''' send E-Mail
 
* Martin: '''Concern about Platform Quality''' - eg SWT Redraws on 3.7.x - Old-time committers moving away
 
** McQ: Platform team's focus will continue being maintenance, and new Platform support ... team's capacity is going down, but SWT is not affected mosted
 
** Martin: Code contributions are easy, hi-quality triage and review are harder
 
** Martin: Re-think the idea of having committers paid by the Foundation and Member Companies paying their share
 
*** Example: Why would Pascal review p2 in his sparetime ... but if he gets paid per bug his experience can be extremely valuable
 
*** Be more creative on resourcing side
 
** McQ: In favor of putting more structure in place similar to LTS ("hire people for fixes") ... just continue with LTS ?
 
*** IBM will have a need for fixes for at least another 8 years .. but that's a very self-serving focus
 
** [[Image:Ok_green.gif]] '''AI Martin''' send E-Mail to Mike to keep the ball rolling
 
* Dani: {{bug|375292}} '''Reference to Marketplace in the SDK'''
 
** Martin: "Classic" is a Building Block but "Packages" are for end users
 
** McQ: The purity of the SDK in itself isn't relevant
 
*** Martin: Why not just create a new package "Classic" which is at +3 and pulls in egit + marketplace ... the process for building is all in place, may just need a package reviewer
 
*** [[Image:Ok_green.gif]] '''AI Martin''' mail Markus
 
 
<hr/>
 
'''March 21, 2012:''' - McQ, Dani, Andrew, Martin
 
* McQ '''Oracle Java on Mac'''
 
* Dani '''denyNonFastForward'''
 
* McQ '''JDT Team might see some losses'''
 
* Andrew '''Running OpenJDK tests now on ARM''' :)
 
 
<hr/>
 
'''March 14, 2012:''' - McQ, Andrew, Dani, John
 
* Losing Eclipse project release engineer next week
 
* David Williams is stepping in to help with our builds until Juno
 
* Most immediate issue is that our build needs elevated privileges to tag, sign, and promote builds
 
** kmoir was the only committer with sufficient privileges
 
** We either need to give another committer sufficient rights, or give build user access it needs
 
** Could use hooks to ensure build user isn't doing anything other than tagging
 
** All agreed the build user approach was the best option. John to open bug against foundation to carry it out
 
 
<hr/>
 
'''March 7, 2012:''' - McQ, Andrew, Martin, John
 
* John: '''API Deletions''' {{bug|370248}} - PMC agrees.
 
* McQ: '''Common Build Infrastructure at the Foundation'''
 
** Shipping Platform Juno bits built by PDE ... but Foundation wants EPP packages built by Tycho; Platform can't support this
 
*** Reason might be that 4.2 is planned to be the start of LTS and VLTS .. ok for now if LTS bits are different since not publicly available
 
*** Plus, LTS really starts after Juno SR2 ... Platform might be in a better position for Tycho by then
 
*** In Linux, Fedora also builds by themselves ... but assumption is that people come to Fedora support first
 
** Martin, Andrew really concerned about fragmentation and duplication of effort ... eg what if the qualifiers don't match
 
** Should be treated as proof of concept but not publicly available until Juno SR2, in order to avoid fragmentation !
 
 
<hr/>
 
'''February 29, 2012:''' - Dani, McQ, John, Martin, Andrew
 
* John: Orion team received a box full of '''Black Ducks''' to honour their Black Duck Rookie of the Year award
 
* Dani: '''Gerrit Move'''
 
** John: Important information needs to stay in Bugzilla ... don't pull from outside git exclusively
 
* Andrew: '''Platform Defect Contest'''
 
** McQ concern: Lots of duplicate bugs would take focus away from the team
 
** Martin: Could encourage triage as part of the contest, and only count good/new bugs
 
** John: Some low-hanging fruit bugs in Platform UI but not necessarily in 4.x ("helpwanted")
 
** John: Re-introduce the "greatbug" keyword ?
 
*** A greatbug is relevant, new, good description that helps understanding/finding the issue; ideally with a patch.
 
*** Resolution: '''AI John''' send note to Mike
 
* John: '''PDE API Moved'''
 
** Some internal, provisional API was migrated to full API in this release
 
** Someone from SAP (Dimitar Giormov) Asked adding back the provisional API such that they could support 2 versions of Eclipse with one codebase
 
** McQ: Would have helped them 4 years ago .. but at the moment don't have enough people
 
*** McQ: Question how pervasive their use of the old API is ... how much Reflection would they need to put int
 
*** One resolution could be OK but only if they provide all the patches
 
** This kind of duplication is error prone and adds a maintenance burden on the project
 
 
<hr/>
 
'''February 22, 2012:''' - Dani, McQ, John, Andrew
 
* Repeat of PDE build discussion from last week. We decided to nominate John Arthorne as a committer so we at least have someone to accept community patches. We will revisit after Juno and perhaps do a larger restructuring
 
* Communication with eGit: We have written some patches for eGit that have been growing stale. Dani will review the patches, and then send an email to eGit lead asking if there is a particular reason for not accepting them. If there is no problem with the patches we will track down an eGit committer to release them.
 
* Andrew asked about process for approving CQs:
 
** Any PMC member can feel free to approve CQs
 
** New versions of existing third party libraries are a no-brainer, typically just +1 right away
 
** For new third party libraries we may need a PMC discussion about why the library is needed, what feature it will live in, etc
 
** For code contributions just make sure the legal process has been followed and then +1. We generally trust the judgement of the committer who will process the contribution.
 
 
<hr/>
 
'''February 15, 2012:''' - Dani, McQ, John
 
* Some discussion of what to do with PDE Build, which lacks committers. PDE as a whole has barely enough committers to be a functioning project, so maybe we should be looking at a larger restructuring after
 
Juno rather than one piece at a time. We lacked quorum to make a decision so we will defer discussion to another week.
 
 
 
<hr/>
 
'''February 8, 2012:''' - Dani, Martin, Andrew, McQ
 
* Andrew: Eclipse stand at '''FOSDEM in Brussles'''
 
** Lots of people just dropped by to say hi and thanks
 
** Mike Milinkovich was showing off Orion; Gunnar and Andrew did others (Web, EclipseRT, C/C++)
 
* McQ: '''4.2 Quality''' ... current list of defects looks manageable to tick all off .. any messaging we want to do ?
 
 
<hr/>
 
'''February 1, 2012:''' - Dani, Martin, John
 
* Dani: '''No UA Committers any more''' - move UA under Platform UI such that at least somebody can apply patches
 
** AI John check with Wayne ... UA is a subcomponent now, may not even need a move review.
 
* Dani: {{bug|343150}} git '''DenyNonFastForward'''
 
** Orion could eventually add tooling to support easy workflows in spite of deny on the repo ... but not in this release
 
** Ping on the bug again and proceed
 
* John: Decide when to switch 4.2 builds from re-using 3.x binary bundles vs full 4.x builds
 
** Today, the 4.x testsuite just tests 4.x specific stuff; things like JDT tests just run against 3.8 today
 
** Today, cannot generate Javadocs in 4.x today sine it needs the full source
 
** Today, nightlies are running 3.x only (could change to running 4.x nightlies only)
 
** Today, 3.x builds run at IBM and 4.x builds run at Eclipse.org
 
** Only few test failures left in the 4.x builds --&gt; ready to switch
 
** AI: '''Kim''' to send 4.x test results to the mailing list, consider switching right after M5
 
** '''Performance Tests:''' Not yet run on 4.x yet - should be able to run on Denis' vserver
 
*** IBM is going to lose the physical machines for performance tests in 2 weeks ! (Going to migrate to vserver too!)
 
*** Need a new baseline
 
** Andrew: at '''FOSSLC''' in Brussels this week, going to represent Eclipse with Mike Milinkovich, Gunnar Wagenknecht and others
 
* '''Gerrit''': Platform won't jump in as an early adopter this time, wait for other projects first
 
** Not all Platform Unittests can run on Hudson today (need at least some fingerprint tests to get value from Gerrit)
 
 
<hr/>
 
'''January 25, 2012:''' - McQ, John, Martin, Andrew, Dani
 
* McQ: '''Note about 4.2 on Release Train'''
 
* Andrew: '''Eclipse 4.2 for Fedora''' - Feature note written for Eclipse Juno led to some discussion at Eng.Steering Committee, but finally approved
 
* Dani: Team down by 1 but no impact (Dani is going to take over responsibilities)
 
* John: '''Build Failures in UA, Update, PDE, p2 yesterday''' after the move to Java 7... nobody watching these, need to find caretakers
 
** UA tests often fail due to a link validity checker, these can be caused by anyone
 
** Certificate Validity issue (Jar signing)
 
 
 
<hr/>
 
'''January 18, 2012:''' - McQ, John, Martin, Andrew, Dani
 
* McQ: '''4.2 quality''' and next steps
 
** More resources found to enable 4.2 as the LTS base - encouraging, although some items still missing
 
** Fedora 17 think about shipping 4.2m6 (work ongoing) - that would be a large stack on top of 4.2
 
** John: '''Oracle Java 7 as Reference Platform''' now that the most severe issues are fixed (Java 6 EOL is June 2012 !) - that is Oracle, not OpenJDK
 
*** Not remove Java 6 for now
 
*** Fedora also does all tests on 7
 
 
<hr/>
 
'''January 11, 2012:''' - McQ, John, Dani, Martin, Andrew
 
* McQ: '''State of Presentation API's'''
 
** Different API's in 4.2 and 3.x -- will need to deprecate API in 3.x
 
** Christian suggested deleting API that's not implemented in 4.x to get compile errors ... John thinks that binary compatibility is more important
 
*** Plugins will be "mostly OK", presentation API is cosmetic anyways
 
** McQ: get in touch with clients who use presentation API, telling them what's best to do ... often newer 4.x infrastructure is much better than trying to keep 3.x around forever
 
* Andrew: '''Cairo and GTK3'''
 
* John: '''4.2 compiling now'''
 
* Martin: '''Updated JSch-0.1.44 version''' - how to announce properly
 
** AI Martin Announce on eclipse-dev and cross-project
 
** Should also put into migrtion notes and README
 
 
<hr/>
 
'''January 4, 2012:''' - McQ, Dani, Martin, Andrew
 
* McQ: Pascal's note about p2 leadership .. not sure who could step in and make a commitment (may see the same fate as UA)
 
** Tom Watson looking for candidates, but looks like none in McQ's team
 
 
<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 2013 | Archive of Meeting Minutes from 2013]]
 +
* [[Eclipse/PMC/Minutes 2012 | Archive of Meeting Minutes from 2012]]
 
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]

Latest revision as of 12:10, 21 March 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

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