Skip to main content

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

Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

(June 12 meeting notes)
(673 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 +
= Documents =
 +
Some documents written and/or used by the PMC:
 +
 +
* [[E4/Graduation_4.0]]
 +
* [[Eclipse/PMC/Unix Groups]]
 +
 
= 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 =
  
'''Aug 19:''' - McQ, Dani, Martin, Jeff, John A
+
'''June 12, 2018''' - McQ, Alex, Tom, Lars
* '''Pruning inactive committers'''
+
* RC4a looks good; hidpi fix is in place
** Martin: The EMO [http://dev.eclipse.org/mhonarc/lists/eclipse.org-project-leadership/msg00000.html recommends removing inactive committers] in order to keep the project vibrant and relevant. Why are there so many non-voters?
+
** no plans for further builds at this point
*** Dani: Component Granularity - Portal is still broken for JDT UI vs. JDT Core.
+
 
*** Martin: Yet there are likely some who really haven't been active for long -- but only component / project lead would know that
+
'''June 05, 2018''' - McQ, Alex, Tom, Dani, Lars
** McQ: We are not actively searching to prune inactive committers. Committers are good, whether active or not.
+
* Dani:
*** Jeff: sees some sense in pruning the list.
+
** Image limit for help should be increased? -> Not covered in the call
** Rights - what can we actually do in the Portal?
+
** Will most likely not be able to join the next call
*** Component leads can mark people active who appear inactive on the portal
+
* Alex:
*** CL don't have the right to move a committer to Emeritus, only Project Lead / PMC can do that
+
** Support only last LTS version of Linux?
*** Martin: [http://dev.eclipse.org/mhonarc/lists/eclipse.org-project-leadership/msg00002.html The Project Lead can decommitterize] without PMC interaction
+
*** Agreement to drop old LTS versions for 4.9 but not to change the target environment for 4.8
**** Jeff - it's odd that this is not symmetrical to approving new committers
+
** Dropping big Endian -> we all agreed to drop it, MQ found the email to cross, so we can remove it
** John: Once a committer is emeritus and decides to come back, can we make the process of re-making them a committer easier?
+
* Lars:
*** Jeff thinks that the normal committer process is good in this case.
+
** Update to EPL 2.0?
** '''Consensus:'''
+
*** change of about.html is trivial
*** We do not actively ask to remove inactive committers, but if a component / project lead wants to do so, they are welcome
+
*** requires version updates of MANIFEST.MF and pom.xml
*** The process is to first send E-Mail to the potentially inactive committer and if they agree they are [http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg04309.html decommitterized] and optionally turned to [http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg04324.html committer emeritus]
+
*** Script for source update look good, Lars checked manually lots of files
*** If the E-Mail doesn't work any more they can also turn to emeritus immediately.
+
*** Coordindate with Jay or Noopur for the JDT UI update
* '''Reference Platforms'''
+
*** Dani suggested to announce such work via the mailing list so that everyone is aware of the work
** Windows 7
+
 +
** Only one N&N per release? -> Agreed to have one document per release
 +
** Do we get a name for Photon+1 -> Dani: Our SDK is called 4.9, splash screen will only be month year, planning counsil still discussing
 +
** Include Tips and Tricks in the SDK -> Not covered in the call
 +
 
  
<hr/>
+
'''May 29, 2018''' - Alex, Tom, Dani
'''Aug 12:''' - McQ, Dani, Martin, Jeff, John A
+
* Dani:
* '''Retrospective Actions''' -
+
** Uploaded IP log
** Need to nominate a person to care for performance: Dani to try find somebody from JDT core for a bounded time (6 months or so)
+
** Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck
** Build issues
+
** Finalized Photon plan
** Bugzilla performance etc
+
** Sent Release Review material for approval to PMC mailing list
* '''Backward compatibility'''
+
** RC3 looks good so far
** Reporting tool - want a foundation database, that Members can report their API / non-API usage signatures into
+
** Part of the member value-add
+
** KNOWING the impact is the first important thing
+
* '''Forward compatibility''' - from RT / Christian Campo
+
** PDE never tried to ensure that somebody can use 3.4 to launch 3.5
+
** The differences in launching 3.4 vs 3.5 are small... if we would have been aware, we could have made this possible
+
  
<hr/>
 
'''Aug 5:''' - McQ, Dani, Martin, Jeff, John A
 
* '''Security proposal''' on eclipse-pmc list - agree that this should be closer to the target runtimes (wtp, ...)
 
* '''"Plugin" vs "Bundle"''' - Clarification: Proposal was only about PDE. Global replacement is out of reach.
 
** McQ thinks that Plugin is a Bundle that makes use of the Eclipse extension registry (plugin.xml) - Jeff disagrees wrt declarative services
 
** As a message to end users, does it help us if we talk about "plugins"?
 
** Is this an internal statement about tooling, or something we should do more globally?
 
** Real problem is, that people should perceive PDE as tooling for bundles: Make Eclipse more adoptable in the OSGi community
 
** "Bundle" and "Plugin" have been used interchangeably for about 5 years... but still, a more pervasive change would require lots of docs changes that may be very painful for consumers
 
** McQ wants a technical proposal what should be changed
 
** Perhaps provide a '''separate''' tooling for bundles (with property files replaced)? EPP Package for Bundle Developers? - But a choice is not a good thing...
 
** '''Jeff suggestion:''' Do PDE 3.6 that is "all bundles" plus add a compatibility bundle that gives you the word "plugin" back.
 
* McQ: '''Backward Compatibility''' - consuming new versions of Eclipse is still too hard. IBM makes it the highest priority that '''everything''' that ran on 3.5 also runs on 3.6 - including internals - or the new version may not be consumable!
 
** Do anything that may not be easily backwards compatible in the 4.0 stream rather than the 3.x stream.
 
** Jeff thinks this is going to be a hard sell because internals are made to be internal
 
** Jeff: API Tooling that allows people to discover use of internals, see also {{bug|261544}}
 
  
<hr/>
+
'''May 22, 2018''' - Alex, Tom, McQ, Dani
'''Jul 29:''' - McQ, Dani, Martin, John A, Jeff
+
* EPL 2.0
* Dani will start to organize [[Eclipse/Galileo/Retrospective]] items
+
** Still working with foundation on whether we can gradually move to 2.0
* Too many broken builds recently
+
* Will we be supporting updates from release to release in the new 3 month release cycle?
* e4 shipping 0.9 this week
+
** Yes, unless we explicitly indicate otherwise.
* PDE project proposal coming to explore Eclipse build technology
+
** To simplify this, we should have a "latest" update site
 +
** We need to make this simpler for users, but not get in the way of the EPP, OOMF, etc.
 +
** Alex to write this up in more detail
 +
** Dani reminded us that there had been a previous discussion in the planning council
 +
* Project leads have updated Photon plans
 +
** Dani will be updating the overall plan; PMC to comment on bug 529640
 +
* Dani also working on release review and IP log
 +
** PMC members to approve once it's ready
 +
* As previously discussed our first milestone will be called "M2"
  
<hr/>
 
'''Jul 15:''' - McQ, Dani, Martin, John A, Jeff
 
* Dani: What to do with the [http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg08660.html Galileo Retrospective] items? Which ones should become action items? E.g. Bugzilla Slowness?
 
** John: Next PC meeting is Aug 3, should have items for the PC ready by then
 
** Decision: PMC mailing list conversation, will review retrospective action in Jul 29 PMC meeting.
 
* McQ to send out a note to formalize John as the PC representation
 
* McQ wants status messages again for the arch call
 
  
<hr/>
+
'''May 15, 2018''' - Alex, Tom, McQ, Lars, Dani
'''Jun 24:''' - McQ, Dani
+
* GDPR
* Dani asked whether the PMC meeting notes are targeted for the public
+
** audit did not report any issues on our project pages
** McQ: yes, they got announced on pmc mailing list
+
* Opening development for 4.9
* no PMC call next week due to a holiday
+
** Will branch RC2 and update master with required Releng work
 +
** master will be open after RC3
 +
* EPL 2.0
 +
** No plans to do anything for 4.8
 +
** Lars will look into it
 +
** Ideally we gradually move to 2.0
  
<hr/>
 
'''Jun 17:''' - McQ, Dani, Jeff, John A, (Martin joined just as we were hanging up)
 
* Dani asked whether the PMC had internal discussion of new committer votes
 
** A: Generally the PMC member for the component gives +1, unless they feel the need to bring the discussion to the rest of the PMC
 
* Jeff mentioned that we should remind the teams to do retrospectives
 
  
<hr/>
+
'''May 8, 2018''' - Dani, Alex, Tom, McQ
'''Jun 10:''' - McQ, Martin, Dani, Steve, John A
+
* GDPR
* Welcome to Dani, John agrees to be here as a listening member for a while
+
** Eclipse Project collects no information from the users on the project websites
* Sun Java 6u14 (May 25) broken for debugging because thread ID's are changed when garbage collector runs
+
** The Error Reporting tool, might be impacted
** Clearly a Sun bug (also happens in jdb) but not yet confirmed by Sun
+
** Also possibly bugzilla <-- Do we need to delete bugs older than some retention period?
** Described in Readme, but readme will only be available when a rebuild occurs
+
** Impossible to remove emails from all git repos (because of cloning)
** Dani will send out a note tomorrow when they know more about other platforms
+
** We need to be sure to respond to requests from the foundation
 +
* Jetty
 +
** 9.4.10 is in latest build, and help system is working
 +
** they made the dependencies that were problematic optional
  
<hr/>
 
'''Jun 3:''' - McQ, Martin, Steve, Jeff
 
* McQ - asking Dani M to join the Eclipse PMC to represent JDT. PMC agrees. McQ will send a note to Mike Milinkovich / EMO.
 
* McQ - asking John A to represent the Eclipse Project on Planning Council
 
** Jeff thinks that the PC rep should be a PMC member in order to have a strong bi-directional communication path.
 
** McQ proposes asking John to join the PMC calls for communication.
 
** Martin agrees provided that John is OK with this delegate role.
 
* Steve {{bug|277713}} critical bug, probably more critical bugs to triage - defer to arch call
 
* Jeff Target Provisioning discussion
 
  
<hr/>
+
'''May 1, 2018''' - cancelled due to public holiday in most Europe
'''May 27:''' - McQ, Martin, Steve
+
* {{bug|277735}} releng.tools copyright tool - Martin would like to see it released. Discuss in Arch call.
+
  
<hr/>
 
'''May 20:''' - McQ, Martin
 
* PC Lead: John A suggested to represent Eclipse
 
* Linux: New Launchers built, didn't start on Linux ... I-build was broken, want to know why
 
  
<hr/>
+
'''April 24, 2018''' - Dani, Lars, Alex, Tom
'''May 13:''' - McQ, Martin, Jeff, Steve, Philippe
+
* Target environments
* {{bug|273660}} Common Navigator: Pipelining issues with JDT + CDT
+
** We will keep Java 8 and 10 and remove java 9 from the list
 +
** remove JVMs as soon as they run out of support from target environments  - AGREED
 +
* javax.annotation
 +
** Version  shipped is quite old, should we update it to newer version
 +
** Update to latest standalone release to be tried
 +
** Alex to try to drive this through
 +
* Notify cross project about removal of ee modules from the JVM
 +
** People don't follow Java 11 work so will probably be surprised when things start to fail so we better try to spread the information
 +
** Dani will send a link to the JEP containing detailed information
 +
* Contribution guidelines
 +
** Do not open bugs for simple changes and cleanups
 +
** Actual bug fixes to be split from cleanups in separate patches so the bug commit is straight on the topic
 +
** Dani will update the wiki
 +
* Cancel May 1st call - public holiday in Europe
  
<hr/>
 
'''May 6:''' - McQ, Martin, Jeff
 
* McQ PDE Feature Request
 
** New Target Platform came in late
 
** PMC agrees with trying to fix this, but want to see the final patch before +1
 
* McQ Testplan
 
** People going to test their own because test plan is too complex
 
* Jeff Splash Screen
 
  
 +
'''April 17, 2018''' - Dani, Alex, McQ
 +
* On Java 11...
 +
** We are actually shipping the javax annotation support
 +
** Java 11 is working in 4.8, but isn't in 4.7.x
 +
*** Tom Watson is investigating why it is not working 4.7.x
  
<hr/>
 
'''Apr 29:''' - McQ, Martin, Steve
 
* Martin: Java6 ref platform - anything between 6u3 and 6u10 (exclusive) was broken, anything after 6u10 (inclusive) has license issues in [http://java.sun.com/javase/6/javase-6-thirdpartyreadme.txt thirdpartylicensereadme.txt].
 
** Suggestion: Dont update the plan document yet, but start running tests with 6u13 on Linux. '''AI McQ''' talk to Kim about this.
 
** '''AI Martin''' make a final attempt to get more info out of Sun.
 
* Steve: Solaris x86 - looks good but some problems with X server
 
* McQ: API Deprecation Policy {{bug|261544}} - '''AI McQ''' synthesise some summary and comment on the bug
 
* M7: Testers found some interesting prolbems with launching Eclipse from Eclipse (depending on VM, BIDI chars in paths dont work)
 
  
 +
'''April 10, 2018''' - Tom, Dani, Lars, Alex
 +
* Discussed {{bug|533390}}: Eclipse does not launch with Java 11
  
<hr/>
 
'''Apr 22:''' - McQ, Martin, Steve, Philippe
 
* Steve: Solaris x86 - got a Browser running, looking good,
 
* Steve: Cocoa Sheets - new API - Dialogs associated with a Window: Dialog slides down from title bar
 
** Clients need to opt in through new API because they need to specify a dialog as being adequate for sheet support
 
* Martin: Maintenance builds post SR2
 
** experience in the past has shown only very few, surgically isolated patches so the problem is probably smaller than anticipated
 
** don't want anything produced to appear official -- anything that appears official MUST result in a test pass and this must be avoided
 
** it makes sense to talk about this in the context of "Release Train" and not only "Eclipse Platform" -- Martin filed {{bug|273262}} against the AC
 
* Martin has some update on Sun Java 6 -- will update {{bug|261724}}
 
  
 +
'''April 3, 2018''' - Tom, Dani, Mcq, Lars
 +
* 4.7.3a update
 +
** Delivered RC2 on Saturday, so we could fix some badness in handling Java 10 "var" support (tl;dr: rename appeared to allow you to affect "var" as if it were a type (but would not have modified the code))
 +
** Currently think we're done
 +
* Naming milestones
 +
** As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1".
 +
** We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming.
  
<hr/>
 
'''Apr 15:''' - McQ, Jeff, Martin, Steve
 
* McQ: '''Solaris x86''' - OK if we get the machine up and running until Friday, too late for swapping reference platform otherways
 
* '''Polish List''' [[Polish3.5]] - Some developers don't have time for polish items. For now, it's just a list such that we *know* what's coming up.
 
** Martin wondering why we need a separate wiki page, bugzilla query should be enough?
 
** Who owns the Polish list - Eclipse Project Committers. We capture items that we find "stupid" when using Eclipse ourselves.
 
* '''Maintenance builds after 3.4'''
 
** IBM will never consume any community builds: want the absolute minimum of required fixes
 
** If a fix shows up in any IBM product, then it is on a bug somewhere
 
** But fixes are never cumulative
 
** Martin thinks that a first step would be well-defined markup of such "released-to-product" fixes.
 
** Another next step is allowing Eclipse builds by the Community -- we can do anything that's not making Kim's life harder.
 
** How to proceed with communications: open bugs, bugzilla discussions.
 
  
 +
'''March 27, 2018''' - Tom, Dani, Mcq, Lars, Alex
 +
* Java packages for configured Java in workspace
 +
** Equinox no longer provides hard-coded information about execution environments.  In the past this information was used at runtime for describing the running execution environment within the OSGi Framework.  Other usecases outside the Framework started uses the Java profile data from Equinox.  Equinox no longer has any need for the hard-coded information so no longer provides it.
 +
** JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
 +
** JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
 +
** See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=531642 531642] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=532773 532773]
 +
* SWT clean-up
 +
** Lars reviewed the removal of Windows XP.  Built binaries locally on Windows.
 +
** Found a form data issue deleted some code that was still used
 +
** Tom - Unit tests didn’t catch the issue.  Concerning?
  
<hr/>
+
--> Update from Lars after the call: Later testing did show that this is a bug already existing in Eclipse. 4.7 and master and not related to the patch
'''Apr 1:''' - McQ, Jeff, Martin, Steve, Philippe
+
* McQ: Solaris x86 (recommend building since Sun helped at Eclipsecon), Perf results (not trustworthy on Windows?)
+
* Martin: M-builds beyond 3.4.2
+
** Two problems: (a) provide a build system that the community can use, and (b) provide a platform for accumulating fixes easily without risking version collisions etc
+
*** The risk of (b) is high that as a result we'd have some low-quality sea of incompatible fixes. We better don't go with this.
+
** Other solution is allow to cherry-pick on source level - just provide a new target milestone in bugzilla, product builders cherry-pick patches they want to apply and do so locally.
+
* Jeff: OSGi tooling; future plans around build
+
** We need to run builds ourselves (see also above) - e.g. equinox sdk feature is in some internal repository
+
** PDE build has stretched pretty far over time.. what to do with it
+
*** Needs to be one of the main plan items for 3.6, but don't want to wait that long
+
*** SAP perhaps to help out with staffing
+
* Boris to host the arch call since Steve, McQ, Philippe all cannot join
+
  
 +
** Lars did review and test
 +
** Dani - put all the code in the branch and produce a build and ask windows community to test it
 +
** Mcq - thinks it is a good idea
 +
** Dani - create an official build for testing, not out of master with normal builds
 +
** Lars - what is the risk of putting in master
 +
** Dani - can do the build right away pre-CQ review approval.  Allows for more quick testing.
 +
** Alex, no need for a branch, can be a developer build we publish.  Alex will ask Leo to do this.
 +
* Jetty version
 +
** Jetty added non-optional dependencies on service-loader
 +
** Dani - got reverted, but old versions still caused Gerrit build issue
 +
** We don’t need the service-loader for our usage of jetty
 +
** jetty may be making a hard requirement on an implementation of server-loader (Aries spi-fly)
 +
** Can we move help off jetty? Will be a major undertaking.  Should figure out what it would me to do so.  Currently no interested contributer has stepped up to do the work to figure out what this would mean.
 +
** Equinox will still need jetty for the http service implementation.  Perhaps things are more simple if this is an Equinox only dependency.  Only pull in jetty if the http service implementation is needed and then pull in all of jetty and its dependencies.
 +
** No current plans or interested contributors for providing our own service-loader implementation.
 +
** Our build should start resolving the capabilities are requirements which would catch issues like this early in the build.
 +
** Alex - can we move latest tycho to get the capability/requirements meta-data.  No objections?  Alex will move forward.
  
<hr/>
 
'''Mar 18:''' - McQ, Steve, Martin
 
* no arch next week due to EclipseCon
 
* McQ found a performance test that is 8000% slower
 
** teams are overwhelmed (but remind them to check performance tests)
 
* Martin reminded us about use of [http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00575.html Parallel IP for Mature Projects] and JSch-0.1.41
 
** need to identify uses on the download links (or also inside the downloads?)
 
** EMO has not developed the policy yet
 
** McQ: "Q: Should we just not use the mechanism?"
 
** Downstream consumers may need to test against new lib features early. Just for test and experimentation, not for consumption: want parallel IP in I-builds
 
** McQ: Milestones are a corner case -- some consumers use these in products!
 
** Parallel IP is a tool for projects who want it. A clear policy is one thing. Guidelines for projects to adopt it or not is another thing -- may depend on the number and kind of consumers.
 
** Result: Martin to Bring up that topic on the [[Architecture Council/Meetings/March 22 F2F EclipseCon 2009]],
 
*** Example issues: can't put it in for I-build and remove for Milestone S-build
 
  
<hr />
+
'''March 20, 2018''' - Dani, McQ, Tom, Lars, Alex
 +
* Dani: The IBM SWT team considers the Windows XP removal too risky and in addition has no capacity to look at that big change. Fine if someone else looks at the removal. The type changes will have to wait after Photon (too risky). Lars will ask Conrad and Alex will also look at the patches.
 +
* Databinding generification should be done early 4.9, too late for Photon.
 +
* Dani: Eclipse support for Java 10 will be merged to the official branches starting Wednesday. A Marketplace entry for 4.7.3 will be made available once 4.7.3 is released. The first official release with Java 10 support is 4.7.3a scheduled for April 11.
  
'''Mar 11:''' - McQ, Steve, Jeff, Martin
 
* Martin - '''{{bug|227055}} and late API additions'''
 
** McQ: after m6 is too late if it has any downstream impact (changing behavior, deleting things, ...). Plain API additions may slip a week.
 
** Steve: If new API has effect on performance and polish, may look more favorably.
 
** If going in after M6, it needs to go through the process (e-mail and public discussion on eclipse-pmc list).
 
** Strict API Tooling checks to be enabled next week
 
* McQ - '''state of M6'''; some late UI things to review
 
** Some low-risk polish Cocoa items for Eclipsecon (enablers)
 
** Still changes in p2 (after m6), but stabilizing
 
* Martin/Jeff - '''New Target Platform Page''' may require more tweaking - risk of breaking community workflows!
 
** E.g. adding a directory to the target platform; Jeff uses target platforms a lot, so he's likely more exposed than most of the Community... 10 to 15 locations with hundreds of bundles...
 
** Related to the {{bug|224145}} p2 "extension location" problem which broke user workflows. Don't want to have such breakage again.
 
* Jeff - '''Status on Galileo Must do's''' - deferred to next week
 
* McQ - '''p2 OSGi OBR Repositories'''
 
** Jeff: OSGi wants to foster bundle store / bundle repositories, and specify a repository standard (long-standing RFE112 never been ratified)
 
** Similar to p2, but does have some potential issues
 
** Ideally, Equinox would be the reference impl of whatever standard comes up... but got a staffing problem, how to get the solution standardized that we need.
 
*** Writing a p2 OBR repository adapter is not hard, but OBR repos won't be able to eat p2 metadata
 
** p2 doesn't care about XML format whereas OBR specifies the XML. p2 got more sophisticated API model. Jeff doesn't have access to the latest spec.
 
* Steve wants Eclipsecon demos to be done on '''Cocoa''', will expedite any bugfixes (please do file them!). Jeff needs browser integration.
 
  
<hr/>
+
'''March 13, 2018''' - Dani, McQ, Tom
 +
* Alex had troubles to join; Lars still in vacation
 +
* Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
 +
** ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project
  
'''Mar 4:''' - McQ, Steve, Jeff, Philippe, Martin
 
  
* Upgrade 3.4 -> 3.5
+
'''March 6, 2018''' - McQ, Tom, Alex
** Will we be able to support this in p2?
+
* Short call without any interesting topics
*** Nope, needed hooks already in previous release (ie. needed them in 3.4 to be used by 3.5)
+
** Problems include replacing the Eclipse .exe
+
** Is this an important use case?  There is no band width to solve this problem in 3.5
+
** it's a good showcase for p2 technology
+
** idea: put in the low level hooks for 3.5.1 and use them next time (ie. 3.5 -> 3.6)
+
** Did Update Manager ever do this?
+
*** Jeff: It does not
+
  
* Deprecating Mac carbon?
 
** Apple claims Cocoa is the future
 
** 3.5 will be the last version of Eclipse where Carbon is under active development
 
*** But will maintain for 3.6 and 3.7
 
** Q: Has Apple officially deprecated carbon?
 
*** No but they have down played it (ie. no 64-bit support for carbon)
 
** Should there be an official deprecation policy for platforms?
 
  
<hr/>
+
'''February 27, 2018''' - Lars, Dani, McQ, Tom, Alex
 +
* JDT support for new Java releases
 +
** McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible
 +
** Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community
 +
* Dropping XP support
 +
** Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release
 +
** Mail to be posted to cross project by Dani to gather feedback
 +
** Alex: 1 week for gathering input on cross-project - '''AGREED'''
 +
** If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex
 +
** To be formally voted after the mail to cross-project
 +
* Release names
 +
** Version only, release names are irrelevant from Eclipse TLP side - '''AGREED'''
 +
* Inactive committers pruning
 +
** Lars: no access to committer emails so sending just to the mailing list
 +
** Wait 2 months for reply before action
 +
** McQ: ask foundation to send direct mails on behalf of the project, if foundation is not fine - remove committers directly
 +
** Alex: only public replies to the mailing list are accepted so people wanting to remain committers at least follow the mailing list
 +
* Tip of the day -
 +
** Lars: CQ approved, to be merged today/tomorrow
 +
** Alex: we should have it part of the build and part of the p2 repo for easy testing
 +
** Dani: unclear APIs to be removed and to be simplified so we don't end up maintaining useless parts
 +
* GTK 2 vs. 4
 +
** Alex: Gtk 4 release aiming at late 2018, it's big change in drawing so conflicts with Gtk 2 badly
 +
** Alex: Gtk 2 support to be removed in future one of the next 2 releases, whether Sep or Dec to be discussed later in the Photon release train
 +
** Alex: mail to cross project list around Photon M7 or RC when more information on both Gtk 4 release plans and SWT bugs will be known
 +
** McQ: what is our statement on supported Gtk version?
 +
** Alex: Statement should be: Once SWT switches to latest Gtk version as default, support for previous versions goes into deep maintenance mode but will kept until it starts hurting new development and support for the default version at which point to be removed.
 +
** To be discussed further.
  
'''Feb 25:''' - McQ, Steve, Martin, Philippe
 
  
* AC "committers should know" mail
+
'''February 20, 2018''' - Lars, Dani, McQ, Tom
** '''Following external links''' McQ why not introduce some Javascript on the server that warns users automatically when they follow an external link?
+
** Components to projects flattening (not on our plate at the time)
+
* Steve Target milestones for Eclipse project
+
* BZ patches to be flagged when they contain API
+
* '''N-builds broken''' over the weekend (again) - 3 weekends in a row - no people currently who are willing to work during the weekend
+
** Hudson might help eventually, for now using e4 builds as the guinea pig
+
* '''UI Forms has no committers''' - opportunity for Community to become committer
+
** migrate off (using internal browser instead)
+
** no critical bugs, less than 125 interesting bugs
+
** long-term future is e4 with css/styling and declarative ui
+
* '''Performance:''' No news (not yet while closing down API)
+
** Philippe thinks that the performance milestone must be earlier since performance might touch on API. We're losing memory because rebasing
+
** McQ - this cycle we had a performance run in M2, this year we're in a better position than last year
+
  
'''Feb 18:''' - no meeting
+
* Dani: Update on 4.7 RC3
 +
* Lars: Can we drop Windows XP support?
 +
** Lars: Big contribution comes in (https://bugs.eclipse.org/bugs/show_bug.cgi?id=531097), dropping XP support might be a good motiviation to contribute more also to other people. Removing lots of code including the version checks will also result in a cleaner code base for maintenance and might improve performance.
 +
** Dani: IBM investigate if they officially drop XP
 +
** Tom: Do we need support XP with the latest Eclipse version?
 +
--> Pending on the answer of the IBM team, will be discussed in next weeks call
 +
* Tom: OSGI CQs updated and approved for OSGi Service Platform 7.0 version
  
'''Feb 11:'''
 
  
'''Feb 4:'''
+
'''February 6, 2018''' - Lars, Dani, McQ
 +
* Lars: Can we mark MInput and MInputPart for deletion ({{bug|509868}})?
 +
** Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references.
 +
*** McQ agrees
 +
* Dani: [https://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00743.html Topic on ui-best-practices-working-group list]: Replace "..." with an ellipses Unicode character
 +
** Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
 +
** McQ:
 +
*** Mac OS UI guidelines specify to use the ellipses character
 +
*** SWT could do the right thing depending on the platform
 +
* Lars: view menu, minimize and maximize buttons look bad to him. Would like to replace the view menu with ellipses
 +
** Dani: Would have to change all three together. View menu is always there and not indicating an overflow
 +
** McQ: Windows 10 also uses a triangle, but upwards. Current view menu is used and familiar to users for at least more than 10 years.
 +
** Lars to file a bug report and send the bug number to the PMC
 +
* McQ: Should discuss in one of the next meetings how JDT can handle the new release cadence for Java
 +
** Dani: We will see how it goes with Java 11 (18.3)
 +
* Dani: How will we name the milestones in our new new release scheme?
 +
** Consensus to start with M1 after each release.
 +
** Up to planning council to decide the release naming convention. Lars: Would prefer year/month
  
<hr/>
 
  
'''Jan 28:'''
+
'''January 30, 2018''' - Alex, Lars, Dani, Tom
 +
* General Updates (Dani)
 +
** Shipped M5, still working some p2 issues
 +
** RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates
 +
** Discussion about the incubation for Java.  Ongoing thread in jdt-dev list https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00964.html.  The incubation features will be part of the release specification which implies they need to be implemented to be compliant.  Spend time putting them into a release only to pull out later if they don’t finalize.  Not clear there are tests added to the TCK.  Alex asks if this effects us for Java 10, no not for Java 10.  Java 10 only has local type reference, not huge delta of function from Java 9.  No incubation in Java 10.  But incubation may affect us for Java 11.
 +
* Info about infrastructure (Alex)
 +
** Foundation push to move to Jenkins.  Releng has moved, uncovered issues with rest API and token exchange … disabled for now for Jenkins.  Issue is being worked but only can be fixed once all is moved to Jenkins.
 +
** Platform HIPP moving to Jenkins tomorrow.  Will be some downtime, should be less than an hour or so.  May cause several issue.  Issues in non-standard jobs with multiple repos etc.  For Gerrit verifications should be fine.  Let Alex know if there are issues.  Alex to send a note when the migration occurs.
 +
** p2 issue is real.  Other issues are pressing (infrastucture/build).  Todor has a bug that he should be looking at.  Not something happening in the past, but now the capabilities are being resolved.  Issues happened with a hand crafted p2.inf file.  Hopefully will scope down the p2.inf files.  Alex to drive to determine if a respin is needed.
 +
** Need to monitor the p2 issue, determine how many are broken.  Cannot just break 100s of folks without serious consideration.  Why not revert?  Alex says it is not an option and we should do everything possible to fix.
 +
** Lars asks about nominating more committers, perhaps that were rejected in the past.  Now the Eclipse PMC can overlook the nomination process.  Work with existing contributors showing interest and look for opportunities to sponsor them for committership.
 +
* Tip of the day (Clippy)
 +
** See [https://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg08006.html Tips Framework]
 +
** Tip of the Day or (Clippy) in coming contribution … looking for integration M6?
 +
** Lars thinks it is worth it.  Dani disables such things by default, and also Lars.  Alex find the function interesting.  Others are also reviewing the patch. 
 +
** Lars is moving forward with it.  If it is very easy to disable and is stable on all platforms then it should be good.
 +
** Is there a concern about a solution that requires network … it doesn’t appear to be a concern.
  
* Java 6
 
** move reference platform to Sun 6u11
 
*** problem(?): Sun added 3 new items added that are licensed LGPL or GPL
 
*** [[Image:Ok_green.gif]] Martin added comment to {{bug|261724}} to identify this issue
 
* ICU 4.0
 
** we will stay with 4.0
 
* Deprecation Policy
 
** still under discussion, {{bug|261544}}
 
* Use of internal provisional
 
** seems to be some consensus about *not* requiring this, {{bug|261874}}
 
* JDT co-leadership
 
** what is the process?
 
*** Jeff: vote in community; then propose to the PMC
 
*** Would like to get Dani Meghert involved.
 
*** Philippe will check development process documents
 
* Cocoa port
 
** Looking good
 
** Taking early access off and making it the "first" choice for Mac downloads
 
* Milestone progress / 3.4.2
 
** Need to discuss M5 in arch call (should have done this last week)
 
** Should always remind the team in the arch call of upcoming deadlines
 
** Performance issues that need API to fix have to happen by M6
 
*** Teams should understand performance results (will be discussed in a couple of weeks)
 
* Re: Reference Platforms
 
** Java6 on Solaris
 
*** Martin's company would like to support this
 
*** [[Image:Ok_green.gif]] filed {{bug|262907}} to discuss process and practices around reference platforms
 
  
'''Jan 21:'''
+
'''January 16, 2018''' - Alex, Lars, Dani, Tom
 +
* Native builds at eclipse.org status (Lars):
 +
** Dani: swt is done for some time already
 +
** Dani: launchers after M5 is released to prevent breakage
 +
* GTK launcher changes (Alex):
 +
** Changes to not rely on X11 atoms but on dbus ready for review
 +
** Linux only as no other GTK platforms are currently built
 +
* Equinox CQs (Tom):
 +
** P2 capabilities patch from Todor and felix.scr update
 +
** Slow process risking M5
 +
** Alex: Ping Sharon asking for speedup if possible
 +
* Updates from Dani:
 +
** Photon plan update - BREE to be part of the build info
 +
** End game - Oxygen.3 and M5 - send to the list
 +
** Running tests against Java 9
 +
* Java 10 eclipse release (Dani):
 +
** Oxygen.3a or marketplace feature only - Agreement for oxygen.3a
 +
** Dani: Local Variable type inference support in a branch
 +
** Future releases - to be aligned with JVM releases if they prove to release on time
 +
* BREE updates recomendations
 +
** Dani: There are reasons to stay on older BREE
 +
** Alex: ease of getting jvm is the main concern here - if a contributor can't get jvm at that version easily we can't call it supported
  
* How should we track meeting minutes topic - Wiki
 
* Provisional API conventions - Jeff working on {{bug|261874}} for discussion at the AC
 
** should there be a tag in the Javadoc (ie. "experimental")?
 
** Jeff wants to keep the concerns "conventions" vs "Javadoc" separate
 
** Jeff, "... Javadoc should not be generated for provisional ..."
 
** Martin disagrees, "... need feedback and discussion for new API ..."
 
* What is the '''role of the PMC lead?'''
 
** global view of components/processes
 
** organize architecture call, ensure we are on track
 
** spark conversations (ie. M5 is feature freeze)
 
* '''Reference platforms'''
 
** we should choose JDK1.6, "update 11" rather than "update 4"
 
** around "RC time", solidify the reference platform (it is the one we are testing on)
 
  
'''Jan 14:'''
+
'''Januar 09, 2018''' - McQ, Alex, Lars, Dani
 +
* Updates from Dani:
 +
** Ian Skerrett is leaving the Eclipse foundation
 +
** Dani got nominated as committer representive
 +
* Planning council update
 +
** Dani: low participation in the last calls
 +
** Dani will talk with Melanie about it
 +
** Input  required for the planning council for the API and feature freezes for the platform
 +
* API and feature freeze policy in platform
 +
*** Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build
 +
*** everyone agrees to Alex suggestion-> agreed
 +
* Alex: SWT linux currently uses X-Windows specific API, which does not work on Wayland. This will be moved to a DBUS API to open file and open URL
 +
* Dani: Plan update, biggest change is for the component plan
 +
** Equinox plan has been added
 +
** Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build
 +
* Launcher and natives build move from IBM to the foundation still in progress
 +
** ({{bug|528230}}) Build FileSystem native component on Eclipse Foundation Infra
 +
** ({{bug|528230}}) Build launcher on Eclipse Foundation Infra
  
* PMC component ownership x bugzilla pmc authorization
+
= Archive =
 +
* [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]]
 +
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 +
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]
 +
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 +
* [[Eclipse/PMC/Minutes 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 2010 | Archive of Meeting Minutes from 2010]]
 +
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]

Revision as of 11:15, 12 June 2018

Documents

Some documents written and/or used by the PMC:

Meeting Schedule

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

Meeting Minutes

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

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

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

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


May 29, 2018 - Alex, Tom, Dani

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


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

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


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

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


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

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


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


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

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


April 17, 2018 - Dani, Alex, McQ

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


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

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


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

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


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

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

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

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


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

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


March 13, 2018 - Dani, McQ, Tom

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


March 6, 2018 - McQ, Tom, Alex

  • Short call without any interesting topics


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

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


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

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

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

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


February 6, 2018 - Lars, Dani, McQ

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


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

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


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

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


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

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

Archive

Back to the top