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"

(→‎Meeting Minutes)
(→‎Meeting Minutes)
(149 intermediate revisions by 5 users not shown)
Line 11: Line 11:
 
= Meeting Minutes =
 
= Meeting Minutes =
  
−
'''May 14, 2019''' - McQ, Dani, Alex, Tom
+
'''Mar 31, 2021''' - McQ, Tom, Alex, Lars
−
* No complaints about our M2 delivery so far
+
* Java 16 jar signing issue
−
* M3 is next week
+
** Tom wants to replace equinox implementation with builtin Jar file implementation so changes don't have to be done in Equinox on each release
−
** 200 bugs still open
+
* JSP/Jetty story in IDE
−
** People are just bumping them to the next milestone
+
** Do we still need same functionality?
−
** Better to remove target milestone if you don’t actually believe it will be fixed by then
+
** Alex - get out of the business for help system. Dependencies (jetty, lucene) generate more releng work than we can handle.
−
* Jetty dev list note:
+
** McQ - url for plugin help would be simplest and open it in browser
−
** https://www.eclipse.org/lists/jetty-dev/msg03307.html
+
** Any change (e.g. JSP removal) has to go through standard deprecation period, announcements and etc.
−
** javax namespace stuff will move jakarta namespace
+
** Alex to initiate communication on longer term plan with Holger who works on improvements to help system lately
−
** Jetty 9 and 10 will support what was there, but we will need to react at some point
+
−
** Things in flux
+
−
* Batik update — 4 of 5 CQs approved should be in for M3
+
  
  
−
'''May 7, 2019''' - McQ, Lars, Dani, Alex
+
'''Mar 31, 2021''' - McQ, Tom, Alex
−
* Gerrit verification jobs to give -1 on warnings
+
−
** Dani: not easy, single file with warnings in Jenkins for all type of warnings
+
−
** PMC is in favor of such solution but there are technical limitations to achieve it or it would require significant effort to get to warning free builds
+
−
* ECF http client update
+
−
** Dani: prefer to ship both old and new implementation, fine with new one only and reconsider
+
−
** Alex: not in favor of shipping two implementations as that would make the testing harder, prefer to ship single one and that being the new one, reconsider if there is issue
+
−
** ACTION: Dani to reply to Scott that Eclipse SDK will ship latest only and we would like to have it for testing purposes ASAP
+
−
* Inactive committers
+
−
** Dani: Notification sent and inactive committers that want to keep commit rights can do it now
+
−
* 2019-06 M2
+
−
** Dani: I-build delivered to M2
+
−
* Dependency updates
+
−
** Alex: Jetty is in progress to 9.4.18, permissions to publishing the version to p2 repo on behalf of Jetty project granted
+
−
** Alex: Batik - work in progress
+
  
 +
* PMC call time
 +
** Overlaps with Planning council call and both Tom and Alex can't make both
 +
-> Decision: Skip PMC call every first Wed of the month
  
−
'''April 30, 2019''' - McQ, Tom, Lars, Dani
+
* Webpage Hugo migration
−
* M2 for us this week - will only contribute last good I-build - no real milestone week
+
** Recommended by Eclipse Foundation and active contributor to do the conversion
−
* Extend fast track for committers for all projects not just inactive ones
+
** Concerns about mixing old and new content are raised but they don't look severe
−
** Tom: already following the proposed process
+
** Supported by PMC
−
** We can't force committers to accept a new committer (against EDP)
+
-> Tom to handle initial communication on behalf of PMC
−
** Unanimous decision to drop fast track program. Mentor/committer can propose any contributor if he can justify the nomination
+
−
* Request for review on JDT mailing list
+
−
** Wait for Stephan to respond for a day or two
+
−
** Dani to contact Stephan if no response
+
  
 +
* Planning process relevance
 +
** the planning process is not providing the detailed and usable plans from the past
 +
** not a pain point as fewer people participate it but looks like useless exercise quite often
 +
** to be discussed....
  
−
'''April 23, 2019''' - McQ, Alex, Dani, Tom
 
−
* M1 train has been published but no official announcement was sent
 
−
* Alex to update Jetty with latest security fixes
 
  
 +
'''Mar 24, 2021''' - Tom, Alex, Lars
  
−
'''April 16, 2019''' - Lars, Dani, Tom, McQ
+
* Pack 200 - API removal in 2 years - 2023-06
−
* M1 has shipped -- Lots of good stuff, see the N&N
+
** Should we turn off all pack 200 features in one year, make it consistent across all Java versions.
−
* Plan has been posted
+
** 2022-06 - disable pack200 for all Java versions. Calling the deprecated API will be a no-op
−
** Attempt to simplify the creation process, still WIP
+
−
* Started working on identifying inactive committers
+
−
** Inactive == haven't committed anything for 2 years
+
−
* Looking at ways to ensure we have enough testing of new Java features
+
−
** Main projects should run on widest ranges of versions, so can't just raise BREE there
+
−
** Could add new test projects, and allow tests to be written with new constructs
+
  
 +
* Pack 200 - When can we stop generating? Agreed on 2021-09 release.  We should set the precedence as early as possible to stop producing pack200 artifacts.
  
−
'''April 9, 2019''' - Alex, Dani, Tom, McQ
+
* split packages
−
* Dani
+
** Causing issues with mandatory directive and p2 {{bug|360659}} and with tycho.
−
** Lots of regressions Dani investigating
+
** Currently tycho requires some work arounds for usage of split packages
−
*** cycle from tests (fixed)
+
** Can we work to get rid of split packages. We agreed to investigate the work and move to combine split packages if possible.
−
*** UI elements gone missing (fixed)
+
−
** Get rid of the new index from JDT
+
−
*** Needs lots of polish to get rid of bugs, but never showed performance improvements.
+
−
*** Decided to disable the option to use it (code remains).  Open to others to help maintain.
+
−
** Created initial 2019-06 (4.12) plan
+
−
*** Still need individual plan bugs from leads (cough Equinox).
+
−
** Created initial release record for 2019-06 (4.12)
+
−
** Made a call for plan items for 2019-06 (4.12)
+
−
** M1 this week
+
−
*** Looks good so far.
+
−
* Tom
+
−
** Investigating parallel activation of bundles {{bug|540507}}
+
−
* Alex
+
−
** M1 fixes for SWT
+
−
*** Fixes for other things in M1 some small regression in custom Linux environment.
+
−
** M1 jsch update needed
+
−
** Tom to Open bug for Apache Felix SCR update post M1
+
−
** SWT issue
+
−
*** SVG image support for Linux-only to start.  Need support for other platforms.
+
−
*** Windows has a number of patches pending. (mostly cleanup patches?)
+
−
*** Try to get more people on board for Windows support help.
+
−
*** Ask for help on the platform list.  We have combined the projects and have more devs available to work on SWT if they are willing to help.
+
−
*** For cleanup you need specific SWT knowledge.
+
−
**** two types of cleanup - use quick fix from Eclipse - and real refactoring.
+
−
** If we are to advance SWT development then we cannot continue with a single committer on a platform.  Need to promote the recruitment of new SWT committers.
+
  
  
−
'''April 2, 2019''' - McQ, Dani, Lars, Tom
+
'''Mar 17, 2021''' - McQ, Tom, Alex, Lars
−
* Planning for this release has started
+
* SWT Chromium support
−
** Sub-projects need to have first cut of plan ready by a week from Friday
+
** Still no recent version of Chromium with security patches
−
* Also a week from Friday is our M1
+
** Will be dropped in M1 (if no recent version is provided in the next weeks or if no one steps up)
−
* Based on community feedback we will keep the update site for adding Java 11 support to the 2018-09 (4.9) release, the Marketplace entry remains removed
+
  
 +
* Pack 2000 support
 +
** not supported anymore as of Java 14
 +
** will be deprecated and marked for removal
  
−
'''March 26, 2019''' - McQ, Dani, Alex, Tom
+
* Moving Eclipse repos to Github
−
* Dani
+
** Moving to Github might simplify and therefore increase contributions
−
** Inactive committer cleanup progress.
+
** Huge amount of work in releng
−
*** It is now harder.  Portal has been deactivated and the functionality to get inactive committers is gone.
+
** Potentially we should all subprojects at the same time
−
*** Looking to use some script originated by Lars for list of contributors.
+
** We check if the foundation plans to move everything to Gitlab
−
***  What is the timeline to be considered inactive again?  Ans. A year of inactivity will trigger the question.
+
−
* Alex
+
−
** Confirms that the new indexer has no value to Red Hat (see also March 5 and {{bug|544898}})
+
−
** {{bug|545032}} Implement native ImageLoader (Linux only)
+
−
*** Allows additional formats not previously supported to work with the native Linux implementation of SWT
+
−
*** What kind of error message will be available on other platforms?
+
−
*** Need to confirm the API doc is updated to indicate what formats are supported on what platforms. (Alex will take care of that in the javadoc)
+
−
*** Has there been investigation into what later Java versions provide for image loading?
+
−
**** No, could be done as part of investigating support on other platforms.
+
−
*** Need to have an umbrella bug for the new functionality with additional children defects for the platforms that don't support the new formats. (Alex to open that)
+
  
  
−
'''March 19, 2019''' - McQ, Lars, Dani
+
'''Mar 10, 2021''' - McQ, Tom, Alex
−
* Dani
+
* Moving to Jetty 10 for next release
−
** 4.11 on track - repositories and download page ready for tomorrow
+
* platform-dev discussion about move to GitHub
−
** Java 12 GA expected today
+
** conversation is useful, but would take a lot of planning
−
** Will merge Java 12 work to master tomorrow or on Thursday
+
** lots of current rel eng dependencies on Gerrit
−
** Will provide a Marketplace entry for Java 12 support for 4.11
+
*** need more community help for rel eng issues
 +
** a massive amount of history in our Bugzilla
 +
* release record and proto-plan created for 4.20
  
−
 
−
'''March 12, 2019''' - ???
 
−
* Missing
 
  
 +
'''Febr 17, 2021''' - Lars, Alex, McQ
 +
* Looks good for 4.19 release
 +
* Mac ARM has to wait for the 4.20 release, as the team fights multiple issues
 +
* Top-level project page can currently only be edited by Tom, other PMC members also have access to it https://projects.eclipse.org/projects/eclipse/who
  
−
'''March 5, 2019''' - Tom, Alex, Dani
 
−
* Dani
 
−
** I will be away starting Friday and next week. No laptop ==> watch out for any 4.11 related issues
 
−
** Tom, please update the status on the Equinox 4.11 plan
 
−
** Tom: {{bug|544370}}: NoClassDefFoundError: org/apache/sshd/server/auth/AsyncAuthException from SshServ
 
−
** {{bug|544833}}: Inactive committer cleanup for Platform for the 4.12 release
 
−
*** Might be much more work since committer info from old portal is not available in the new PMI
 
−
** Get rid of new indexer. Alex, not sure who from Red Hat mentioned it at EclipseCon Europe but there seemed to be interest to further work on this.
 
−
*** Alex: Roland looked at it and could not see any benefit
 
−
*** Current thinking: drop it, but Alex will double-check and report back in two weeks
 
  
 +
'''Dec 15, 2020''' - Lars, Alex, McQ
 +
* 06. January 2021 is the next meeting
 +
* How can PMC increase the awareness of the project leads / committers?
 +
** Maybe invite the project leads once per month to the PMC meeting?
 +
** Discussion how we can increase the JDT community
  
−
'''February 26, 2019''' - McQ, Tom, Alex, Lars, Dani
 
−
* Dani
 
−
** Issues with Mac signing
 
−
*** McQ: we should ask the Foundation whether they can't set up a watchdog
 
−
**** Dani: filed ({{bug|544915}})
 
−
** Issues with JAR signing
 
−
** Release on track
 
−
** Prune inactive committers
 
−
*** AGREED to do this like we did last year for Platform ({{bug|530200}})
 
−
*** Lars for Platform. Tom for Equinox and Dani for JDT and PDE
 
−
* Lars: move active committers to the list of contributors in the Acknowledgments
 
−
** AGREED
 
  
 +
'''Dec 01, 2020''' - Lars, Alex, McQ
 +
* RC1 is out; final touches on RC2
 +
* How can we remove the confusion about "e4" project?
 +
** e4 has always been intended to be a sandbox project where people could try things that are experimental or are on a longer timeline
 +
** Should be renamed to make it clear this isn't about leftovers from the Eclipse 4.0 work (maybe "eNext"?)
 +
** Should clean up repos
 +
*** Remove repos that just hold code that has already moved to the platform
 +
*** Remove repos that are no longer getting any investment
 +
*** Work toward moving things that are active/useful into the platform (e.g. "spies" to PDE)
  
−
'''February 19, 2019''' - Tom, Alex, Dani, Lars
+
'''Nov 24, 2020''' - Lars, Alex, McQ
−
* Lars: API removal announcement on cross project
+
* PMC is considering the potential of an SDK / IDE working group at the foundation
−
** AGREED: To send one mail per release for RC1 announcing all removals to reduce noise on the mailing list
+
−
** In case of more important removal it can be announced individually.
+
−
** Dani to open bugs for releases so it's handled properly.
+
−
* Lars: Provisional API guidelines changes
+
−
** Current approach with internal/provisional package names until API is stable is an issue because:
+
−
*** It creates more work for maintainers to rename packages.
+
−
*** It creates more work for adopters to change references once API is stable.
+
−
** AGREED: Use the intended package name but mark it as x-internal until API is final. Lars will update the document.
+
−
* Dani: End game plan posted
+
  
 +
* Discussion Do we need the extra releng work to create p2 repositories for milestones?
 +
** Lot of extra work and sometimes goes wrong
 +
** All I-Builds are anyway available
  
−
'''February 12, 2019''' - Tom, Alex, Dani, Lars
+
-> PMC decided to drop the additional p2 repository
−
* Dani:
+
-> Alex will be sending out an email about it to inform potential users of the special p2 repos
−
** M3 next week.
+
−
** Must start to work on IP log, release review and Endgame plan.
+
−
* Alex: What's the future of ECF (not much happening there)? How feasible is it to replace ECF and HttpClient with new Java HTTP Client from Java 11?
+
−
** Interesting to know, but unfortunately no resources to investigate this at the moment.
+
−
* PMC decision regarding HttpClient for 2019-03: will ship what we have (4.5.5).
+
  
 +
** Discussion about the purpose of the milestone week at all
 +
-> Decision not to change the process for now, as the additional testing and focus has also some benefits
  
−
'''February 5, 2019''' - Tom, Alex, Dani, Lars
 
−
* Dani:
 
−
** I-build contributed to 2019-03 M2, no complaints so far
 
−
** Over 200 bugs for M3 with 2 weeks left, need to be looked at and target adjusted
 
−
* Alex:
 
−
** JIPPs are subject to update to new infra in the next few months. Releng JIPP is a matter of separate treatment.
 
−
** As soon as most JIPPs (not Eclipse TLP only) are moved to new infra SWT will move to GTK 3.22 as a min version.
 
−
** Sep 2019 release is the earliest possible for SWT GTK min version bump.
 
−
* Tom:
 
−
** equinox.framework and bundles git repositories merge
 
−
** APPROVED if history is preserved
 
−
** Alex: new name of repo should be eclipse.equinox.* not rt.equinox
 
−
** After merge Alex takes renaming rest of equinox repos with webmaster
 
−
* Lars: Fosdem
 
−
** IDE and Free Tools room
 
−
** Netbeans and IntelliJ talks and interest
 
  
 +
'''Nov 17, 2020''' - Lars, Alex, Tom, McQ
 +
* Release 4.18 winding down
 +
** SWT churn for Linux and Mac Big Sur
 +
** Does not appear the Foundation got the new Mac Hardware for testing
 +
* Planning Council discussion
 +
** Dani filled the Eclipse TLP representation role on the Council
 +
** Alex can take the lead to that role
 +
** Alex will look to find a replacement for the tools TLP representative
  
−
'''January 29, 2019''' - McQ, Tom, Alex, Dani, Lars
 
−
* Alex: Java 11, should we move the build to Java 11?
 
−
** Agreed to move the Tycho snapshots for testing and move back to Tycho stable after M3
 
−
* Dani: This week is M2, we will contribute the Wednesday I-Build with some sanity checks
 
−
* Dani: Having problems with the asynchronous JDT UI initialization {{bug|543935}}
 
  
 +
'''Nov 10, 2020''' - Lars, Alex, Tom, McQ
 +
* Still dealing with the loss of Dani
 +
* Discussed representation of JDT on PMC
 +
* Stabilizing for M3
 +
* Some releng issues with Java 15 and 16
 +
* Tom began investigating p2 ECF httpclient dependency
  
−
'''January 22, 2019''' - McQ, Tom, Alex, Dani
 
−
* Alex:Felix SCR update
 
−
** Tom: Orbit update to make felix.scr bundle imports non-optional
 
−
** Missing compile warning in the first build - not clear why it happened
 
−
* Tom: Equinox tests move from runtime git repo
 
−
** Needed because tests are not run on gerrit and not findable for contributors
 
−
** Alex: how easy it is to find which one are for equinox and which should stay in runtime repo
 
−
** Tom: to open bug with details
 
  
 +
'''Nov 10, 2020''' - Lars, Alex, Tom, McQ
 +
* Still dealing with the loss of Dani
 +
* Discussed representation of JDT on PMC
 +
* Stabilizing for M3
 +
* Some releng issues with Java 15 and 16
 +
* Tom began investigating p2 ECF httpclient dependency
  
−
'''January 15, 2019''' - McQ, Tom, Alex, Lars, Dani
 
−
* Dani
 
−
** We shipped 4.11 M1 last Friday - no issue so far
 
−
** Created release record for 4.11 (mandatory to be there by 4.11 M1)
 
  
−
* Lars: {{bug|543218}} was a severe regression in M1
+
'''Nov 3, 2020''' - Lars, Alex, Tom, McQ
 +
* Dani!
  
−
* Tom
 
−
** Chatter about update configurator {{bug|542706}}
 
−
** Alex: update configurator still there but not hooked into Equinox/p2/PDE anymore
 
−
** Alex and Lars to update the bug report
 
  
 +
'''Oct 27, 2020''' - Lars, Tom
 +
* Nothing to discuss
  
−
'''January 8, 2019''' - Dani, ?
 
−
* We had a meeting, no notes were taken
 
  
 +
'''Oct 20, 2020''' - Lars, Tom, McQ, Alex
 +
* EclipseCon is running virtual this week
 +
* Agreement that removal of API should only before M1 release
 +
* Proof of concept for using Java 11 http client instead of ECF should be done
 +
* if we remove ECF we should send out an announcement and keep it for at least one release
 +
* Decision to start using the @Deprecated(since = "x.y.z", forRemoval = true) for planned API removals if the bundle can use Java 11, wiki for API removal should be updated
  
−
'''December 18, 2018''' - McQ, Tom, Alex, Dani
+
'''Oct 6, 2020''' - Dani, Tom, McQ, Alex
−
* Talked about potential release train delay due to JAXB - nothing we have to worry about
+
* M1 under control
−
* Next call on January 8
+
* Release train materials being worked
 +
* Moved to Jetty 9.4.32
 +
* ECF — need to simplify how we consume http client
 +
** could use Java11 http client instead, but this would require significant development effort
 +
** Tom/Alex to take an initial stab at understanding scope + open bugs
 +
* Proposal: remove API once a year
 +
** Given the already long time for consumers to respond to API deprecation, PMC decision was to continue to allow API removal in any release. It was felt that the incremental benefit was outweighed by the need to be able to move forward quickly.
  
  
−
'''December 11, 2018''' - Tom, Lars, Dani
+
'''Sep 15, 2020''' - Dani, Tom, Lars, Alex
−
* Dani: 4.10 looks good, work for 4.11 is open for development
+
* M1
−
* Dani: Will add Bugzilla milestones
+
** Next week M1 - Alex to send reminder note
−
* Tom: Will update Equinox to Java 8 soon will need to support Java 8 for quite some time in the future
+
** Holiday in India on this Friday
  
 +
* Y-Build for Java 16
 +
** Builds should be fixed and can continue to progress on Java 16
  
−
'''December 4, 2018''' - McQ, Alex, Tom, Lars, Dani
+
* SCR upgrade
−
* Dani away on Thursday and Friday.
+
** Some issues with EBR maven plugin
−
** Please keep an eye on RC2.
+
** causes versions to be incorrectly represented in p2 meta-data
−
** Please watch the release review ({{bug|541666}}).
+
** Orbit needs a new lead, will end up impacting us if no replacement found
−
* Dani: 4.10 on good track but investigating last minute {{bug|542090}}.
+
−
* {{Bug|541689}}: What needs to be done to add OpenJDK on Windows as a reference platform?
+
−
** We will add this for now, but for 4.11 we will query the community which runtimes are actually used and/or tested.
+
−
** Alex: We need to specify from where the OpenJDK runtime comes from.
+
−
* Tom: When do we push 4.10 to Maven central?
+
−
** Dani: ask on Releng list.
+
−
* Alex: Help Center issue. What's the state?
+
−
** Tom will investigate this a bit more this week. Probably no fix for RC2.
+
  
 +
* Tycho being updated to be able to OSGi-fy JARs if they are not there yet.
 +
** How to use this for a feature?
 +
** Behaves much like Orbit to produce new versions of the artifact.
 +
** Could be the solution for Orbit needs.
  
−
'''November 27, 2018''' - Alex, Dani, McQ, Tom
 
−
* Mailing lists
 
−
** Discussion on merging various mailing lists {{bug|541508}}
 
−
** Merge all platform-x lists into one (platform-dev?) list, except the current platform-releng-dev will remain separate.
 
−
** merge all jdt lists into one list (jdt-dev?) list.
 
−
** Considered merging the equinox-dev and p2-dev into one list (equinox-dev?), will leave separate for now because the two groups still seem to have distinct topics to discuss (even if the traffic is relatively low).
 
−
** What is the target usage of the lists?  For the user community to ask questions or for the developers to have discussions around development of Eclipse?  At this point the traffic is low and the PMC does not see a need to discourage usage by the user community to ask questions.
 
−
** Before merging we need a way to have responses sent to messages sent to the old archived mailing lists which directs them to the new list.
 
−
* Rules for freeze/endgame
 
−
** Consider allowing the gerrit reviews to act as the way to record approval by a member of the PMC and/or project lead instead of requiring that to be flagged in the bugzilla.  If the gerrit review was done by someone other than a member of the PMC or project lead then there still needs to be some record in the bugzilla that the required approval of the PMC or project lead was done.
 
  
 +
'''Sep 22, 2020''' - no meeting
  
−
'''November 20, 2018''' - Alex, Lars, Dani, McQ
 
−
* Dani reminded the team to update plans so we can do release review
 
−
* Dani working on IP review
 
−
* M3 this week; then API/feature freeze next week; then one more week and we’re done
 
−
* JDT Code Mining went in today; test!; disabled by default
 
−
* Demonstrated proof of concept, empty shell running on GTK4 alpha
 
−
* {{bug|541307}} needs to be investigated; could be a blocker for PDE or Equinox
 
−
* Seems to be general consensus that code clean-up is more important than maintaining git blame usefulness
 
−
** Ref: https://www.eclipse.org/lists/eclipse-pmc/msg03568.html
 
  
 +
'''Sep 15, 2020''' - McQ, Dani, Lars, Tom, Alex
 +
* Dani: Java 15 released today
 +
** 4.17 release together with Marketplace for Java 15 support are ready
 +
** JDT Java 15 to be merged this week
 +
* Dani: Zoom call with password unless each of the PMC members can be added as meeting owner so can start the meeting
 +
* Alex: 4.18 stream opened and releng work calmed down
 +
* Lars: Cleanup of migration guides
 +
** Dani: this will break existing links, so existing content have to stay unless someone does all the work to fix our plans and other links that will break
 +
** McQ: help system needs work to focus on the latest stuff/release, what should we do to achieve it? How can we better shape the help system now that having all content ofline is not a requirement?
 +
** Alex: do not ship migration, n&n,etc. but rather point to website url from help system
 +
** Alex: this would also reduce manual work for releng (+1 by Dani)
 +
** ACTION ITEM: Alex to work on n&n in help system to use the website content directly as a proof of concept for further work
  
−
'''November 13, 2018''' - Alex, Lars, Dani, McQ
 
−
* Plan update 4.10 plan update 1 from Dani
 
−
** As Foundation still provides only SLES 12 we might still have to list it
 
−
** SWT team tests on SLES15
 
−
** Details: {{bug|541074}}
 
−
* Train name update from Dani: We can keep "our" Eclipse IDE name, foundation dropped the idea of adding an additional identifier to the "Eclipse IDE" brand.
 
−
* jsch - Dani checked if preferences are used and could not find any usage, Dani did not yet contact Thomas as JGit did not make any progress in the area. Alex did update Equinox.
 
−
* Cherry-pick as strategy in Gerrit
 
−
** {{bug|541021}}
 
−
** Dani does not like the idea and voted against it
 
−
** Alex: Linux tools and CDT are using Cherry-pick
 
  
−
-> Everyone agrees that the build infrastructure is getting worse and that we should find ways to speed up the build, Dani will follow-up with the foundation on that
+
'''Sep 01, 2020''' - Lars, Alex
 +
* RC1 is fine, no additional requests for RC2
  
  
−
'''October 30, 2018''' - Alex, Lars, Dani, Tom
+
'''August 25, 2020''' - Tom, Lars, Alex, Dani
−
* Dani: Update on release train name
+
* Dani: sent out Endgame plan, RC1 this week, vacation starting on Friday
−
** Foundation accepts "Eclipse IDE" as long as the scope is clear
+
* Alex informed about Red Hat's Releng participation
−
** Foundation can use another name when the Eclipse IDE is shown along with other IDEs, e.g. Che. Possible name could be "Eclipse Classic IDE"
+
−
* Increase major segment when deleting deprecated API
+
−
** Discussed last year on [https://wiki.eclipse.org/Eclipse/PMC/Minutes_2017 October 10, 2017] but did not make an official decision
+
−
** Disruption would be huge
+
−
** Today we decided unanimously that in general we will NOT increase the major version when removing deprecated API
+
−
*** There might be cases/bundles where we might be more aggressive
+
  
  
−
'''October 23, 2018''' - No meeting due to EclipseCon Europe
+
'''August 18, 2020''' - Tom, Lars, Dani
 +
* Dani to create and send out Endgame plan
 +
* Looking into Mac Big Sur launching issue ({{bug|565913}})
  
  
−
'''October 16, 2018''' - Alex, Lars, Dani, McQ
+
'''August 11, 2020''' - Alex, Dani, Tom, McQ
−
* We all agreed that at this point, the right thing regarding renaming the project is to do nothing.
+
* Eclipse Foundation is getting access to an Apple Silicon dev kit
−
* Delivered 2018-12 (4.10) M1 on Friday. No feedback on that so far. Train to deliver this Friday.
+
** Will make it available to SWT devs via cloud connectivity
−
* Dani gave an update on the work for the EDP.
+
* M3 next week; RC1 following week
−
* Alex together with Mickael will make sure that the Unconference session at EclipseCon will be split into interest groups after initial discussion.
+
* ARM64 port seems to be working fine, except for browser widget (still investigating)
  
  
−
'''October 9, 2018''' - Alex, Lars, Tom, Dani, McQ
+
'''August 4, 2020''' - Alex, Lars, Dani
−
* 4.10 plan and release record published
+
* no topics to discuss
−
* 4.10 M1 looks good, low number of bugs
+
−
* Project naming - pushback in planning council and there will be no change until Eclipse Foundation provides the document describing the rules names should comply with
+
−
* Performance tests
+
−
** Lars: jdt.core performance tests not running
+
−
** Dani: performance tests running (mostly) since Photon, most work done by Sravan
+
−
** Dani: results look sane but need to be checked thoroughly for some time to ensure all the infra runs proper
+
−
** Alex: SWT perf tests for 4.9 properly shown improvement in startup initialization
+
  
  
−
'''September 18, 2018''' - Alex, Lars, Dani, Tom, McQ
+
'''July 28, 2020''' - Tom, McQ
−
* Release looks ok, respin was required
+
* no topics to discuss
−
* EPL 2.0 conversion was done for the Eclipse SDK but not for the e4 sub projects
+
−
** Lars: e4 repository have not been converted
+
−
** Dani: JDT, Equinox, PDE and Equinox have been converted so the Eclipse SDK has been converted
+
−
** Lars plans to convert the e4 spies
+
−
** Dani will inform Wayne/ Webmaster about the EPL 2.0 migration of the Eclipse SDK
+
−
* Alex suggests deleting the long dead e4 repository like e4 JDT (no commits for 5 years, they should be archived) -> Alex to announce on e4 mailing list
+
−
* Lars reports that SAP might get more involved, he delivered a workshop for them and they have very skilled developers which hopefully will contribute to the platform.
+
−
* Dani: JDT will create a common plan for its components under https://wiki.eclipse.org/JDT/Plan/4.10, similar to platform.
+
  
  
−
'''September 11, 2018''' - Alex, Lars, Dani, Tom
+
'''July 21, 2020''' - Tom, Dani, Alex, McQ, Lars
−
* Dani: 4.9 Review is done and passed
+
* no topics to discuss
−
** Release is looking good for final phase
+
* Alex on vacation next week
−
** RC2 is done - no planned changes left for 4.9
+
−
** Moving on for 4.10
+
−
* Alex: 4.9 is in good shape now
+
−
** Had last minute issues that almost made us miss RC2 date.  Felix SCR change in qualifier caused meta-data to be regenerated because of an upgrade in Tycho.  Tycho now published generic OSGi capabilities.  This lead to cases where Felix SCR would get included without equinox.ds.  That lead to issues with activating Felix SCR.
+
−
** Tycho is fixed now to handle starting of Felix SCR, worked around issue for 4.9
+
−
** For 4.10 dropped 32-bit and gtk2 now
+
−
* Tom: org.eclipse.equinox.ds to be removed.  Decided to keep equinox.ds in the repository as part of the Equinox SDK feature, but it will not be shipped as part of the Eclipse SDK features.
+
−
** Need to make sure other areas can handle equinox.ds missing (e.g PDE)
+
−
* Dani: Informs us if the team attending Eclipse Day and EclipseCon events.
+
−
* Via email: Pinging robot for bugs will be activated for all subcomponents of the Eclipse top level project, as it is currently not possible to activate the robot for only a sub-component.
+
  
−
'''September 04, 2018''' - Alex, Lars, McQ, Tom
 
−
* CQ in JDT was approved to create code duplication. Lars asked what caused that.
 
−
** Delay in JDT review, biggest blocker is still not in JDT
 
−
** Large change, agreed with Dani to get review priority review in 4.10 from the JDT team
 
−
* Alex/Tom - 4.9 RC2 status
 
−
** Looks good, no know bugs
 
−
* Lars: Activate autoclose for Platform bugs?
 
−
** Lars argues that platform and e4 has too many old bugs so people are not looking at them
 
−
** McQ is against autoclose
 
−
** Agreed by al to enable "Pinging the user if this problem still exists" for selected components (Platform/UI) and see how much feedback we get.
 
−
** Email send to McQ, Tom and Alex if we could also add e4 to that pinging list -> all agreed to enable it also for e4 bugs
 
  
−
'''August 28, 2018''' - Alex, Lars, Dani, Tom
+
'''July 14, 2020''' - Tom, Dani, Alex, McQ, Lars
−
* Reminder - RC1 this week, RC2 next week
+
* Project status
−
* Dani on vacation starting this Friday
+
** M1 shipped last week
−
* Dani will submit the release review and IP log before going on vacation (Wayne approved this)
+
** Draft Plan for 4.17 posted - additional fixes done after review
−
** Alex will handle all things that come up with that
+
** Release record created for 4.17
−
* EPL 2.0
+
* CQ process discussion - new clearly defined process
−
** Lars: almost done - few pending patches
+
** Note sent to Wayne to get clarifications on handbook, Wayne has made some edits in response.  We need to review latest handbook
−
** Alex: boring work - hopefully EPL 3.0 only on 10 years
+
** Should simplify IP clearance for third party libraries
 +
*** If a bundle is approved by clearly defined it can be added with no CQ as long as the mavin URLs/coordinates are vetted by clearly defined
 +
*** Orbit should soon automate the linking to clearly defined approvals for bundles added.  Currently a work in progress by Roland at Orbit.
 +
*** The ratings system at clearly defined is not used.  Only the license check is used.
 +
** PMC needs to review latest handbook on the topic ... As of now we should move forward with the new process
 +
*** If concerns arise later we will need to take actions to correct
 +
* {{bug|565066}} - Needs some attention to the solution and testing
 +
** attempt to make incremental installation be consistent with resolution of a fresh install (or -clean).
  
  
−
'''August 21, 2018''' - Alex, Lars, Dani, Tom
+
'''June 23, 2020''' - no call
−
* Reminder - M3 this week RC1 next week
+
−
* Milestone discussion
+
−
** M2 and M3 are too close together.
+
−
** Delivering M1 and M3 instead provides better space for the development team.
+
−
** M1 will be short, but still should give us 1 month time to deliver. 
+
−
** For 4.10 we will try delivering M1 and M3 milestones.
+
−
* Dani will look at submitting the release review and IP log early since he will be out during the week they are due.
+
−
** Alex will cover if that cannot be done
+
−
* EDP update - Arch council is making changes ... should ease some things. 
+
−
** For example, decoupling the project review from a project release.  Project releases still will require IPLogs
+
−
* Lots of bugs still open against 4.9.
+
−
** Team needs to adjust milestones accordingly before 4.9 is done
+
−
* Java 11
+
−
** Work almost done to support Java 11.
+
−
** Initial support will be delivered in Marketplace only (no 4.9a planned).
+
−
** First official release with Java 11 support will be 4.10
+
  
 +
'''June 16, 2020''' - no call
  
−
'''August 14, 2018''' - McQ, Alex, Lars, Dani, Tom
+
'''June 9, 2020''' - Alex, Dani, McQ, Lars, Tom
−
* Changing our test framework to use JUnit 5 always ({{bug|531057}})
+
* McQ: message to guide the community got no public reactions so far
−
** In progress: suites are running, but some tests are aborting
+
* Dani: bug reports needed for JDT, do we have PMC agreement?
−
** Reports should be fine in next build
+
** Alex: For me that was approved after jdt-dev vote ended
−
* Release review and IP log will be coming soon
+
** AGREED
−
** M3 next week, then one week for RC1 and one week for RC2
+
* Dani: RC2 done, no major bug so far but still monitoriing for regressions
−
** A lot of bugs in the backlog that need to have their milestone re-assigned
+
* Alex: 4.17 stream open, not finished until 4.16 if final so all apichecks and etc. are in proper shape
−
* Once we get a few releases under our belt using the new process, we should do a retrospective looking at burn rates, quality, etc.
+
* Tom: OSGi R8 merge after stabilizing 4.17 stream
−
** The good news is we no longer have to maintain two streams and back port changes.
+
* Tom: OSGi Move to Java 8 right after that
−
* Support for J9 shared classes merged into Equinox
+
* Dani: Switch to Java 11 as min version as it was already announced to happen in 4.17 stream shortly
−
** Will not update launcher to specify them for this release
+
−
** Need to provide doc on how users can specify the options themselves (via eclipse.ini)
+
−
* McQ away for two weeks
+
  
  
−
'''August 7, 2018''' - McQ, Alex, Lars, Dani
+
'''June 2, 2020''' - Alex, Dani, McQ, Lars, Tom
−
* Dani: outstanding plan topics:
+
* Inactive committer clean up for Eclipse project for the 4.16 release started via {{bug|563720}}
−
** Target platforms should use SLES 15 (instead of 12)
+
* Infrastructure is really slow for RC2 release
−
*** Dani to talk to SWT team about this
+
* RC2 bug queue is really low, one restart issue which is currently under investigated by Tom
−
** Remove RHEL 7.4 (current is 7.5)
+
* Discussion about the JDT cleanup e-mails
−
*** all agree to this
+
** Need to ensure community discussions are positive and respectful.
−
* McQ to send note about Windows 32-bit EOL
+
** Expectations here should come from leadership
−
* Alex: ASM breakage in master — issue in Orbit; should be in next iBuild
+
*** LibreOffice did this in the past to great success.
−
* Dani: shipped M2 last week everything went well
+
** Committers can vote against bugs but the tone of the discussion is important.
 +
** PMC will respond via the public mailing list within a week
  
  
−
'''July 31, 2018''' - Dani, Tom, Alex
+
'''May 26, 2020''' - Alex, Dani, McQ
−
* Dani: For quality reasons, suggests to have an official M3 (August 24) since after RC1 (August 31) we will only have 1 week left
+
* Closed all M3 bugs; RC1 looking good
−
** all agree to this
+
* Tips&tricks, new&noteworthy, contributions to the newsletter in progress
−
* Dani: Initial 4.9 plan is ready but no feedback so far
+
* Chromium integration CQ approved -- https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21808
  
  
−
'''July 10, 2018''' - McQ, Dani, Tom, Alex
+
'''May 19, 2020''' - Tom, Dani, Lars, Alex
−
* 32 bit support
+
* Dani: Issues with the build infrastructure, might endanger M3, the team got a working build for testing
−
** Harder to find 32 bit JVM
+
* Dani: PowerPC hardware was donated so builds are starting again for it
−
** Devs are not supposed to work on 32 bit OSes anymore
+
* Alex: CQ process might get simpler based on blog post from Wayne, Alex to test and validate with Wayne https://blogs.eclipse.org/post/wayne-beaton/revising-eclipse-ip-due-diligence-process-third-party-content
−
** Agreement to drop support for 32 bit but keep sources and build support for some period to give people time to bring it back
+
* Lars: Question if we want to allow "EGit" commit style in Eclipse top-level project. Agreement was to allow it but not to recommend it or enforce it
−
* GTK 2.x support in SWT
+
−
** Planned to be removed for 2018-12 release
+
−
** Needed so GTK 4.x port can be started prior to 4.0 release so SWT needs a taken into account from GTK devs
+
−
** Bugs are not being looked at for some time already and GTK 3 has been the default for years now.
+
−
* 4.9 release
+
−
** M1 is this week
+
−
** Platform will contribute I-build with some basic testing but not the full milestone which is to be done for the only milestone which is to be delivered for M2 of the SimRel
+
  
  
−
'''June 12, 2018''' - McQ, Alex, Tom, Lars
+
'''May 12, 2020''' - Tom, Dani, McQ, Lars, Alex
−
* RC4a looks good; hidpi fix is in place
+
* Update to themes
−
** no plans for further builds at this point
+
** Preference being added for choosing square vs round tabs
 +
** Intern from Alex's team is taking up the work
 +
** Update to Windows theme to be Windows 10
 +
* Alex brings up changes to CQ requirements.  Need to read up on Wayne's post about this and discuss in a future call if we can change how the project does CQs
 +
* Who is running dark theme?
 +
** Need someone to cover test of Dark Theme on Linux.  Lars indicated that he runs with Linux Dark Theme and can help in coverage
 +
** Dani described the various members of his team that cover the rest of the platforms
 +
* Request to contribute to article on what is new in the release for a June newsletter.  Lars to contribute improvements in the Dark theme.  General request to others to contribute anything else.
 +
* ppc64le build troubles
 +
** Been having ongoing issues with the university hosted ppc64le machine we use to build support for ppc64le
 +
** Currently the ppc64le build has been disabled
 +
** Need to find alternatives
 +
*** May be able to use something from IBM public cloud
 +
*** Other suggestions: McQ - look towards using emulation, Alex - could do cross-compilation
 +
** Need to plan if ppc 10 will supported in the future
  
−
'''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 5, 2020''' - Dani, Alex, Lars, McQ, Tom
  
−
'''May 29, 2018''' - Alex, Tom, Dani
+
* M2 shipped on time
−
* Dani:
+
** Dark theme rebuild for M2 due to severe issue
−
** Uploaded IP log
+
* ICU4J removal note sent
−
** Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck
+
** Lars - 2 years notice period needed?
−
** Finalized Photon plan
+
** Agreement: it's needed as we expose it in API and still have usages in internals so we need time to clean up ourself
−
** Sent Release Review material for approval to PMC mailing list
+
** EPPs cleanup - some blocked by JDT still using it, some by WTP, Rust probably the first one to be icu4j clean
−
** RC3 looks good so far
+
* Roundes vs square ctabfolder
 +
** Number of themes to be reduced
 +
** Performance not being measurable
 +
** Agreement: add preference to switch the rounded vs
 +
** Agreement: when preference is available Square is default
 +
* Windows theme update -
 +
** Fix colors to match Windows 10
 +
** GTK looks way more sane as more effort has been invested to keep it current
 +
** Don't set colors but use the colors from the OS theme is the recipe
 +
** Ugly white line on windows dark theme needs bugzilla open
  
  
−
'''May 22, 2018''' - Alex, Tom, McQ, Dani
+
'''April 28, 2020''' - Dani, Alex, Lars
−
* 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"
+
  
 +
* PMC decided that the OS specific themes should be removed, https://bugs.eclipse.org/bugs/show_bug.cgi?id=562227
 +
* Windows light theme should become better https://bugs.eclipse.org/bugs/show_bug.cgi?id=551462
 +
* Dani - This week is M2, no special freeze or testing but we will contribute our build from Friday to the simrel
 +
* Databinding analyis was done by Jens Lindstroem and it looks good for an API compliant solution
 +
* Alex will prepare the information for cross that we will drop ibm icu from the SDK build
  
−
'''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
 
  
 +
'''April 21, 2020''' - McQ, Alex, Tom, Lars
 +
* Q: How do we deal with ICU removal from data binding?
 +
** Need to follow standard API removal rules
 +
*** Deprecate old API and offer new API
 +
*** Remove deprecated API after 2 years
 +
** Can we put the old stuff in a fragment that could be removed?
 +
* Theming: rounded tabs versus square tabs ({{bug|562221}})
 +
** Should we offer it at all?
 +
** Alex: Don’t increase the number of themes or options
 +
** Lars: Square tabs are faster
 +
** If speed is significant, we should consider changing the default
  
−
'''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
 
  
 +
'''April 14, 2020''' - McQ, Dani, Alex, Tom, Lars
 +
* Dani
 +
** M1 shipped, no problems so far
 +
** Using ECJ from M1 to build the SDK has some issues, there are people working on it
 +
** 4.16 plan to be published this week
 +
* Unanimous decision to continue to use Zoom as usual
  
−
'''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 7, 2020''' - McQ, Dani, Alex, Tom, Lars
 +
* Dani
 +
** Created [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_16.xml 4.16 plan]
 +
** Created [https://bugs.eclipse.org/bugs/show_bug.cgi?id=561643 release record for 4.16]. Corresponding bug is {{bug|561643}}
 +
** Sent note to add planning bugs for 4.16
 +
** '''Please review and provide feedback if any'''
 +
** After some infrastructure issues we have a good test build and currently things look good for M1 this week
 +
* Alex seconded the infrastructure issues and missing test results
 +
* ICU4J ({{bug|560312}}): we decided to remove it piece by piece from projects where possible and where someone is interested to do it. The ICU bundle itself will stay, and we will follow the API removal process when we are ready to remove it, i.e. no usage in the SDK anymore
  
−
'''April 10, 2018''' - Tom, Dani, Lars, Alex
 
−
* Discussed {{bug|533390}}: Eclipse does not launch with Java 11
 
  
 +
'''March 31, 2020''' - Dani, Alex, McQ, Tom, Lars
 +
* Dani: Contacted the ICU4J owner. He updated {{bug|560312}}, PMC members will review the comment and we will discuss next week
 +
* Dani: Planning bugs are created slowly for 4.16. Will send a reminder to the list to submit more. Started to work on plan and release record.
  
−
'''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 24, 2020''' - Alex, McQ, Tom
 +
* Dani: Regrets for the call (Eclipse Board call)
 +
* Alex: status updates
 +
** JDT merged Java 14 in master
 +
** Build instability due to infra status
 +
* Alex: OSGi R8 modules support - what is it?
 +
** Tom: ability to represent external content in the OSGi framework
 +
** Alex: Will it allow shipping eclipse plugins as JPMS modules to ease native library handling?
 +
** Tom: Haven't found any clear example how JPMS handles this, so good example is needed before could be looked further.
  
−
'''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?
 
  
−
--> 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
+
'''March 17, 2020''' - Alex, McQ, Lars Tom, Dani
 +
* ICU4J use still under discussion
 +
** Dani still to contact ICU4J owner
 +
* Shipping Java 14 and 4.15 this week
 +
* Java 14 work will be merged to master on Wednesday
  
−
** 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 10, 2020''' - Lars, Tom
 +
* Dani: Regrets for the call (vacation)
 +
* ICU4J use still under discussion
 +
** if we can be confident that performance and language support are of *similar* quality, we should work towards removing icu4j because it reduces complexity for us, in addition allowing for smaller RCP apps
 +
** note that we already have mixed usage -- some components using icu4j and some not
 +
* to clarify approvals that require a project lead can be done by a project lead for any of the Eclipse Project subprojects
 +
** as usual, the project lead should take care to understand the change and its implications before approving
 +
* we will move to Jetty 10 (and thus to Java 11) for the fall release
 +
* RH will be leading releng for 4.16
  
−
'''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 3, 2020''' - no meeting
  
−
'''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
 
  
 +
'''February 25, 2020''' - Dani, McQ, Tom, Alex
 +
* Dani: Created and sent Endgame plan
 +
* Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
 +
* Alex: SWT on Linux in 4.16 to require Gtk 3.20 to simplify CSS machinery and prep for GTK4
 +
* Alex: ICU4J removal
 +
** Dani: ICU4J reacts faster to changes and supports more features (new Japanese era)
 +
** Alex: It might but Eclipse fails at keeping up so current version shipped with Eclipse misses features that the JVM supports (latest CLDR)
 +
** Dani: Asks for a proof that JVM is better that ICU
 +
** Alex: Which metrics to be measured?
 +
** Dani: Will check with ICU guy about that and whether it's still needed
  
−
'''March 6, 2018''' - McQ, Tom, Alex
 
−
* Short call without any interesting topics
 
  
 +
'''February 18, 2020''' - McQ, Alex, Dani, Lars, Tom
 +
* Dani: need to work on IP Log, Release Review and Endgame Plan
 +
* Lars: ECF - will we update to the latest
 +
** Alex: is in the works. Scott needs to provide us with the update
 +
* Tom: Found an issue with JUnit 5 launching but not reproducible with latest I-build
 +
** Dani: File a bug if you have steps or contact Noopur directly
 +
* Dani: Update on X-builds and tags
  
−
'''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 11, 2020''' - McQ, Alex, Dani, Lars, Tom
 +
* Alex: Infrastructure is very instable, how can be complain to the foundation?
 +
** Alex: Eclipse foundation server team not responding to complains and seem unclear about the source of the issue
 +
** Discussion about makes a stronger statement to the foundation about the bad state of the infrastructure
 +
** McQ: Suggestion to send a note as PMC to the foundation
 +
** Dani: First we should ask webmaster why this takes so long
 +
** Alex: Marketplace infrastructure is also in bad state
 +
*** Dead marketplace entries are not getting removed https://bugs.eclipse.org/bugs/show_bug.cgi?id=550713
 +
*** No clean contact person from the foundation
 +
*** Marketplace is also not Open Source hence we cannot fix thing ourself.
  
−
'''February 20, 2018''' - Lars, Dani, McQ, Tom
+
-> Alex to contact Denis and to cc the other PMC members
  
−
* Dani: Update on 4.7 RC3
+
'''February 4, 2020''' - McQ, Dani, Tom
−
* Lars: Can we drop Windows XP support?
+
* OSGi Spec talk
−
** 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.
+
** OSGi R8 Core will be done this year.
−
** Dani: IBM investigate if they officially drop XP
+
** May be ready for 4.16, but no rush if it slips to 4.17
−
** Tom: Do we need support XP with the latest Eclipse version?
+
** Will not put anything in master until spec is final which makes it more likely to be 4.17
−
--> 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
+
'''January 28, 2020''' - McQ, Alex, Dani, Tom, Lars
−
* Lars: Can we mark MInput and MInputPart for deletion ({{bug|509868}})?
+
* Ongoing saga of the EPP packages
−
** 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.
+
** Markus did it last week
−
*** McQ agrees
+
** PMC discussed possible futures here, but no conclusions
−
* 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
+
** Discussion also happening at the board level
−
** Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
+
* M2 is this week
−
** McQ:
+
* Pushing for JUnit updates for M2
−
*** 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
+
'''January 21, 2020''' - Dani, Tom, Lars
−
* General Updates (Dani)
+
* Dani: EPP builds still missing, Dani contacted Markus Knauer to update EPP for M1, release train is at risk if nobody steps up
−
** Shipped M5, still working some p2 issues
+
* New test failures are investigated, action plan is to restart the test, if they still fails restart the machine and if the tests still fail, see if a revert fixes the test
−
** 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.
+
  
  
−
'''January 16, 2018''' - Alex, Lars, Dani, Tom
+
'''January 14, 2020''' - McQ, Alex, Dani, Tom
−
* Native builds at eclipse.org status (Lars):
+
* Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
−
** Dani: swt is done for some time already
+
* Dani: Plan updated to remove Windows 7
−
** Dani: launchers after M5 is released to prevent breakage
+
* Alex: Felix Dependencies for SCR done
−
* GTK launcher changes (Alex):
+
** confirm fix for {{bug|544571}}
−
** Changes to not rely on X11 atoms but on dbus ready for review
+
** releng disruptions during update, but recovered.  More disruptions expected as we update dependencies for March release.
−
** Linux only as no other GTK platforms are currently built
+
** broken builds, need to get a list of issues.  Seems to be more infrastructure issues.  Need to report back to the foundation. Example, the signing issue that broken the respin.
−
* Equinox CQs (Tom):
+
* Some discussion about gitlab option at foundation. {{bug|537913}}
−
** P2 capabilities patch from Todor and felix.scr update
+
** What happens to gerrit work flow for review?
−
** Slow process risking M5
+
** Would dropping bugzilla happen or can we migrate all issues?
−
** Alex: Ping Sharon asking for speedup if possible
+
** Without migration it is a no-go for us
−
* Updates from Dani:
+
** Currently no plans to move Eclipse project to gitlab at this time.
−
** 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
+
'''January 7, 2020''' - McQ, Alex, Dani, Tom, Lars
−
* Updates from Dani:
+
* Dani: Created initial 4.15 plan - please have a look
−
** Ian Skerrett is leaving the Eclipse foundation
+
* Dani: Created release record for 4.15
−
** Dani got nominated as committer representive
+
* Dani: Sent a note to teams to create their 4.15 plan items/bugs
−
* Planning council update
+
* Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
−
** Dani: low participation in the last calls
+
** Unanimous decision: Yes
−
** Dani will talk with Melanie about it
+
* Dani: Discuss (again, see below) resolution for stale bugs
−
** Input  required for the planning council for the API and feature freezes for the platform
+
** We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
−
* API and feature freeze policy in platform
+
** We will only auto/mass close existing stale bugs with notification turned off
−
*** Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build
+
* Change rules about x-internal exports ({{bug|553709}})
−
*** everyone agrees to Alex suggestion-> agreed
+
** Decision:
−
* 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
+
** - Newly added internal packages should not use x-internal exports unless there are very good reasons
−
* Dani: Plan update, biggest change is for the component plan
+
** - For existing packages the x-internal export can be removed with PMC approval
−
** Equinox plan has been added
+
−
** Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build
+
−
* Launcher and natives build move from IBM to the foundation still in progress
+
−
** ({{bug|528230}}) Build FileSystem native component on Eclipse Foundation Infra
+
−
** ({{bug|528230}}) Build launcher on Eclipse Foundation Infra
+
  
 
= Archive =
 
= Archive =
 +
* [[Eclipse/PMC/Minutes 2019 | Archive of Meeting Minutes from 2019]]
 +
* [[Eclipse/PMC/Minutes 2018 | Archive of Meeting Minutes from 2018]]
 
* [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]]
 
* [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]]
 
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]

Revision as of 11:09, 21 April 2021

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 31, 2021 - McQ, Tom, Alex, Lars

  • Java 16 jar signing issue
    • Tom wants to replace equinox implementation with builtin Jar file implementation so changes don't have to be done in Equinox on each release
  • JSP/Jetty story in IDE
    • Do we still need same functionality?
    • Alex - get out of the business for help system. Dependencies (jetty, lucene) generate more releng work than we can handle.
    • McQ - url for plugin help would be simplest and open it in browser
    • Any change (e.g. JSP removal) has to go through standard deprecation period, announcements and etc.
    • Alex to initiate communication on longer term plan with Holger who works on improvements to help system lately


Mar 31, 2021 - McQ, Tom, Alex

  • PMC call time
    • Overlaps with Planning council call and both Tom and Alex can't make both

-> Decision: Skip PMC call every first Wed of the month

  • Webpage Hugo migration
    • Recommended by Eclipse Foundation and active contributor to do the conversion
    • Concerns about mixing old and new content are raised but they don't look severe
    • Supported by PMC

-> Tom to handle initial communication on behalf of PMC

  • Planning process relevance
    • the planning process is not providing the detailed and usable plans from the past
    • not a pain point as fewer people participate it but looks like useless exercise quite often
    • to be discussed....


Mar 24, 2021 - Tom, Alex, Lars

  • Pack 200 - API removal in 2 years - 2023-06
    • Should we turn off all pack 200 features in one year, make it consistent across all Java versions.
    • 2022-06 - disable pack200 for all Java versions. Calling the deprecated API will be a no-op
  • Pack 200 - When can we stop generating? Agreed on 2021-09 release. We should set the precedence as early as possible to stop producing pack200 artifacts.
  • split packages
    • Causing issues with mandatory directive and p2 bug 360659 and with tycho.
    • Currently tycho requires some work arounds for usage of split packages
    • Can we work to get rid of split packages. We agreed to investigate the work and move to combine split packages if possible.


Mar 17, 2021 - McQ, Tom, Alex, Lars

  • SWT Chromium support
    • Still no recent version of Chromium with security patches
    • Will be dropped in M1 (if no recent version is provided in the next weeks or if no one steps up)
  • Pack 2000 support
    • not supported anymore as of Java 14
    • will be deprecated and marked for removal
  • Moving Eclipse repos to Github
    • Moving to Github might simplify and therefore increase contributions
    • Huge amount of work in releng
    • Potentially we should all subprojects at the same time
    • We check if the foundation plans to move everything to Gitlab


Mar 10, 2021 - McQ, Tom, Alex

  • Moving to Jetty 10 for next release
  • platform-dev discussion about move to GitHub
    • conversation is useful, but would take a lot of planning
    • lots of current rel eng dependencies on Gerrit
      • need more community help for rel eng issues
    • a massive amount of history in our Bugzilla
  • release record and proto-plan created for 4.20


Febr 17, 2021 - Lars, Alex, McQ

  • Looks good for 4.19 release
  • Mac ARM has to wait for the 4.20 release, as the team fights multiple issues
  • Top-level project page can currently only be edited by Tom, other PMC members also have access to it https://projects.eclipse.org/projects/eclipse/who


Dec 15, 2020 - Lars, Alex, McQ

  • 06. January 2021 is the next meeting
  • How can PMC increase the awareness of the project leads / committers?
    • Maybe invite the project leads once per month to the PMC meeting?
    • Discussion how we can increase the JDT community


Dec 01, 2020 - Lars, Alex, McQ

  • RC1 is out; final touches on RC2
  • How can we remove the confusion about "e4" project?
    • e4 has always been intended to be a sandbox project where people could try things that are experimental or are on a longer timeline
    • Should be renamed to make it clear this isn't about leftovers from the Eclipse 4.0 work (maybe "eNext"?)
    • Should clean up repos
      • Remove repos that just hold code that has already moved to the platform
      • Remove repos that are no longer getting any investment
      • Work toward moving things that are active/useful into the platform (e.g. "spies" to PDE)

Nov 24, 2020 - Lars, Alex, McQ

  • PMC is considering the potential of an SDK / IDE working group at the foundation
  • Discussion Do we need the extra releng work to create p2 repositories for milestones?
    • Lot of extra work and sometimes goes wrong
    • All I-Builds are anyway available

-> PMC decided to drop the additional p2 repository -> Alex will be sending out an email about it to inform potential users of the special p2 repos

    • Discussion about the purpose of the milestone week at all

-> Decision not to change the process for now, as the additional testing and focus has also some benefits


Nov 17, 2020 - Lars, Alex, Tom, McQ

  • Release 4.18 winding down
    • SWT churn for Linux and Mac Big Sur
    • Does not appear the Foundation got the new Mac Hardware for testing
  • Planning Council discussion
    • Dani filled the Eclipse TLP representation role on the Council
    • Alex can take the lead to that role
    • Alex will look to find a replacement for the tools TLP representative


Nov 10, 2020 - Lars, Alex, Tom, McQ

  • Still dealing with the loss of Dani
  • Discussed representation of JDT on PMC
  • Stabilizing for M3
  • Some releng issues with Java 15 and 16
  • Tom began investigating p2 ECF httpclient dependency


Nov 10, 2020 - Lars, Alex, Tom, McQ

  • Still dealing with the loss of Dani
  • Discussed representation of JDT on PMC
  • Stabilizing for M3
  • Some releng issues with Java 15 and 16
  • Tom began investigating p2 ECF httpclient dependency


Nov 3, 2020 - Lars, Alex, Tom, McQ

  • Dani!


Oct 27, 2020 - Lars, Tom

  • Nothing to discuss


Oct 20, 2020 - Lars, Tom, McQ, Alex

  • EclipseCon is running virtual this week
  • Agreement that removal of API should only before M1 release
  • Proof of concept for using Java 11 http client instead of ECF should be done
  • if we remove ECF we should send out an announcement and keep it for at least one release
  • Decision to start using the @Deprecated(since = "x.y.z", forRemoval = true) for planned API removals if the bundle can use Java 11, wiki for API removal should be updated

Oct 6, 2020 - Dani, Tom, McQ, Alex

  • M1 under control
  • Release train materials being worked
  • Moved to Jetty 9.4.32
  • ECF — need to simplify how we consume http client
    • could use Java11 http client instead, but this would require significant development effort
    • Tom/Alex to take an initial stab at understanding scope + open bugs
  • Proposal: remove API once a year
    • Given the already long time for consumers to respond to API deprecation, PMC decision was to continue to allow API removal in any release. It was felt that the incremental benefit was outweighed by the need to be able to move forward quickly.


Sep 15, 2020 - Dani, Tom, Lars, Alex

  • M1
    • Next week M1 - Alex to send reminder note
    • Holiday in India on this Friday
  • Y-Build for Java 16
    • Builds should be fixed and can continue to progress on Java 16
  • SCR upgrade
    • Some issues with EBR maven plugin
    • causes versions to be incorrectly represented in p2 meta-data
    • Orbit needs a new lead, will end up impacting us if no replacement found
  • Tycho being updated to be able to OSGi-fy JARs if they are not there yet.
    • How to use this for a feature?
    • Behaves much like Orbit to produce new versions of the artifact.
    • Could be the solution for Orbit needs.


Sep 22, 2020 - no meeting


Sep 15, 2020 - McQ, Dani, Lars, Tom, Alex

  • Dani: Java 15 released today
    • 4.17 release together with Marketplace for Java 15 support are ready
    • JDT Java 15 to be merged this week
  • Dani: Zoom call with password unless each of the PMC members can be added as meeting owner so can start the meeting
  • Alex: 4.18 stream opened and releng work calmed down
  • Lars: Cleanup of migration guides
    • Dani: this will break existing links, so existing content have to stay unless someone does all the work to fix our plans and other links that will break
    • McQ: help system needs work to focus on the latest stuff/release, what should we do to achieve it? How can we better shape the help system now that having all content ofline is not a requirement?
    • Alex: do not ship migration, n&n,etc. but rather point to website url from help system
    • Alex: this would also reduce manual work for releng (+1 by Dani)
    • ACTION ITEM: Alex to work on n&n in help system to use the website content directly as a proof of concept for further work


Sep 01, 2020 - Lars, Alex

  • RC1 is fine, no additional requests for RC2


August 25, 2020 - Tom, Lars, Alex, Dani

  • Dani: sent out Endgame plan, RC1 this week, vacation starting on Friday
  • Alex informed about Red Hat's Releng participation


August 18, 2020 - Tom, Lars, Dani

  • Dani to create and send out Endgame plan
  • Looking into Mac Big Sur launching issue (bug 565913)


August 11, 2020 - Alex, Dani, Tom, McQ

  • Eclipse Foundation is getting access to an Apple Silicon dev kit
    • Will make it available to SWT devs via cloud connectivity
  • M3 next week; RC1 following week
  • ARM64 port seems to be working fine, except for browser widget (still investigating)


August 4, 2020 - Alex, Lars, Dani

  • no topics to discuss


July 28, 2020 - Tom, McQ

  • no topics to discuss


July 21, 2020 - Tom, Dani, Alex, McQ, Lars

  • no topics to discuss
  • Alex on vacation next week


July 14, 2020 - Tom, Dani, Alex, McQ, Lars

  • Project status
    • M1 shipped last week
    • Draft Plan for 4.17 posted - additional fixes done after review
    • Release record created for 4.17
  • CQ process discussion - new clearly defined process
    • Note sent to Wayne to get clarifications on handbook, Wayne has made some edits in response. We need to review latest handbook
    • Should simplify IP clearance for third party libraries
      • If a bundle is approved by clearly defined it can be added with no CQ as long as the mavin URLs/coordinates are vetted by clearly defined
      • Orbit should soon automate the linking to clearly defined approvals for bundles added. Currently a work in progress by Roland at Orbit.
      • The ratings system at clearly defined is not used. Only the license check is used.
    • PMC needs to review latest handbook on the topic ... As of now we should move forward with the new process
      • If concerns arise later we will need to take actions to correct
  • bug 565066 - Needs some attention to the solution and testing
    • attempt to make incremental installation be consistent with resolution of a fresh install (or -clean).


June 23, 2020 - no call

June 16, 2020 - no call

June 9, 2020 - Alex, Dani, McQ, Lars, Tom

  • McQ: message to guide the community got no public reactions so far
  • Dani: bug reports needed for JDT, do we have PMC agreement?
    • Alex: For me that was approved after jdt-dev vote ended
    • AGREED
  • Dani: RC2 done, no major bug so far but still monitoriing for regressions
  • Alex: 4.17 stream open, not finished until 4.16 if final so all apichecks and etc. are in proper shape
  • Tom: OSGi R8 merge after stabilizing 4.17 stream
  • Tom: OSGi Move to Java 8 right after that
  • Dani: Switch to Java 11 as min version as it was already announced to happen in 4.17 stream shortly


June 2, 2020 - Alex, Dani, McQ, Lars, Tom

  • Inactive committer clean up for Eclipse project for the 4.16 release started via bug 563720
  • Infrastructure is really slow for RC2 release
  • RC2 bug queue is really low, one restart issue which is currently under investigated by Tom
  • Discussion about the JDT cleanup e-mails
    • Need to ensure community discussions are positive and respectful.
    • Expectations here should come from leadership
      • LibreOffice did this in the past to great success.
    • Committers can vote against bugs but the tone of the discussion is important.
    • PMC will respond via the public mailing list within a week


May 26, 2020 - Alex, Dani, McQ


May 19, 2020 - Tom, Dani, Lars, Alex

  • Dani: Issues with the build infrastructure, might endanger M3, the team got a working build for testing
  • Dani: PowerPC hardware was donated so builds are starting again for it
  • Alex: CQ process might get simpler based on blog post from Wayne, Alex to test and validate with Wayne https://blogs.eclipse.org/post/wayne-beaton/revising-eclipse-ip-due-diligence-process-third-party-content
  • Lars: Question if we want to allow "EGit" commit style in Eclipse top-level project. Agreement was to allow it but not to recommend it or enforce it


May 12, 2020 - Tom, Dani, McQ, Lars, Alex

  • Update to themes
    • Preference being added for choosing square vs round tabs
    • Intern from Alex's team is taking up the work
    • Update to Windows theme to be Windows 10
  • Alex brings up changes to CQ requirements. Need to read up on Wayne's post about this and discuss in a future call if we can change how the project does CQs
  • Who is running dark theme?
    • Need someone to cover test of Dark Theme on Linux. Lars indicated that he runs with Linux Dark Theme and can help in coverage
    • Dani described the various members of his team that cover the rest of the platforms
  • Request to contribute to article on what is new in the release for a June newsletter. Lars to contribute improvements in the Dark theme. General request to others to contribute anything else.
  • ppc64le build troubles
    • Been having ongoing issues with the university hosted ppc64le machine we use to build support for ppc64le
    • Currently the ppc64le build has been disabled
    • Need to find alternatives
      • May be able to use something from IBM public cloud
      • Other suggestions: McQ - look towards using emulation, Alex - could do cross-compilation
    • Need to plan if ppc 10 will supported in the future


May 5, 2020 - Dani, Alex, Lars, McQ, Tom

  • M2 shipped on time
    • Dark theme rebuild for M2 due to severe issue
  • ICU4J removal note sent
    • Lars - 2 years notice period needed?
    • Agreement: it's needed as we expose it in API and still have usages in internals so we need time to clean up ourself
    • EPPs cleanup - some blocked by JDT still using it, some by WTP, Rust probably the first one to be icu4j clean
  • Roundes vs square ctabfolder
    • Number of themes to be reduced
    • Performance not being measurable
    • Agreement: add preference to switch the rounded vs
    • Agreement: when preference is available Square is default
  • Windows theme update -
    • Fix colors to match Windows 10
    • GTK looks way more sane as more effort has been invested to keep it current
    • Don't set colors but use the colors from the OS theme is the recipe
    • Ugly white line on windows dark theme needs bugzilla open


April 28, 2020 - Dani, Alex, Lars


April 21, 2020 - McQ, Alex, Tom, Lars

  • Q: How do we deal with ICU removal from data binding?
    • Need to follow standard API removal rules
      • Deprecate old API and offer new API
      • Remove deprecated API after 2 years
    • Can we put the old stuff in a fragment that could be removed?
  • Theming: rounded tabs versus square tabs (bug 562221)
    • Should we offer it at all?
    • Alex: Don’t increase the number of themes or options
    • Lars: Square tabs are faster
    • If speed is significant, we should consider changing the default


April 14, 2020 - McQ, Dani, Alex, Tom, Lars

  • Dani
    • M1 shipped, no problems so far
    • Using ECJ from M1 to build the SDK has some issues, there are people working on it
    • 4.16 plan to be published this week
  • Unanimous decision to continue to use Zoom as usual


April 7, 2020 - McQ, Dani, Alex, Tom, Lars

  • Dani
    • Created 4.16 plan
    • Created release record for 4.16. Corresponding bug is bug 561643
    • Sent note to add planning bugs for 4.16
    • Please review and provide feedback if any
    • After some infrastructure issues we have a good test build and currently things look good for M1 this week
  • Alex seconded the infrastructure issues and missing test results
  • ICU4J (bug 560312): we decided to remove it piece by piece from projects where possible and where someone is interested to do it. The ICU bundle itself will stay, and we will follow the API removal process when we are ready to remove it, i.e. no usage in the SDK anymore


March 31, 2020 - Dani, Alex, McQ, Tom, Lars

  • Dani: Contacted the ICU4J owner. He updated bug 560312, PMC members will review the comment and we will discuss next week
  • Dani: Planning bugs are created slowly for 4.16. Will send a reminder to the list to submit more. Started to work on plan and release record.


March 24, 2020 - Alex, McQ, Tom

  • Dani: Regrets for the call (Eclipse Board call)
  • Alex: status updates
    • JDT merged Java 14 in master
    • Build instability due to infra status
  • Alex: OSGi R8 modules support - what is it?
    • Tom: ability to represent external content in the OSGi framework
    • Alex: Will it allow shipping eclipse plugins as JPMS modules to ease native library handling?
    • Tom: Haven't found any clear example how JPMS handles this, so good example is needed before could be looked further.


March 17, 2020 - Alex, McQ, Lars Tom, Dani

  • ICU4J use still under discussion
    • Dani still to contact ICU4J owner
  • Shipping Java 14 and 4.15 this week
  • Java 14 work will be merged to master on Wednesday


March 10, 2020 - Lars, Tom

  • Dani: Regrets for the call (vacation)
  • ICU4J use still under discussion
    • if we can be confident that performance and language support are of *similar* quality, we should work towards removing icu4j because it reduces complexity for us, in addition allowing for smaller RCP apps
    • note that we already have mixed usage -- some components using icu4j and some not
  • to clarify approvals that require a project lead can be done by a project lead for any of the Eclipse Project subprojects
    • as usual, the project lead should take care to understand the change and its implications before approving
  • we will move to Jetty 10 (and thus to Java 11) for the fall release
  • RH will be leading releng for 4.16


March 3, 2020 - no meeting


February 25, 2020 - Dani, McQ, Tom, Alex

  • Dani: Created and sent Endgame plan
  • Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
  • Alex: SWT on Linux in 4.16 to require Gtk 3.20 to simplify CSS machinery and prep for GTK4
  • Alex: ICU4J removal
    • Dani: ICU4J reacts faster to changes and supports more features (new Japanese era)
    • Alex: It might but Eclipse fails at keeping up so current version shipped with Eclipse misses features that the JVM supports (latest CLDR)
    • Dani: Asks for a proof that JVM is better that ICU
    • Alex: Which metrics to be measured?
    • Dani: Will check with ICU guy about that and whether it's still needed


February 18, 2020 - McQ, Alex, Dani, Lars, Tom

  • Dani: need to work on IP Log, Release Review and Endgame Plan
  • Lars: ECF - will we update to the latest
    • Alex: is in the works. Scott needs to provide us with the update
  • Tom: Found an issue with JUnit 5 launching but not reproducible with latest I-build
    • Dani: File a bug if you have steps or contact Noopur directly
  • Dani: Update on X-builds and tags


February 11, 2020 - McQ, Alex, Dani, Lars, Tom

  • Alex: Infrastructure is very instable, how can be complain to the foundation?
    • Alex: Eclipse foundation server team not responding to complains and seem unclear about the source of the issue
    • Discussion about makes a stronger statement to the foundation about the bad state of the infrastructure
    • McQ: Suggestion to send a note as PMC to the foundation
    • Dani: First we should ask webmaster why this takes so long
    • Alex: Marketplace infrastructure is also in bad state

-> Alex to contact Denis and to cc the other PMC members

February 4, 2020 - McQ, Dani, Tom

  • OSGi Spec talk
    • OSGi R8 Core will be done this year.
    • May be ready for 4.16, but no rush if it slips to 4.17
    • Will not put anything in master until spec is final which makes it more likely to be 4.17


January 28, 2020 - McQ, Alex, Dani, Tom, Lars

  • Ongoing saga of the EPP packages
    • Markus did it last week
    • PMC discussed possible futures here, but no conclusions
    • Discussion also happening at the board level
  • M2 is this week
  • Pushing for JUnit updates for M2


January 21, 2020 - Dani, Tom, Lars

  • Dani: EPP builds still missing, Dani contacted Markus Knauer to update EPP for M1, release train is at risk if nobody steps up
  • New test failures are investigated, action plan is to restart the test, if they still fails restart the machine and if the tests still fail, see if a revert fixes the test


January 14, 2020 - McQ, Alex, Dani, Tom

  • Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
  • Dani: Plan updated to remove Windows 7
  • Alex: Felix Dependencies for SCR done
    • confirm fix for bug 544571
    • releng disruptions during update, but recovered. More disruptions expected as we update dependencies for March release.
    • broken builds, need to get a list of issues. Seems to be more infrastructure issues. Need to report back to the foundation. Example, the signing issue that broken the respin.
  • Some discussion about gitlab option at foundation. bug 537913
    • What happens to gerrit work flow for review?
    • Would dropping bugzilla happen or can we migrate all issues?
    • Without migration it is a no-go for us
    • Currently no plans to move Eclipse project to gitlab at this time.


January 7, 2020 - McQ, Alex, Dani, Tom, Lars

  • Dani: Created initial 4.15 plan - please have a look
  • Dani: Created release record for 4.15
  • Dani: Sent a note to teams to create their 4.15 plan items/bugs
  • Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
    • Unanimous decision: Yes
  • Dani: Discuss (again, see below) resolution for stale bugs
    • We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
    • We will only auto/mass close existing stale bugs with notification turned off
  • Change rules about x-internal exports (bug 553709)
    • Decision:
    • - Newly added internal packages should not use x-internal exports unless there are very good reasons
    • - For existing packages the x-internal export can be removed with PMC approval

Archive

Retrieved from "https://wiki.eclipse.org/index.php?title=Eclipse/PMC&oldid=443062"

Back to the top